Phaedo MCP

Phaedo MCP server (phaedo-mcp)

Phaedo learns how you write, work and decide, and keeps that profile on your phone. This server lets your AI apps use it: Claude Desktop, Claude Code, Cursor, and any other app that supports MCP. With it, they can:

• Answer the way you like — your preferred length, tone and format, without you repeating it in every chat.
• Check with you before acting — an AI agent asks Phaedo whether you'd want it to go ahead. When it's unsure, your phone gets an approve / deny card.
• Learn from your answers — each approve or deny teaches it how you want work handled when you're not watching.
• Get your signature for purchases — you sign a spending permission on your phone with Face ID; the agent never holds the key.

Your profile comes from your phone encrypted. The copy kept on this computer, for when your phone is offline, is encrypted too.

What you need

1. A profile, from either:

• the Phaedo phone app — your full profile lives there. The app isn't open to the public yet; phaedo.so has a link to hear when it is.
• your own Claude Code sessions — no phone needed. Phaedo builds a starter profile on this computer from how you work in Claude Code (see *Install*).

1. Node.js, free from nodejs.org (the LTS button), for Claude Code and other apps. Claude Desktop brings its own.

With neither, there is no profile, and the server says so plainly rather than guessing. You can still try Phaedo with a made-up example profile.

Install

Claude Code (and Cowork) — run these two commands in Terminal:

claude plugin marketplace add phaedo-labs/phaedo-mcp

claude plugin install phaedo@phaedo

Then start a new Claude Code session. That's all: Phaedo loads your profile at the start of each session, checks with you before Claude merges, deploys or publishes, and learns from how you work. Without the phone app, it builds a starter profile from your own sessions (for example, that you want short answers without headers). It starts thin and grows as you work. In Claude Code, type /phaedo:status to see how far along it is, and /phaedo:pair to pair the phone app.

Claude Desktop — download phaedo.mcpb and double-click it. Claude Desktop shows what it installs and asks you to confirm. Node.js comes with Claude Desktop, so nothing else is needed. Desktop uses the same profile and pairing as the Claude Code plugin on this computer.

Other apps (Cursor and others) — see *Use your own profile in other apps* below, or the manual setup under *Reference*.

What Phaedo reads stays on this computer: each Claude Code session is reduced to counts (like "asked for a shorter answer, 4 times"), and the text itself is discarded. If you pair the phone app later, your full profile replaces the starter one and keeps what it learned.

Try it with the example profile (no phone needed)

This loads a made-up person's profile, so you can see what Phaedo adds before you have your own.

Claude Code — run this in Terminal (it applies to all your projects):

claude mcp add -s user phaedo -e PHAEDO_FINGERPRINT=sample -- npx -y phaedo-mcp

Claude Desktop — open Settings → Developer → Edit Config, add the phaedo entry below inside mcpServers, save, then quit and reopen Claude Desktop:

{

"mcpServers": { "phaedo": { "command": "npx", "args": ["-y", "phaedo-mcp"], "env": { "PHAEDO_FINGERPRINT": "sample" } } } }

If Claude Desktop reports that the server failed to start, it couldn't find npx. Replace "npx" with the full path that this prints:

which npx

Then start a new chat and ask: *"Load my Phaedo profile."* To stop using the example, delete the env line in Claude Desktop, or in Claude Code run claude mcp remove -s user phaedo and add it again without -e …. The server will then tell you there's no profile until you pair your phone.

Use your own profile in other apps (with the phone app)

1. Get this folder. On the GitHub page, click Code → Download ZIP, unzip it, and open the mcp folder inside.
2. Run the installer.

• macOS: double-click `installers/macos/Install Phaedo MCP.command`. If macOS says it can't be opened, right-click it and choose Open.
• Windows: double-click `installers/windows/Install Phaedo MCP.bat`.
• Linux: run bash installers/linux/install-phaedo-mcp.sh.

It adds Phaedo to Claude Desktop, Cursor and Claude Code — keeping your other settings, and backing each file up first — then starts pairing. (In Claude Code and Claude Desktop, the plugin and the .mcpb above are simpler; use one route per app, not both.)

1. Pair with your phone. Open Phaedo on your phone. On the same Wi-Fi, approve "Phaedo MCP Server" and check that the code matches the one in Terminal. On a different network, tap Pair with code and type the code Terminal shows.
2. Quit and reopen your AI apps, start a new chat, and ask: *"Load my Phaedo profile."*

