MCP adapter

Configured MCP clients can read bounded project context and tasks, then report results through Phewsh's existing record. Your project-owned .intent/ files remain the source of truth.

Optional, local-first, and removable. MCP connects tools; it does not make them identical or authorize execution.

Your machine, right now

Local bridge not connected
Connect only when you want this page to inspect the loopback worker on this machine.

Recent receipts

Redacted activity appears here when the local bridge is running. These bounded records point to what was observed; they are not transcripts or proof that every claimed result was independently verified.

Use the adapter in three steps

Install the CLI. curl -fsSL phewsh.com/install.sh | sh — no account needed.
Configure a supported client. phewsh mcp setup adds the bundled stdio server to a client you choose. The client receives bounded Project, Next, constraints, and task capabilities.
Keep authority explicit. MCP access does not claim work or grant remote execution by itself. For team coordination, open Ion; same-machine execution still requires a deliberately registered project and a human click or phewsh ion claim.

How the planes fit together

/cli — command
Author intent, sync it everywhere, run the bridges. The terminal surface.
/mcp — coordination
Optional stdio capabilities plus a redacted view of local bridge activity.
/api — inference
One OpenAI-compatible key for any model, bounded by your project's budget.

Everything on this page is local-first: the bridge binds to localhost only, and receipts are plain JSON files you can open yourself. Team coordination and explicit cloud state live in Ion; teammates cannot reach this machine's localhost. See /connect for the full integration picture.