Connect your client

Config blocks for Claude Desktop, Claude Code, Cursor, VS Code and any other MCP client. Copy, paste, restart.

One URL, one header. Copy the block for your client, restart it, and your agents appear as tools.

Before you start

Check which agents that key exposes — by default, the ones you published. See Tools and scopes.

Have some credits. A tool call with an empty balance fails politely, but it fails.

Claude Code

One command, no file editing:

claude mcp add --transport http amnt https://www.amnt.io/api/mcp \
  --header "Authorization: Bearer amnt_sk_..."

Then /mcp inside Claude Code lists the server and its tools.

Claude Desktop

Newer builds add remote servers from Settings → Connectors → Add custom connector — paste the URL and the header there. If your build has no such screen, edit the config file instead:

claude_desktop_config.json

{
  "mcpServers": {
    "amnt": {
      "url": "https://www.amnt.io/api/mcp",
      "headers": {
        "Authorization": "Bearer amnt_sk_..."
      }
    }
  }
}

Where the file lives

# macOS
~/Library/Application Support/Claude/claude_desktop_config.json

# Windows
%APPDATA%\Claude\claude_desktop_config.json

If your build only speaks stdio

{
  "mcpServers": {
    "amnt": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://www.amnt.io/api/mcp",
        "--header", "Authorization: Bearer amnt_sk_..."
      ]
    }
  }
}

Quit and reopen the app — a reload is not enough.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "amnt": {
      "url": "https://www.amnt.io/api/mcp",
      "headers": {
        "Authorization": "Bearer amnt_sk_..."
      }
    }
  }
}

.cursor/mcp.json for one project, ~/.cursor/mcp.json for every project. Cursor shows the server under Settings → MCP with a green dot and the tool count once it connects.

VS Code

.vscode/mcp.json

{
  "servers": {
    "amnt": {
      "type": "http",
      "url": "https://www.amnt.io/api/mcp",
      "headers": {
        "Authorization": "Bearer ${input:amnt_key}"
      }
    }
  },
  "inputs": [
    {
      "id": "amnt_key",
      "type": "promptString",
      "description": "amnt API key",
      "password": true
    }
  ]
}

The inputs block means the key is typed once and never committed — worth copying into any config that lives in a repo.

Any other client


URL	`https://www.amnt.io/api/mcp`
Transport	Streamable HTTP (POST, JSON responses)
Header	`Authorization: Bearer amnt_sk_...`

Verify without a client

Ask for the tool list by hand

curl -X POST https://www.amnt.io/api/mcp \
  -H "Authorization: Bearer $AMNT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

A list of tools means the server and your key are both fine, and anything still wrong is on the client side.

Keep the key out of git

A committed .cursor/mcp.json or .vscode/mcp.json with a live key is a key anyone with repo access can spend. Use the VS Code inputs pattern above, or add the file to .gitignore.