v4.2.0

Aki MCP Server 4.2: connect any AI that signs in, keep secrets out of the chat

An AI that signs in with OAuth but has no tab of its own in the panel can now connect: its refused sign-in address shows in the panel, and one click adds it. No AkiMCP update needed. A key written in a project file such as .env now comes back as [redacted] instead of reaching the chat, and SQLite queries can only read. Still 38 tools.

Update, restart, reconnect once: only the sqlite_query description changed, so each app needs one reconnect to see it. If Claude asks, choose Always allow again for that tool.

1 · Your AI app

  • Claude web
  • ChatGPT
  • Grok
  • Notion
  • ClickUp
  • Buda
  • Gemini· experimental
  • Postman
  • Cursor
  • Claude Code
  • Claude app
  • AGY (Antigravity)
  • Codex

+12 more apps

“Read my project’s .env and tell me which services it uses”

2 · AkiMCP checks your limits

AkiMCP on your computer

Secret values hidden from the AIbuilt in
aki__read_text_file

3 · Your computer does the work

  • FilesNames listed; every key came back as [redacted]
  • Terminal
  • Browser
  • 1

    click to let a new AI sign in

    Add on its refused address, applied on the next sign-in with no restart

  • 6

    times in 5 releases a new AI needed an AkiMCP update

    Now it is an address you add in the panel

  • 5

    statement types sqlite_query runs

    SELECT, WITH, EXPLAIN, PRAGMA and VALUES; anything else is refused

  • 38

    tools, same as 4.1

    One description changed: sqlite_query

Connect any AI that signs in with OAuth

For an AI that has its own custom connector and signs in with OAuth but has no tab in the panel. Like every web AI, it needs a public address (panel section 0).

New

Add a refused sign-in address with one click

Add the AI’s connector with your MCP URL. If it cannot connect, open panel section 1 → Web · needs ingress → Other AI (sign-in): its address shows under Refused since AkiMCP started. Click Add, or Add as prefix to allow every address under that folder, then connect again and type the passphrase. The change applies to the next sign-in, with no restart. An address AkiMCP cannot use (http, localhost, an IP address) shows the reason instead.

New

Your own addresses, with Remove

The same tab lists the addresses you added, each with Remove, and a form to type one: exact, or a prefix ending in /. They live in setting.json under oauth.callbacks, which you can also edit by hand. Remove stops new sign-ins through that address; to cut off an AI already connected, use Revoke & roll on it in section 7 Clients, or Roll & sign out all clients.

Changed

The confirmation page says where the sign-in returns

Above the passphrase field, the page now shows the address the sign-in goes back to, and whether it is built in (with the AI’s name; for Gemini, that it goes through Google’s shared sign-in relay) or added in your panel. Check it before you type the passphrase.

Changed

A refused AI is told where to fix it

A refused registration answers invalid_redirect_uri with a line that says where in the panel to add the address, or why it cannot be added, or that the AI sent no address. Every sign-in also re-checks its address, so removing one in the panel takes effect for AIs that registered earlier too.

Secrets stay out of the chat

These work without any setting. Restart AkiMCP after updating for them to take effect.

Security

A key in a project file comes back as [redacted]

search_content, read_text_file and run_cmd (cat, grep) used to return a project .env as written. Now every result hides the value of a NAME=value line whose name has a part such as TOKEN, SECRET, KEY, PASSWORD, AUTH or COOKIE, and anywhere in the text: Telegram bot tokens, sk-, GitHub, Slack, Postman, Google and AWS keys, Bearer values, the password in a URL and PEM private keys. A $reference stays, so a script that reads a secret stays editable.

Security

An edit cannot overwrite a hidden value

Because the AI now sees [redacted] where the value was, write_file and edit_file refuse to write that marker into a file that holds a hidden value. The other lines stay editable.

Security

SQLite queries can only read

sqlite_query runs only a statement that starts with SELECT, WITH, EXPLAIN, PRAGMA or VALUES, after any blanks and comments. Before, a comment in front let VACUUM INTO write a new database file, or ATTACH open one outside your allowed folders.

Security

Sign-in files survive a crash

tokens.json, the retired-token list and passphrase.txt are now written whole or not at all, so a crash or a full disk cannot leave one empty. An empty passphrase.txt is replaced by a new passphrase instead of letting a blank one in.

Security

A sign-in address cannot climb out of its folder

Every sign-in address is read the way the browser will follow it: %2e%2e and similar tricks resolve before the check, and an address with #, a user name or a password is refused. Every built-in address still matches.

Browser tools say what really happened

For anyone who lets the AI drive Chrome.

Fixed

Typing goes only into a text field

chrome_interact type used to answer typed: true on a button, a select or a plain <div>, so the AI went on as if the text were in. Now only an input or a textarea takes the text, and anything else is refused as not a text field, so the AI picks the right selector.

