Log inSubmit server
Phaedo MCP logo

Phaedo MCP

Injects a user-owned cognitive fingerprint into MCP sessions and supports consultations, policy checks, and phone-based escalation.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Phaedo MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "phaedo-mcp-2": {
      "command": "npx",
      "args": [
        "-y",
        "phaedo-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

The install command started, but didn't respond the way we expected when we tried to talk to it.

npx -y phaedo-mcp

initialize succeeded but no response to tools/list.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1d ago.

Overview

phaedo-mcp carries a user-owned cognitive fingerprint into MCP clients, injecting it at session start and answering agent consultations at decision points. Consultations return calibrated proceed, clarify, escalate, decline, or abstain signals under user-authored deference policies. Blocking decisions can be sent to a paired phone for live approval, denial, or modification, with an encrypted local audit trail. Use it when an agent needs to reflect a person's working preferences without exposing the fingerprint's underlying structure.

Use cases

  • Inject a user's working preferences into an MCP session
  • Ask whether a delegated action should proceed
  • Escalate uncertain or blocking decisions to a paired phone
  • Apply explicit deference policies to agent actions

Key features

  • Session-start fingerprint injection
  • Proceed, clarify, escalate, decline, and abstain signals
  • User-authored deference policies
  • Real-time phone escalation
  • Encrypted local audit trail
  • Local stdio execution

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

11/11 checks healthy over the last 53d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9d ago via OSV.dev · phaedo-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads2.4kPackage downloads in the last 30 days.
Last commit2d agoMost recent push to the default branch.
Install checkInconclusiveStarted but did not complete the MCP handshake in our test.

How Phaedo MCP works

What phaedo-mcp does

phaedo-mcp connects MCP-compatible AI clients with a portable Phaedo cognitive fingerprint. The fingerprint represents communication style, working style, and decision patterns, and is used to provide context at the beginning of a session. The server also handles consultations when an agent reaches a decision that may depend on how the user would act.

A consultation produces a signal such as proceed, clarify, escalate, or decline, along with confidence. When the available information does not support a reliable answer, the server can return an abstention signal instead of guessing. User-authored deference policies take priority over inferred behavior, and explicit standing authorizations are auditable.

How it works

The reference server is published as phaedo-mcp on npm and communicates with MCP clients over stdio. Running npx phaedo-mcp is the general-purpose launch path. Claude Code has a plugin that includes the server and hooks, while Claude Desktop can use the packaged desktop bundle.

The full fingerprint is supplied by the Phaedo phone app and learned on-device from the user's activity. The Claude Code plugin can create a starter profile locally when the phone-based profile is unavailable. A sample profile can be selected with PHAEDO_FINGERPRINT=sample for testing. If no profile is available, the server reports that condition rather than generating an inferred identity.

For blocking signals, the server can contact a paired phone in real time. The user can approve, deny, or modify the requested action. Those overrides contribute to the delegated “act-as-me” behavior. Communications between a computer and paired phone are end-to-end encrypted, and the relay carrying them cannot read them.

Setup and configuration

For Claude Code, add the Phaedo marketplace and install the Phaedo plugin:

Terminal
claude plugin marketplace add phaedo-labs/phaedo-mcp
claude plugin install phaedo@phaedo

For Claude Desktop, download desktop/phaedo.mcpb and open it. Other MCP clients can launch the server with:

Terminal
npx phaedo-mcp

Set PHAEDO_FINGERPRINT=sample when a made-up example profile is needed. Pairing, policy configuration, receipts, and the agreement metric are covered by the server's companion guides.

Tools and capabilities

  • Injects a cognitive fingerprint at session start.
  • Answers agent consultations with calibrated decision signals.
  • Applies user-defined deference policies and explicit authorizations.
  • Abstains when the fingerprint lacks sufficient coverage.
  • Escalates blocking decisions to a paired phone.
  • Records an encrypted audit trail on the device.
  • Uses user overrides to inform delegated-work behavior.

Limitations and notes

The learning pipeline that builds fingerprints is separate from this open repository. The phone app provides the full learned profile and is not publicly available. The open portion contains the fingerprint standard, schemas, MCP binding, conformance suite, and reference server for consuming and interoperating with fingerprints.

The server exposes consultation signals rather than the internal fingerprint structure. Fingerprints are stored on user devices in encrypted form, and the server does not keep plaintext fingerprint data at rest. The Phaedo name and logo are trademarks.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Phaedo MCP

phaedo-mcp is an MCP server that connects AI clients to a user-owned Phaedo cognitive fingerprint. It injects that profile at session start, answers consultations with proceed, clarify, escalate, decline, or abstain signals, and can escalate blocking decisions to a paired phone for approval, denial, or modification.

Run `npx phaedo-mcp` for an MCP client that supports stdio. Claude Code users can install the Phaedo plugin from its marketplace, while Claude Desktop users can download and open `desktop/phaedo.mcpb`.

Yes, if Cursor is configured to run MCP servers over stdio. Launch it with `npx phaedo-mcp`; the server is intended for MCP clients beyond the specifically packaged Claude Code and Claude Desktop integrations.

Yes, blocking signals can be escalated in real time to a paired phone. You can approve, deny, or modify the action, and those overrides inform the delegated act-as-me channel.

It reports that no profile is available instead of guessing. Claude Code can build a starter profile locally, and `PHAEDO_FINGERPRINT=sample` selects a made-up example profile for testing.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewPhaedo MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/phaedo-mcp-2?style=directory)](https://allmcps.com/mcp/phaedo-mcp-2)
HTML Embed
<a href="https://allmcps.com/mcp/phaedo-mcp-2"><img src="https://allmcps.com/api/badge/phaedo-mcp-2?style=directory" alt="Phaedo MCP on AllMCPs" /></a>