MCP server

Connect from Claude (OAuth)

The remote endpoint supports OAuth, so Claude Code and claude.ai custom connectors connect without a pasted key. You log in to ApexApi and approve once; approving creates an ak- key named MCP: <client> on your account that the connector uses. Usage bills to your prepaid balance, and you can revoke the connection any time from apexapi.dev/keys.

Claude Code

claude mcp add --transport http --scope user apexapi https://api.apexapi.dev/mcp

Then run /mcp in Claude Code, choose apexapi, and click Authenticate. A browser opens to the ApexApi consent screen; approve, and the tools become available.

--scope user registers the server for your whole machine, so you authorize once and every project sees it. Without it Claude Code defaults to local scope, which is per directory, and you would repeat this in each new project.

claude.ai

Settings → Connectors → Add custom connector → URL https://api.apexapi.dev/mcp → Connect → approve on the ApexApi screen.

Remote endpoint (bearer key)

For MCP clients that take a bearer key directly instead of doing OAuth. Get a key at apexapi.dev/keys, then point the client at https://api.apexapi.dev/mcp with header Authorization: Bearer ak-....

Responses use MCP Streamable HTTP framing (SSE). Clients like Claude Code handle this natively; it is not a plain-JSON REST endpoint.

Claude Code: claude mcp add --transport http --scope user apexapi https://api.apexapi.dev/mcp --header "Authorization: Bearer ak-..."

Local (stdio)

Runs the apexapi-mcp package locally over npx. Get a key at apexapi.dev/keys, then add to your MCP client config:

{
  "mcpServers": {
    "apexapi": {
      "command": "npx",
      "args": ["-y", "apexapi-mcp"],
      "env": { "APEXAPI_API_KEY": "ak-..." }
    }
  }
}

Claude Code: claude mcp add --scope user apexapi -e APEXAPI_API_KEY=ak-... -- npx -y apexapi-mcp