Fixed

chrome_stop leaves other programs alone

After AkiMCP restarted and the Chrome it launched had closed, chrome_stop could signal another program that took the same process ID, and still answered stopped: true. It now signals only while the profile’s own lock and the process’s command line show it is that Chrome; otherwise it answers stopped: false with the reason.

From 4.1: lighter for every chat, steadier for long ones

Every app puts the full tool list into the AI’s context at the start of each chat, so a shorter list leaves more room for your own work. Long chats also stop losing their receipt.

Changed in 4.1

A tool list nearly 700 characters shorter

Text that repeated a tool’s inputs or said nothing the AI acts on is gone: the 38-tool list measured 36,751 characters instead of 37,428.

Fixed in 4.1

A long chat keeps its receipt

The server keeps the 200 rule receipts issued or used most recently, so a chat that keeps working is not refused because newer chats got receipts. A receipt that does drop out is refused as RULE_RECEIPT_EVICTED; fetch a fresh one.

Changed in 4.1

With AIObox, chrome_launch refuses

While AIObox runs, aki__chrome_launch opens nothing and answers aiobox_running with one next step: open the link from the AIObox window with aki__aiobox_write op=open_url, so the AI never acts from a profile signed in to another account.

New in 4.1

The rules tell the AI how to act in an AIObox window

While aki__aiobox is served, the aki__akidevrule_context result tells the AI to call aki__aiobox op=whoami first and act through aki__aiobox_write.

Upgrade notes

Upgrading from 4.1 or earlier?

The sqlite_query description changed in 4.2, so every app reconnects once. Coming from 4.0, the same reconnect also covers the 4.1 tool descriptions; from 3.2 or earlier, also take the 3.3 step below once.

  1. 1Update with the same command you used to install (below), then start it again.
  2. 2Reconnect AkiMCP in every app once, or start a new chat. In Claude, choose Always allow again for sqlite_query; coming from 4.0, also for the tools 4.1 changed: every tool that takes a receipt, plus akidevrule_context, aiobox, chrome_profiles, devtools_targets, port_status and read_text_file.
  3. 3From 3.2 or earlier: click Apply in the Claude Code, Codex and Cursor tabs so the entry moves to the akimcp key, and rename a Claude Code allow-list that names mcp__aki-mcp__ to mcp__akimcp__.
  4. 4Renaming later? Restart, reconnect every app, and set the default name back before you ever install a 3.x version.
# Global CLI
npm install -g @akinet/akimcp
akimcp
# From source
git pull && npm install && npm start

What changed under the hood

An AI whose sign-in address is not built in

BeforeRefused until an AkiMCP release added it

NowAdded in panel section 1 → Other AI (sign-in), from the next sign-in

The sign-in confirmation page

BeforeA passphrase field

NowThe return address, built in or added by you, above the passphrase field

A key in a project .env

BeforeReturned as written by search, read and cat

Now[redacted]; write and edit refuse to put the marker over it

sqlite_query

BeforeA list of refused first words; a comment in front slipped past

NowOnly SELECT, WITH, EXPLAIN, PRAGMA and VALUES run

Sign-in files on a crash or a full disk

BeforeCould be left empty; an empty passphrase file let a blank passphrase in

NowWritten whole or not at all; an empty passphrase file is replaced

chrome_stop after its Chrome closed

BeforeSignalled whatever held the old process ID, answered stopped: true

NowSignals only its own Chrome; otherwise stopped: false and why

chrome_interact type on a button or div

Beforetyped: true, nothing typed

NowRefused: not a text field

Receipts the server keeps (4.1)

BeforeThe 200 issued first; the oldest dropped out even in use

NowThe 200 issued or used most recently

chrome_launch while AIObox runs (4.1)

BeforeOpened the profile, then warned

NowOpens nothing: aiobox_running and one next step

Know the limits

A feature you can trust tells you where it stops.

  • An AI you add still needs a public address (panel section 0). An http, localhost or IP address cannot be added.
  • Remove stops new sign-ins only: an AI already connected keeps working until you Revoke & roll it in section 7 or use Roll & sign out all clients.
  • Adding an address was tested end to end against a test server, not yet with a real AI whose address is not built in.
  • Secrets are hidden by their shape: one under a neutral name (CHAT_ID=) or in another form (password: in YAML) still comes back as written, and an encoded copy (compressed or base64) is not recognized.
  • On Windows, chrome_stop has no way to check which program holds the process ID, so it stops as before.
  • Updating to 4.2 needs one reconnect in every app for the new sqlite_query description.
  • While AIObox runs, chrome_launch has no force flag: open the link from the AIObox window, or quit AIObox first.

Ready to try it?

See the panel in the live preview, read the full security model, or go straight to the install page.