Connect

Connect your AI app to Aki MCP Server

Pick your app below. Every web AI that signs in with OAuth self-registers, so there is no Client ID or Secret to paste; ChatGPT needs Developer mode on first and Notion needs custom MCP servers enabled. Buda takes the access token in a header instead. Any other AI that signs in with OAuth connects once you add its sign-in address in the panel. Claude and Grok are the most dependable today; Gemini is experimental and not recommended.

A word you do not know? Words you will meet

Which kind of AI app do you use?

An app on this computer

Cursor, Claude Code, the Claude app, Postman, AGY, Codex, or any app that takes an MCP JSON. They connect straight to this computer over 127.0.0.1 or stdio: no public address and no passphrase. Jump to the section that names your app below.

An app on the web

Claude.ai, ChatGPT, Grok, Notion, ClickUp, Buda, Gemini, or any other AI that signs in with OAuth. They reach your computer through a public HTTPS address, so turn one on first (see Get started), then sign in with your passphrase. Buda takes the access token in a header instead.

A web chat with no connector menu

If the chat can send HTTP requests (a code sandbox, a fetch tool, a Postman agent), it connects with a temporary token instead of a sign-in. Jump to the section below.

Before you connect

  • Your server is running (see the Get started page). For a web AI app, the public address is on too.
  • Grab the Display name (AkiMCP unless you renamed it), the MCP URL and the passphrase from the panel’s “Connectors” section (or ~/.aki/mcpsv/passphrase.txt).
  • Paste the two-line instruction from the panel’s “Instructions” section into your AI once. It is static, so it never needs re-pasting.

Coding tools on this computer: 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, and the link to AkiMCP needs no internet. Use the literal 127.0.0.1, not localhost.

  • Cursor: click Apply to Cursor on the panel’s Cursor tab. It writes ~/.cursor/mcp.json with the current token and leaves your other servers alone; after Roll token, click Apply again.
  • Claude Code: click Apply to Claude Code on the panel’s Claude Code & app tab. It registers the server for every project with the current token, replacing any old entry; after Roll token, click Apply again.
  • Codex: click Apply on the panel’s Codex tab. It replaces the [mcp_servers.akimcp] table in ~/.codex/config.toml in place and removes an old aki-mcp table; after Roll token, click Apply again.
  • From another computer: the Cursor, Claude Code and Codex tabs each have a From another computer block with a snippet using your public address plus /mcp and the Bearer token. The token is stored in plain text on that computer, and after Roll token you paste the new snippet there. Not yet checked against a live second computer. If you paste a snippet by hand, delete any old aki-mcp or aki-mcp-sv entry; the server key is now akimcp, so Claude Code tool names are mcp__akimcp__*, and an allow-list naming mcp__aki-mcp__* must be renamed.

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

Any other app that takes an MCP JSON

Most apps with an MCP settings screen accept the same JSON: an mcpServers entry with a URL and a header. The panel keeps it ready in one tab.

  1. 1In the panel’s Local · direct group, open Any MCP app (the first tab) and click the JSON to copy it. It points at http://127.0.0.1:9999/mcp with your access token.
  2. 2Paste it where your app adds an MCP server, keeping any servers already there.
  3. 3For an app on another computer, copy the second JSON instead: it uses the public address from section 0, and its token sits in plain text on that computer until the next Roll token.

Postman and Cursor take this JSON as is; their own tabs add Launch for Postman and Apply for Cursor. After Roll token, copy the JSON again.

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.

Claude desktop app

Set up separately from Claude Code; one does not connect the other. The app starts AkiMCP over stdio with no token, so Roll token changes nothing for it.

  1. 1In the Claude app, open Settings → Developer → Edit Config.
  2. 2Merge the entry from the panel’s Claude Code & app tab under mcpServers in the claude_desktop_config.json it opens. The tab fills in your path.
  3. 3Quit the app completely and open it again.

If the server fails to start, replace node with the full path from which node (Windows: where node).

Apps that start the tools themselves (stdio)

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’s Display name, AkiMCP by default) 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.

The connector belongs to your Claude account: claude.ai, the Claude app and the mobile app all reach it from Anthropic’s cloud, so it needs a public ingress even on the computer running AkiMCP. On that computer, Claude Code and the Claude app can connect locally instead, with no ingress.

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 (the ChatGPT tab of the panel has a Download icon button for the AkiMCP icon).
  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

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 panel’s Display name, exactly (AkiMCP by default): the pasted instruction keys off it. Set Server URL to the MCP URL.
  3. 3Click Connect and enter the passphrase to approve.

If a Grok update moves its sign-in address and the connection is refused, the new address shows in the panel’s Other AI (sign-in) tab, where one click adds it.

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.

