Use AC with Cursor

Prerequisites

• Cursor 0.43+ with MCP support enabled.
• Node ≥ 20 on PATH (for npx).
• An ac_live_… key from /agent in the AC app.

1 · Open MCP settings

Cursor → Settings → MCP. Click Add new MCP Server. Cursor stores its MCP config at ~/.cursor/mcp.json on macOS / Linux and %USERPROFILE%\.cursor\mcp.json on Windows — you can edit that file directly if you prefer.

2 · Add the server block

{
  "mcpServers": {
    "advisors-crypto": {
      "command": "npx",
      "args": ["-y", "@advisors-crypto/mcp"],
      "env": {
        "AC_AGENT_KEY": "ac_live_…"
      }
    }
  }
}

3 · Reload

Cursor reloads MCP servers when you close and reopen the settings panel — no full restart needed. The advisors-crypto server should turn green and show 6 tools, 2 resources, 2 prompts.

4 · Useful Cursor patterns

• Inline policy checks. Ask Cursor in chat: “Use validate_trade to check what would happen if I bought $5k of BTC.” It returns the decision inline next to your code.
• Codegen with policy context. Read the ac://mandate/current resource into context, then ask Cursor to write a sizing helper that respects the bands. The model sees the real limits.
• Prompt-driven flows. Use the propose-trade-with-rationale prompt — Cursor surfaces MCP prompts in the slash menu.

Keeping agent tools out of normal sessions

Cursor lets you scope MCP tools to specific composer modes or chat sessions. If you don’t want the AC tools showing up while you’re writing a webpack config, disable the server in that workspace and re-enable it when you’re working on agent code.

Troubleshooting

• Red status. Click the row → check the stderr panel. Common cause: npx couldn’t reach the registry (corporate proxy).
• Tools surface but every call 401s. Your AC_AGENT_KEY is wrong, expired, or revoked.
• Missing tools after Cursor update. MCP settings are version-stable but the merge order changed in 0.43 — global keys are applied first, project keys override.