Connect your AI client to Aki MCP Server

Before you connect

• Your server is running and Funnel is on (see the Install page).
• Grab the MCP Name (AkiMCP), the MCP URL and the passphrase from panel section 1 (or ~/.aki/mcpsv/passphrase.txt).
• Paste the two-line instruction from panel section 3 into your AI once. It is static, so it never needs re-pasting.

Local IDEs: Cursor, Claude Code, Codex

These run on the same machine, so they connect straight to http://127.0.0.1:9999/mcp with the shared access token from the panel. No tunnel, works offline. Use the literal 127.0.0.1, not localhost.

• Cursor: add an aki-mcp entry with url and an Authorization: Bearer … header to ~/.cursor/mcp.json.
• Claude Code: run claude mcp add --transport http aki-mcp http://127.0.0.1:9999/mcp --header "Authorization: Bearer YOUR_TOKEN".
• Codex: append an [mcp_servers.aki-mcp] table with url and http_headers to ~/.codex/config.toml.

Each panel tab under the Local group shows the snippet already filled in with your token.

AGY (Antigravity) CLI and IDE

AGY connects as a stdio command, so there is no URL and no token to paste. The panel sets it up for you.

1. 1In the panel’s AGY tab, click Apply to AGY CLI.
2. 2It registers akimcp in ~/.gemini/config/mcp_config.json and pre-allows mcp(akimcp/*) in ~/.gemini/antigravity-cli/settings.json, so the CLI stops asking per tool. It merges into what you have and is safe to re-run.
3. 3The Antigravity IDE reads the same mcp_config.json, so it connects too. It keeps its own per-tool approval prompt.

stdio clients

A client that starts MCP servers itself runs Aki MCP over stdin/stdout. There is no gateway, no tunnel and no token to set up.

# The command the client spawns
npx -y @akinet/akimcp --stdio

The package ships a server.json record (name io.github.lacvietanh/akimcp) that describes it for the MCP Registry and names this command.

Claude.ai web connector

Claude discovers OAuth by itself. No Client ID or Client Secret is needed.

1. 1Go to claude.ai → Settings → Connectors → Add custom connector.
2. 2Enter a Name (the panel suggests AkiMCP) and the Remote MCP server URL: https://your-machine.ts.net/mcp, then connect.
3. 3Enter the passphrase when Aki MCP opens its confirmation page.

ChatGPT web and mobile

Needs a ChatGPT plan that offers Developer mode (Plus, Pro, Business, Enterprise or Edu). ChatGPT self-registers, so there is no Client ID to paste.

1. 1Turn on Developer mode first, in ChatGPT → Settings → Security and login. OpenAI requires it to create a custom MCP app.
2. 2Create a connector in Settings → Connectors. Enter a Name and Description of your choice; the Icon is optional.
3. 3Under Connection, set Server URL to the MCP URL from the panel.
4. 4Tick I understand and want to continue, then Create.
5. 5On connect, enter the passphrase.

Read-only tools run without a confirmation prompt, while every tool that can write still asks. Which write tools ChatGPT allows depends on OpenAI’s current policy.

Grok

Verified and production-ready. Grok self-registers (DCR with PKCE), so the URL is the only thing to paste.

1. 1Open grok.com/connectors → New Connector → Custom.
2. 2Set Name to the MCP Name from the panel, exactly (AkiMCP): the pasted instruction keys off it. Set Server URL to the MCP URL.
3. 3Click Connect and enter the passphrase to approve.

Notion AI

Notion needs a public ingress and a workspace that allows custom MCP servers. It self-registers, so there is nothing to paste, and it keeps working after Roll token.

1. 1Enable custom MCP servers in your Notion workspace settings (a workspace admin may have to).
2. 2Open notion.so/my-connections and add a Custom MCP server with the MCP URL from the panel.
3. 3Enter the passphrase when Aki MCP opens its confirmation page.
4. 4Add the connection inside an agent, then republish the agent so the published agent can use it.

Connect Notion with the passphrase, never by pasting the access token as a bearer: that copy stops working on every Roll token.

Postman AI Agent

Postman runs on the same machine, so it connects straight to the local engine at http://127.0.0.1:9999/mcp — zero latency, offline, no tunnel. Postman has no OAuth redirect for third-party MCP servers, so you paste a minted Bearer token instead.

1. 1In the panel’s Postman tab (under the Local group), click the filled JSON to copy it. It targets the loopback URL http://127.0.0.1:9999/mcp and carries a real access token (not the passphrase).
2. 2In Postman, add a new MCP server under Settings → Connected Accounts and paste the JSON.
3. 3Still in the Postman tab, click Launch to start Postman, then Send now to post the short instruction into the open chat. Turn on Auto-inject if you want it sent into every new chat (off by default).

Gemini (experimental)

Paid Gemini tier only, and not recommended. The connection works, but tool use is unreliable today.

1. 1Open Gemini’s custom connected apps (Gemini → paid subscriptions → Custom apps) and set the custom app link to the MCP URL.
2. 2Under Advanced Settings, paste the Client ID and Client secret that akimcp prints in the terminal at start (the OAuth Client ID and OAuth Client Secret lines; they are also in ~/.aki/mcpsv/oauth-client.json). Gemini is the one client that still needs them.
3. 3Ignore Gemini’s Copy redirect URI button: the redirect is already allowlisted on the server.
4. 4On Continue, enter the passphrase to approve.

In repeated testing Gemini accepted the connection but did not reliably discover or drive the tools. Prefer Claude, Grok, or ChatGPT for now.