Connect your coding agent to M1K3

$ brew trust round-tower/tap && brew install --cask round-tower/tap/m1k3
$ m1k3 connect claude

The first line is Homebrew: version 6 asks you to trust a third-party tap before it will install from one, and the cask then installs the nightly Developer ID build of M1K3 and symlinks m1k3 — the small command-line client that ships inside the app bundle — onto your PATH.

The second line writes the MCP entry for your agent. Swap claude for codex, cursor, vscode or zed; add --print to see the config without touching a file.

One switch, once

The MCP server is off by default, and it lives inside the app: open M1K3, then Settings ▸ Privacy ▸ MCP server. That is the whole setup. The same pane has a picker for all five agents with the snippet and a Copy button, if you would rather click than type.

Without Homebrew

Download the signed, notarized M1K3.dmg from GitHub Releases and drag it to Applications. Then either use the picker in Settings ▸ Privacy ▸ MCP server, or run the same command from inside the bundle:

$ /Applications/M1K3.app/Contents/Helpers/m1k3 connect claude

M1K3 needs an Apple Silicon Mac on macOS 26. It does not need an account.

Per agent

Five clients, and they genuinely differ — so connect does the safe thing for each and tells you which it did. These are the snippets m1k3 connect --print produces:

the two it edits keep every other server in the file, and get one .bak beside them the first time

Claude Code

$ claude mcp add --transport http -s user m1k3 http://127.0.0.1:4242/mcp

-s user registers it once for every project, which is the point of a resident.

Cursor — ~/.cursor/mcp.json

{
  "mcpServers": {
    "m1k3": { "url": "http://127.0.0.1:4242/mcp" }
  }
}

VS Code — ~/Library/Application Support/Code/User/mcp.json

{
  "servers": {
    "m1k3": { "type": "http", "url": "http://127.0.0.1:4242/mcp" }
  }
}

Codex — ~/.codex/config.toml

[mcp_servers.m1k3]
url = "http://127.0.0.1:4242/mcp"

Zed — ~/.config/zed/settings.json

"context_servers": {
  "m1k3": { "url": "http://127.0.0.1:4242/mcp" }
}

Zed's settings schema has moved more than once — check the shape against your Zed version. That, and Codex's TOML living in a file full of your own settings, is why those two print rather than write.

Tell your agent it's there

A connected server your agent never thinks to call is a wasted server. m1k3 agent-notes --write folds this block into the project's AGENTS.md — or CLAUDE.md, or any path you name. It is marker-fenced, so running it again replaces the block instead of stacking copies:

<!-- m1k3:begin -->
## M1K3 is the resident

M1K3 is a local, private assistant running on this Mac, reachable over MCP. It
holds the user's own documents and memories — so before you search the web, ask
it: `ask_m1k3` for a grounded answer, `search_knowledge` for the sources behind
one. Persist a durable fact with `remember` and it is there next session too.
`speak` narrates aloud, which is often kinder than a wall of text.

M1K3 can be down — a "disconnected" MCP server just means the app is closed.
Never block on it; carry on without it.
<!-- m1k3:end -->

Four lines an agent will actually obey beat a paragraph it skims. Run m1k3 agent-notes with no arguments to print it instead.

What your agent gets

Eighteen tools. The short version: it can ask a local brain, search your own documents, keep and recall facts across sessions, speak and listen, and put something on your todo list without ever taking it off.

The consent gates are deliberate and asymmetric: an agent can remember and it can forget_memory, but it can only ever propose a todo — accepting, completing and dismissing stay with the person.

What it will not do

• It will not answer another machine. The listener is pinned to 127.0.0.1 at the socket, never an interface address, so nothing on your network can reach it.
• It will not answer a web page. Requests whose Host header is not a loopback address are refused, and an Origin that is not a loopback page is refused too — the standard defence against a site using your browser to reach a server on your own machine.
• It will not run while M1K3 is closed. The server is part of the app. A "disconnected" MCP server almost always means the app is not open — which is why the resident block above tells your agent never to block on it. The m1k3 command opens the app itself and waits for the port.
• It will not ask for a password, because it has none. There is no token on the loopback server today: anything running as you on this Mac can call it while it is switched on. That is the same trust boundary as your shell, and it is the reason the server ships off by default.
• It will not write your config from the App Store build. That copy of m1k3 is sandboxed, so it can neither read ~/.cursor/mcp.json nor run claude for you. There, connect prints the config and says so. The Developer ID build — the DMG and the Homebrew cask — does the write.
• It will not serve two agents at once. One MCP client at a time, in this version: a second client connecting ends the first one's session.
• It will not send what your agent asks it anywhere. Retrieval, embeddings, inference and voice run on the Mac. M1K3's documented network crossings are unchanged by connecting an agent: a one-time model download you opt into, web tools that are off by default, and updates.

Frequently asked questions