You can disconnect this computer at any time from the Agents screen on your phone.

Learn from your ChatGPT or Claude history

npm run import -- ~/Downloads/your-export.zip

Get the file from ChatGPT (Settings → Data controls → Export data) or Claude (Settings → Privacy → Export data); each emails a zip. Phaedo reads the last year of conversations (--all for everything, --dry-run to count first) through the same on-device detectors as Claude Code capture, keeps only the counts, and discards the text — delete the export afterwards. Importing the same file again replaces, never doubles. Paired: the patterns go to your phone. Not paired: they become your starter profile. In the Claude Code plugin, it's /phaedo:import.

See what Phaedo learned — keep it or remove it

npm run learned

Lists what Phaedo inferred from how you work (not your interview answers or your rules), one plain sentence each, and flags pairs that disagree ("favor speed" vs "favor quality"). npm run learned -- --remove 3,5 stops those shaping answers and decisions on this computer — the list is applied every time the profile loads, so a pattern your sessions keep showing stays removed. --keep all marks the rest reviewed; --forgotten and --restore undo. /phaedo:status says when there are new things to look at. To remove something from the phone's profile itself, use the Phaedo app. In the Claude Code plugin, it's /phaedo:learned.

Give agents without MCP the same profile

Codex, Copilot CLI, Gemini CLI and Antigravity each read a personal instructions file at the start of every session. One command writes a short version of your profile (your rules and how you like answers) into each one found on this computer:

npm run rules

It goes into ~/.codex/AGENTS.md, ~/.copilot/copilot-instructions.md and ~/.gemini/GEMINI.md (shared by Gemini CLI and Antigravity), inside a marked block; the rest of each file is left alone. Cursor has no personal file, so name a project: npm run rules -- --project ~/code/app writes .cursor/rules/phaedo.mdc and keeps it out of git. Phaedo refreshes these files whenever a Claude Code session starts with Phaedo on, and only those you set up. npm run rules -- --dry-run shows the text first; npm run rules -- --remove takes it out. In the Claude Code plugin, it's /phaedo:rules.

---

Reference

Everything below is for developers: the full tool list, how the profile is loaded, and the test suite.

The server implements the MCP binding of the Anamnesis protocol (docs/protocol/mcp-binding.md §3.1):

The projection is rendered by the same context-block.js the extension injects, so MCP injection is byte-identical to web injection.

Status

The phases below track the fingerprint source (how the server obtains the fingerprint). The consultation, real-time escalation, act-as-me / delegation, and receipts-audit surfaces (the tools table above) shipped on top of these across the 0.2.x line, and the §8.3 signing pair in 0.3.0 — see CHANGELOG.md.

Install 0.3.0 or later. 0.2.0, 0.2.1 and 0.2.2 were published with three

modules missing from the package, so they exit with ERR_MODULE_NOT_FOUND

instead of starting. 0.3.0 is the first working release since 0.1.1, and

test-package-closure.mjs now boots the packed tarball in CI.

• Phase 1a (this cut): reads the fingerprint from a local JSON file (see *Fingerprint source*). Lets injection work in a real client today, no crypto.
• Phase 1b-i (done): the spec-faithful key boundary — authorize → pull /v1/profile → unwrap the §7.2 envelope from the paired phone, reusing the repo crypto modules (protocol/envelope/kdf/identity.js) in node. The decrypted fingerprint stays in memory (never written to disk). Auto-selected when a pairing record is configured (see *Fingerprint source*). Plan + decisions: ../docs/roadmap/mcp-1b-plan.md.
• Phase 1b-iii (done): encrypted at-rest cache — a successful phone pull caches the fingerprint as ciphertext under a server-held key; when the phone is unreachable the server serves that cache, so it works phone-absent (frictionless default; mirrors the extension's Option C — defense-in-depth, NOT phone-gated). State dir defaults to ~/.phaedo-mcp/ (override PHAEDO_MCP_STATE_DIR); holds a 0600 key file + ciphertext-only cache. Revocation is honored: if the phone *rejects* this client (revoked / invalid credentials → 4xx), the cache is purged and the pull fails — a revoked agent can't keep serving a cached copy. The cache only covers the phone being genuinely *unreachable* (network/timeout). v1 caveat: the raw key is on disk (weaker than the extension's non-extrac