autocrypto-setup

One command to wire AutoCrypto into your AI assistant.

npx autocrypto-setup

That's it. The installer detects which AI clients you have (Claude Code, Claude Desktop, Cursor, VS Code, Windsurf), adds the AutoCrypto MCP server to each, and drops the AutoCrypto skills into ~/.claude/skills/autocrypto/.

You run this in your own terminal — not via your AI. AI assistants run in sandboxed containers; if you ask Claude Code (or any other AI) to run the installer for you, it will install in the sandbox, not on your machine. Open Terminal.app (macOS), iTerm, or your shell of choice, and paste the command above.

After install, open your AI and just say what you want:

"Set up my crypto agent."

"Watch ETH for me, careful style, $100."

"Pause everything."

⚠ Before you (or your AI) run it — trust signals

Reasonable concern: any package with the word crypto in its name should be treated like a supply-chain risk until proven otherwise. Read SECURITY.md — it explains exactly what this package does, what it doesn't, what an LLM should verify, and how to audit it in a sandbox.

Quick facts (each one is verifiable from the source in this repo):

• Zero runtime dependencies. npm pack --dry-run shows the published tarball contains only files in dist/ and skills/.
• No network calls during install. The installer reads/writes only config files in your home directory.
• No secrets touched. It cannot see your seed phrase, private keys, or wallet — wallet connection happens later, in your browser, on autocrypto.space/connect.
• Backup-first writes. Every config file is copied to <file>.autocrypto-bak-<timestamp> before any change.
• Idempotent. Run twice, get the same state. Run with --uninstall to remove cleanly.
• Open source. This repo is the canonical source — the npm tarball is built from src/ via tsc. From v0.2.0, every release is signed with npm provenance attesting it was built from a specific GitHub commit.

Maintained by Backroom Inc. — product info at autocrypto.space.

What it does

1. Detects every supported AI client installed on your machine.
2. Backs up any existing config files (<file>.autocrypto-bak-<timestamp>) before touching them.
3. Adds an autocrypto MCP server entry pointing at https://autocrypto.space/api/mcp (override with AUTOCRYPTO_MCP_URL).
4. Installs the AutoCrypto skills into ~/.claude/skills/autocrypto/ (Claude Code only; other clients use the MCP server's tools directly).

It does not:

• modify any configuration outside the MCP entry it adds,
• read your wallet, seed phrase, or private keys,
• touch your funds — connecting a wallet happens later, on the AutoCrypto website.

Supported AI clients

| Client | Config file written | |---|---| | Claude Code | ~/.claude/settings.json | | Claude Desktop | ~/Library/Application Support/Claude/claude_desktop_config.json (macOS), %APPDATA%\Claude\claude_desktop_config.json (Win), ~/.config/Claude/claude_desktop_config.json (Linux) | | Cursor | ~/.cursor/mcp.json | | VS Code | ~/Library/Application Support/Code/User/mcp.json (macOS), platform-equivalent elsewhere | | Windsurf | ~/.codeium/windsurf/mcp_config.json |

Usage

# Install (interactive — confirms before writing anything)
npx autocrypto-setup

# Uninstall — removes AutoCrypto entries from every client and the skills directory
npx autocrypto-setup --uninstall

# Show help
npx autocrypto-setup --help

Environment variables

| Variable | Purpose | Default | |---|---|---| | AUTOCRYPTO_MCP_URL | Override the MCP endpoint (useful for local dev) | https://autocrypto.space/api/mcp |

After install — the wallet step

Installing the agent is step 1 of 2. Step 2 is connecting your crypto wallet on autocrypto.space/connect. The wallet is your identity — without it the agent can analyse markets but can't trade anything for you.

Free to install. Free to connect. Free to analyse and simulate. Pay only if you want the agent to execute real on-chain trades — $9.99/mo or $95.88/yr (-20%), Stripe-secured, cancel anytime.

Safety

• Every config file is backed up before modification (<file>.autocrypto-bak-<timestamp>).
• The installer never writes secrets, never touches your wallet, never makes a network call beyond what it needs to verify the package version.
• Atomic writes: configs are written to a temp file then renamed, so a crash mid-write leaves your existing config untouched.
• Idempotent: running the installer twice writes the same entry; nothing duplicates.

Uninstalling

npx autocrypto-setup --uninstall

This removes the autocrypto MCP entry from every client config file and deletes ~/.claude/skills/autocrypto/. It does not touch any other entries you've added. The previous backups are kept on disk so you can restore manually if needed.

Troubleshooting

"No supported AI client detected" — make sure your AI app has been launched at least once so its config directory exists. The installer checks for the canonical paths above.

"MCP entry added (restart Cursor to load)" — most clients require a restart after their MCP config changes.

Wrong URL — set AUTOCRYPTO_MCP_URL if you're running a local dev instance: AUTOCRYPTO_MCP_URL=http://localhost:3000/api/mcp npx autocrypto-setup.

Privacy

The installer runs entirely on your machine and reads/writes only the config files listed above. It does not phone home, does not collect telemetry, and does not include any third-party tracking. Once the AutoCrypto MCP server is active, it sees the requests your AI sends to it; see autocrypto.space/legal for the full data-processing disclosure.

License

MIT. Source code: this repository.

Author

Developed by Soynido — see autocrypto.space/legal for legal mentions.