Skip to main content

Connect Your AI Agent

Axon exposes ~35 typed tools over the Model Context Protocol (MCP). Any MCP-compatible runtime can drive the daemon.

One-command setup​

The CLI auto-detects installed runtimes and writes the right config for each:

axon install

Output looks like:

✓ Claude Code     — wrote ~/.config/claude-code/mcp_servers.json
✓ Claude Desktop  — wrote ~/Library/Application Support/Claude/claude_desktop_config.json
✓ Cursor          — wrote ~/Library/Application Support/Cursor/User/globalStorage/...
✓ Cline           — wrote ~/.config/cline/mcp_servers.json
✗ Continue        — not detected (install Continue, then re-run `axon install`)

Restart your agent runtime once after the install. The Axon MCP server appears as axon with ~35 tools (get_balance, open_perp, install_strategy, kill_switch_on, …).

Supported runtimes​

RuntimeDetectionConfig file
Claude Code~/.config/claude-code/ existsmcp_servers.json
Claude DesktopApp installedclaude_desktop_config.json
CursorApp installedmcp.json in user globalStorage
ClineVS Code ext installedcline_mcp_settings.json
Codexcodex binary on PATH~/.codex/mcp.json
Continue.continue/ config exists.continue/config.json
WindsurfApp installed~/.codeium/windsurf/mcp_config.json
OpenClawApp installedopenclaw.config.json

Targeted install​

Install for just one runtime:

axon install claude-code
axon install cursor
axon install cline

Dry-run to preview the config diff without writing:

axon install --print

Verify existing configs (catches stale paths after a CLI reinstall):

axon install --verify

Manual setup​

If axon install can't auto-detect your runtime, here's the canonical MCP server config:

{
  "mcpServers": {
    "axon": {
      "command": "axon",
      "args": ["mcp"]
    }
  }
}

Or, if axon isn't on PATH for your runtime:

{
  "mcpServers": {
    "axon": {
      "command": "/absolute/path/to/axon",
      "args": ["mcp"]
    }
  }
}

Drop this into your runtime's MCP config file and restart.

How auth works​

The MCP server is a stdio subprocess spawned by your agent. It connects to the running daemon at http://127.0.0.1:47890/ using the bearer token from ~/.axon/session.token (chmod 0600 — only your user can read it).

Your agent never sees the bearer token, the unlock passphrase, or the private key. It calls MCP tools; the MCP server enforces policy + signs through the daemon.

Test the connection​

In your agent runtime, ask it:

Use the axon MCP server to check my balance.

If Axon's connected, the agent will call get_balance and report the demo-mode synthetic balance. If not, you'll see a connection error — usually the daemon isn't running. Start it with axon (or open the desktop app).

Next​