Development MCP
A coding agent needs conversation records to investigate a run. The development MCP provides read-only access under your persona, authorized with a passkey and revocable from the connections page.
The web app hosts the development MCP server. Connect an MCP client to authorize access in your browser.
Your coding agent can then read your persona's conversations, traces, and replay plans, or query your data with SQL.
claude mcp add --transport http polychrome https://polychrome.sh/mcpRun /mcp inside the session and approve access in the browser tab. For other MCP clients, use https://polychrome.sh/mcp as the server URL.
Connect an agent
The client registers and redirects you to polychrome.sh/authorize. Name the connection and approve it with your sign-in passkey. Approval creates a separate session for the client. Revoking that session leaves your browser session active, and vice versa.
Sign in before approving the connection, then use the same wallet to approve it. The consent screen rejects a different wallet to preserve the selected persona. It labels the client's name and redirect addresses as unverified because clients supply these values during registration.
What it can read
The server exposes seven read-only tools. Start with whoami to check the persona and administrator status that determine each tool's access.
| Tool | Answers |
|---|---|
whoami | Which persona this session reads as, and whether it is an administrator. |
list_conversations | The conversations this persona took part in, with recent activity, turn count, and a first-message preview. |
describe_schema | The tables this session can query, or the columns of one table. |
query | Read-only SQL over those tables. Same engine, scope rules, and cost ceilings as the query surface. |
get_trace | A conversation's turn graph: ranked failure signals, integrity status, and per-turn steps. Pass a turn id to select one turn. |
get_replay_plan | The exact request that produced a turn, alongside the output it produced. Override the model or decode parameters to plan a replay with different settings. |
get_wallet | The live wallet: state, balance, spend policy, deposit address, and deployment ceilings. |
get_trace and get_replay_plan provide results unavailable through SQL queries. A trace ranks failure signals and verifies signed integrity roots. A replay plan reconstructs the request from recorded events.
What it cannot do
The tools cannot send turns, transfer money, or change settings. A standard persona can read only its authorized conversations; administrators have broader access as described below. The client receives an opaque token while the underlying session remains on the server.
Administrators can read across the deployment. If your persona has the administrator attribute, these tools can read other personas' conversations. Check whoami before relying on the scope of a query.
These read-only tools do not require the approvals used for gated actions during a turn.
Disconnect a client
polychrome.sh/connections lists each approved connection, its label, creation time, and last use. Disconnecting revokes the control-plane session before removing its entry. The client's existing token no longer grants access.
A connection expires after 30 days without use or 90 days in total. Signing out revokes only the browser session, so the client can continue while you are signed out. Revoking the authorizing wallet also ends the connection's access once its current token expires.
Repository MCP server
The development MCP server reads persona data for your coding agent. A separate server at mcp.polychrome.sh/mcp provides read-only access to the Polychrome repository. Its tools read files, search code, list directories, and retrieve docs. See Endpoints for the available hosts.