Connect aimactok via MCP in 5 minutes

MCP (Model Context Protocol) lets Claude Code, Cursor, Continue, and Cline call any model through the aimactok BYOK gateway. You bring your own provider keys; aimactok adds routing, quota, and dashboard visibility.

ⓘ

What you'll need: an aimactok account, an active subscription (Free tier works for testing), and your own provider API key (e.g. sk-... from OpenAI). The aimactok Authorization header is your session JWT — not a payment token.

1. Create your account

Go to /account/register, confirm your email, then sign in at /account/login. Free tier includes 1,000 calls per calendar month — enough to verify the full MCP round-trip before upgrading.

⚠

Already have an account? Skip to step 3 — adding a provider key surfaces your aimactok_token in a yellow banner. Copy it the moment it appears — it's only shown once. This is your AIMACTOK_JWT for the config in step 4.

2. Pick a plan (or stay on Free)

From /account/billing, choose Free, Pro (10,000 calls/month), or Team (50,000 calls/month). Pro and Team are billed through PayPal subscriptions. Plan limits are checked on every MCP call.

✓

Free tier is enough to validate setup. If your first 3 test calls return data, you're done — upgrade only when you hit a real workload.

3. Add your provider API key

Go to /account/api-keys, click Add key, pick the provider (OpenAI / Anthropic / Google / DeepSeek / Alibaba / Mistral / xAI / MiniMax), paste your sk-... value, and save. aimactok stores only a SHA-256 hash — your raw key is never persisted.

4. Configure your MCP client

Pick your client and paste the config. The MCP endpoint is https://aimactok.com/mcp. Two headers go in: Authorization: Bearer <your-aimactok-jwt> (your session token, not a payment token) and X-API-Key: <your-provider-sk> (forwarded to the vendor for each call).

⚠

Token rotation: aimactok session tokens expire; regenerate from /account/dashboard if calls start returning 401. Provider keys can be rotated from /account/api-keys without re-editing client configs.

Claude Code

Edit ~/.config/claude-code/mcp.json (or use claude mcp add):

JSON

{
  "mcpServers": {
    "aimactok": {
      "url": "https://aimactok.com/mcp",
      "headers": {
        "Authorization": "Bearer <AIMACTOK_JWT>",
        "X-API-Key": "<OPENAI_SK_XXX>"
      }
    }
  }
}

Then restart Claude Code. Verify with claude mcp list — you should see aimactok with two tools (route and health).

Cursor

Open Settings → MCP → Add new global MCP server, paste:

JSON

{
  "mcpServers": {
    "aimactok": {
      "url": "https://aimactok.com/mcp",
      "headers": {
        "Authorization": "Bearer <AIMACTOK_JWT>",
        "X-API-Key": "<OPENAI_SK_XXX>"
      }
    }
  }
}

Cursor will show a green dot next to the server when ready.

Continue (VS Code / JetBrains)

Edit ~/.continue/config.json:

JSON

{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "name": "aimactok",
        "transport": {
          "type": "http",
          "url": "https://aimactok.com/mcp",
          "headers": {
            "Authorization": "Bearer <AIMACTOK_JWT>",
            "X-API-Key": "<OPENAI_SK_XXX>"
          }
        }
      }
    ]
  }
}

Cline (VS Code extension)

Cline reads the same MCP config as Claude Code. Install Cline → open MCP Servers panel → paste:

JSON

{
  "mcpServers": {
    "aimactok": {
      "url": "https://aimactok.com/mcp",
      "type": "http",
      "headers": {
        "Authorization": "Bearer <AIMACTOK_JWT>",
        "X-API-Key": "<OPENAI_SK_XXX>"
      }
    }
  }
}

5. Test with a natural-language call

From your MCP client, ask: "Use aimactok to summarize my last 3 PRs in one sentence each." The client will call the route tool with your preferred model. Within ~3 seconds you should see the response.

Verify the call landed in /account/dashboard — the Recent API calls table shows model, provider, token counts, latency, and HTTP status for every call.

⚠

If you see HTTP 401: the aimactok JWT expired. Regenerate from your dashboard. If you see HTTP 429: monthly quota hit — upgrade your plan or wait until the next calendar month. If you see HTTP 502/504: the upstream provider rejected your X-API-Key — rotate it from /account/api-keys.

Next steps

Browse supported models — 14 vendors, 35 models, latency benchmarks per edge
Edge routing explained — how requests pick a region
Self-host chat_v3.py — run your own gateway, point MCP at it
FAQ — quotas, billing, security

0. Get your MCP Subscription Token

You need a long-lived token (not the 15-minute session JWT) to put in your MCP client config. Issue it from your Dashboard → MCP Subscription Token section. The token looks like mcp_aimactok_v1_… and is shown once — copy it immediately. Use Rotate to invalidate + replace; Revoke to disable without replacing.

You also need your provider API key (e.g. OpenAI sk-…, Anthropic sk-ant-…, Google AIza…) — this is the upstream key the gateway forwards to. Manage them under API Keys.

One-click setup scripts

Skip the JSON below — these scripts write ~/.claude.json and ~/.config/cursor/mcp.json for you, with safe merge if a file already exists.

macOS / Linux

curl -fsSL https://aimactok.com/docs/mcp-setup/aimactok-mcp-setup.sh | bash

Windows (PowerShell)

irm https://aimactok.com/docs/mcp-setup/aimactok-mcp-setup.ps1 | iex

The script will prompt for your MCP Subscription Token and your provider API key, then write the config files and tell you to restart your MCP client.