ClickUp

ClickUp needs a public address. It registers itself through OAuth, so there is no Client ID, secret or token to paste. After Roll token, reconnect it once from ClickUp.

  1. 1In ClickUp, open Settings → App Center → MCP Servers → Connect an MCP Server.
  2. 2Set Name and URL from the panel, Authentication Method = OAuth, leave Advanced configuration closed, then click Next.
  3. 3Enter the passphrase in the tab ClickUp opens and approve.

ClickUp Brain then calls the tools when a request needs them, without a mention.

Buda

Buda needs a public ingress and connects with the shared access token in a header, not the passphrase. The panel’s Buda tab holds every value ready to copy.

  1. 1In Buda, open Agent Settings → your agent → Integrations → Add MCP server.
  2. 2Set Name from the panel, Connection type = Remote HTTP, HTTPS endpoint = the MCP URL.
  3. 3Under Authentication headers, add Authorization with the value Bearer YOUR_ACCESS_TOKEN from the panel.
  4. 4Click Save, then start a new chat to load the tools.

After Roll token, paste the new header value into Buda again. This setup has not been tried in a live Buda session yet.

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, with no tunnel and no internet for that link. 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).

Another AI that signs in with OAuth?

For an AI that has its own custom connector and signs in with OAuth but has no tab of its own in the panel. Like every web AI, it needs a public address. Since 4.2 you add its sign-in address in the panel once, with no AkiMCP update.

  1. 1In your AI, add a custom connector with the MCP URL from the panel.
  2. 2If it cannot connect, open the panel’s “Connectors” section → Web · needs ingress → Other AI (sign-in). Its refused sign-in address shows under Refused since AkiMCP started: click Add, or Add as prefix to allow every address under that folder. An address AkiMCP cannot use (http, localhost, an IP address) shows the reason instead.
  3. 3Connect again and enter the passphrase. The confirmation page names where the sign-in returns, so check that address before you approve.

If nothing shows as refused, the AI never reached AkiMCP: check the public address first (see Get started). You can also type an address into the form at the bottom of the tab (exact, or a prefix ending in /), or write it into setting.json under oauth.callbacks; the change applies to the next sign-in, with no restart. Remove stops new sign-ins through that address; to cut off an AI already connected, use Revoke & roll on it in the panel’s “Security & connection limits” section, or Roll & sign out all clients. Tested end to end on a test server, not yet with a real AI.

Your AI app has no connector menu?

If the chat can send HTTP requests, it becomes the MCP client itself with plain HTTP requests: the provider needs no custom MCP support. It signs in with a temporary token instead of the passphrase.

  1. 1In the panel’s Web · needs ingress group, open the Any HTTP chat tab and click Mint temp token & copy kickoff. The block holds the guide link, the MCP URL and the token.
  2. 2Paste the block into the chat, then give it your task.
  3. 3When the work is done, tell the chat to revoke its token, or click Revoke beside it in the panel.

The token lasts 4 hours; +30 min beside it in the panel adds half an hour, as often as needed, and Last used shows when and from where it was used. A server restart revokes it; your shared token and other apps keep working. The protocol the chat follows: the AkiMCP HTTP guide for web chats (v1).

Gemini (experimental)

Paid Gemini tier only, and not recommended. In 3.1 it signs in with the passphrase again (not yet checked live); in earlier tests it connected but did not use the tools reliably.

  1. 1Open Gemini’s custom connected apps (Gemini → paid subscriptions → Custom apps), paste the MCP URL and click Next.
  2. 2Enter the passphrase on the AkiMCP authorization page and click Approve. Gemini registers itself, so there is nothing else to paste; the pre-issued Client ID/Secret that akimcp prints at start is only an optional fallback.
  3. 3Ignore Gemini’s Copy redirect URI button: Google’s redirect addresses are already allowlisted on the server. This flow has not been tried in a live Gemini session yet.

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

Running AkiMCP on more than one computer? Name each one

Optional, from 4.0. A name of your own lets your AI apps list each computer apart. Keep the default, AkiMCP, and skip this section.

  1. 1At the top of the panel’s Connectors section, type a Display name. The Server ID and Tool prefix follow as you type: MacMCP gives macmcp and mac__run_cmd. Customize fields sets either one yourself.
  2. 2Click Save name, then restart AkiMCP.
  3. 3Reconnect it in every app. In Claude Code, Codex, Cursor and AGY, click Apply: it moves the entry to the new Server ID. In a web app, type the new Display name as the connector name. Claude asks Always allow again for each tool.

Set the default back (Reset to AkiMCP) before you install a 3.x version. AIObox connects claude.ai by itself only while the name contains AkiMCP. Renaming was checked by reading the code path, not against live clients.