FAQ
Frequently asked questions
Short, honest answers. For detail, follow the links to the full pages.
A word you do not know? Words you will meet
Common questions
What is Aki MCP Server?
A free, open-source program you run on your own computer that gives AI apps 38 tools for your files, terminal, browser, git and SQLite, only inside the folders and commands you allow. MCP is the standard those apps use to call tools. AI apps on this computer connect directly (127.0.0.1 or stdio, no tunnel); web AI apps connect through an optional public address and sign in with your passphrase.
Is it free?
Yes. It is open source under the MIT license and free to self-host.
Which AI apps are supported?
On this computer (over 127.0.0.1 or stdio): Postman, Cursor, Claude Code, the Claude app, AGY and Codex. On the web (over a public address): Claude, ChatGPT and Grok are the most dependable; Notion and ClickUp sign in with the passphrase too; Buda connects with the access token in a header; any other AI that signs in with OAuth connects once you add its sign-in address in the panel; Gemini signs in again but is experimental: tool use was unreliable in tests.
Do I need to keep my computer on?
For remote use, yes: your machine must be powered on with the server running. Closing the terminal stops it.
What can the AI access by default?
By default the file root is your whole home folder plus ~/.aki and ~/.claude, and the shell allowlist is inspection-first with a few pre-approved dev helpers that can write. Narrow the folders and review the allowlist in the panel on a sensitive machine.
Do I need a desktop app?
No. Aki MCP Server runs from one terminal command and works with the web AI apps and AI apps on this computer you already use.
What operating systems does it run on?
Windows, Linux and macOS with Node.js 22. On Windows you also need Git for Windows (or WSL) on PATH.
Does it work with the Claude desktop app?
Yes: since 3.1.0 the Claude app connects to Aki MCP Server over stdio, with no token to paste. Web AI apps use the chat plan you already pay for, and any browser profile or account can reach the same machine.
Can I run it on two computers and tell them apart?
Yes, from 4.0: give each one its own Display name in the panel (for example MacMCP and WinMCP), and its tools get their own prefix (mac__run_cmd). Keep the default name and nothing changes.
Does the allowlist stop prompt injection?
Not on its own. It keeps a careless or overeager AI on the commands you approved, but the file tools can edit AkiMCP’s own settings inside the default folders and widen it. Connect only AI apps you trust, keep the passphrase and token private, narrow the folders, and check the call log.
How do I expose it over HTTPS?
Only web AI apps need it; AI apps on this computer connect directly (127.0.0.1 or stdio). For web AI apps, Tailscale Funnel is the free default: install Tailscale, sign in, and turn Funnel on once with the link AkiMCP prints. A Cloudflare named tunnel or your own HTTPS origin also work.
How do I revoke access?
Open the panel’s “Security & connection limits” section, press Revoke & roll on the client (Delete if it never got a token; Remove only just signs it out). If a secret may have leaked, use Roll & sign out all clients so every AI reconnects with the passphrase.
Can someone guess my passphrase?
Guessing is throttled: 5 rejected credentials in 60 seconds block that caller for 15 minutes with a 429, and a security log (the panel’s “Logs” section) records the attempts. Your own valid token is never blocked. The limits are editable in the panel’s “Security & connection limits” section.
How do I see who is connected?
The panel’s “Security & connection limits” section lists every client with first seen, last approval and last token grant, and the addresses active since the last restart; the “Logs” section holds the newest 200 security log lines.
Does Aki MCP Server log what the AI does?
Yes for calls over HTTP: the panel’s “Logs” section writes one JSON line per tool call to tool-calls.jsonl in the data folder: time, client, tool and op, window and port, ok or an error code, duration and server version. It never writes the arguments, text, script or URL the AI passed, and it records only the names of request headers, never their values. Basic (the default) keeps a short error code; Detail adds the full error text, the chat acted on and a hash of eval expressions. A file rolls at the size cap (16 MB by default) and old files are deleted after the keep days (40 by default); both are editable in that section. Apps that start AkiMCP over stdio (the Claude app, AGY) are not logged.
How can a local app get the access token?
Send GET /api/access-token to the panel (port 9998 by default) with the per-launch panel token in the x-panel-token header, and it returns the shared access token as {accessToken}. It answers on loopback only and sends no CORS header, so a web page cannot read it. It adds no new capability: whoever holds the panel token can already see the access token in the panel.
How does a stdio client start it?
With npx -y @akinet/akimcp --stdio, which serves the same tools over stdin/stdout with no gateway, tunnel or token, so any client that starts MCP servers itself can spawn it. The package also ships a server.json record (name io.github.lacvietanh/akimcp) that describes it for the MCP Registry and names this command.
How many tools are there?
38 tools, from files and shell to browser automation, git, SQLite, background tasks and Postman control. See What’s new for the latest changes.