MCP (Model Context Protocol) adapter extension for Pi coding agent
Pi MCP server exists for a simple reason — assistants are far more useful when they can act on Pi directly instead of describing what you should do. MCP (Model Context Protocol) adapter extension for Pi coding agent.
Use MCP servers with Pi without burning your context window.
Once Pi is connected, these are the calls the assistant has available:
File — PurposeField — Descriptionargs — Command argumentssocket — Explicit rmcp-mux Unix-domain socket path; supports ${VAR}, $env:VAR, and ~ expansion and is mutually exclusive with command and urlenv — Environment variables; supports ${VAR} and $env:VAR interpolation. A value beginning with ! runs a command when the stdio server connects; use !! forcwd — Working directory; supports ${VAR}, $env:VAR, and ~ expansionurl — HTTP endpoint (StreamableHTTP with SSE fallback); supports raw ${VAR} and $env:VAR interpolation, and missing URL variables fail before any requestheaders — HTTP headers; supports ${VAR} and $env:VAR interpolation. A value beginning with ! runs a command when the HTTP server connects or OAuthauth — "bearer" or "oauth"oauth.grantType — "authorization_code" (default) or "client_credentials" for non-interactive machine authoauth.clientId — Pre-registered OAuth client ID; dynamic registration is used when omittedoauth.clientSecret — OAuth client secret for confidential clients; a value beginning with ! runs a command when OAuth authenticates, while !! escapes a literal leading !Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Pi's toolset — File, Field, args and 11 more — is a fair guide to whether it matches your workflow. It is maintained by nicopreme; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| File | Purpose |
| Field | Description |
| args | Command arguments |
| socket | Explicit rmcp-mux Unix-domain socket path; supports ${VAR}, $env:VAR, and ~ expansion and is mutually exclusive with command and url |
| env | Environment variables; supports ${VAR} and $env:VAR interpolation. A value beginning with ! runs a command when the stdio server connects; use !! for a literal leading !. |
| cwd | Working directory; supports ${VAR}, $env:VAR, and ~ expansion |
| url | HTTP endpoint (StreamableHTTP with SSE fallback); supports raw ${VAR} and $env:VAR interpolation, and missing URL variables fail before any request is sent |
| headers | HTTP headers; supports ${VAR} and $env:VAR interpolation. A value beginning with ! runs a command when the HTTP server connects or OAuth authenticates; use !! for a literal leading !. |
| auth | "bearer" or "oauth" |
| oauth.grantType | "authorization_code" (default) or "client_credentials" for non-interactive machine auth |
| oauth.clientId | Pre-registered OAuth client ID; dynamic registration is used when omitted |
| oauth.clientSecret | OAuth client secret for confidential clients; a value beginning with ! runs a command when OAuth authenticates, while !! escapes a literal leading ! |
| oauth.scope | Requested OAuth scopes |
| oauth.redirectUri | Exact localhost redirect URI for browser OAuth, including port and path, for providers that pre-register callbacks |
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": ["-y", "chrome-devtools-mcp@1.6.0"]
}
}
}Configuration as documented by the project. Restart the client after saving.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.