pi-mono/packages/coding-agent/docs/mcp.md

MCP Servers

Pi connects to Model Context Protocol servers over stdio or streamable HTTP and makes their tools available to the model.

Configure servers

Add servers to ~/.pi/agent/mcp.json, or to .pi/mcp.json in a project. The format matches other MCP clients, so existing mcpServers entries can be copied over:

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "."]
    },
    "docs": {
      "url": "https://example.com/mcp",
      "headers": { "Authorization": "Bearer ${DOCS_TOKEN}" },
      "exposure": "direct"
    }
  }
}

• stdio servers take command, args, env, and cwd. Relative cwd resolves against the session directory.
• HTTP servers take url, headers, and oauth (see Sign in with OAuth). The legacy SSE transport is not supported.
• env and headers values can reference environment variables (${NAME}) or commands (!command), like provider API keys.
• timeout sets the per-request timeout in seconds (default 60). Progress notifications from the server reset it.
• enabled: false keeps an entry without connecting to it.

Project entries replace global entries with the same name. A project mcp.json is only read after the project is trusted, because stdio servers run commands.

Pi connects when a session starts. The first prompt waits until startup connections finish. A server that drops its connection is reconnected on the next call. Run /mcp to see server status, tool counts, and errors.

Sign in with OAuth

Remote servers that use OAuth, such as Sentry, need no credentials in mcp.json:

{
  "mcpServers": {
    "sentry": { "url": "https://mcp.sentry.dev/mcp" }
  }
}

When such a server rejects the connection, /mcp shows it as needing sign-in. Run /mcp login sentry to open the authorization page in your browser. After you approve access, the browser redirects to a temporary server on 127.0.0.1 and pi connects. If the browser runs on another machine, for example over SSH, paste the URL it was redirected to into the prompt instead.

Pi registers itself with the authorization server (dynamic client registration), stores tokens in ~/.pi/agent/mcp-auth.json, and refreshes expired access tokens automatically. /mcp logout sentry deletes the stored credentials.

OAuth applies to HTTP servers without an Authorization header. For authorization servers that do not support dynamic client registration, configure a pre-registered client:

{
  "mcpServers": {
    "example": {
      "url": "https://mcp.example.com/mcp",
      "oauth": { "clientId": "my-client", "clientSecret": "${EXAMPLE_SECRET}", "callbackPort": 8765 }
    }
  }
}

callbackPort fixes the redirect URI to http://127.0.0.1:<port>/oauth/callback, which must match the redirect URI registered for the client. clientSecret is optional and can reference environment variables or commands.

Exposure

Each server's tools are registered as mcp__<server>__<tool>. The exposure setting controls how the model reaches them:

• codemode (default): the tools are callable from codemode scripts but are not declared to the model. Large MCP tool lists stay out of the model's tool declarations, and scripts can call several MCP tools, in parallel if needed, while returning only the part of the result the model needs. Pi activates the codemode tool when such a server connects.
• direct: the tools are declared to the model like built-in tools, and are also callable from codemode.

MCP tools that declare an outputSchema return their structuredContent to codemode scripts. Other tools return their text output. Images are passed through as image content.

Every MCP call goes through pi's tool pipeline, so tool_call and tool_result extension handlers, including permission gates, apply to MCP tools. Calls made from codemode scripts carry the codemode call's id as parentToolCallId.