M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
P

Pi MCP Adapter

Community
Gateway / proxy
Low-context MCP access for Pi.

This gateway aggregates or proxies other MCP servers; it only becomes useful once you connect real servers behind it.

How to install ↓ Compare GitHub source repository ↗
Category
Dev Tools #108 of 438
Stars
★ 1.6k Very popular
Transport
stdio (local process) · Streamable HTTP · SSE
Runtime
Node.js
Credentials
Optional API key
License
MIT
Last commit
Tools
1
61FMRS · C

This project is a Pi-focused MCP adapter extension rather than a standalone domain-specific MCP server. Its main value is reducing context usage through one proxy tool, lazy startup, and metadata caching; actual capabilities, permissions, and risks depend on the MCP servers configured by the user.

Strongest · Documentation 16/20 Weakest · Reliability 10/20

Reliability
10/20
Security and permissions
12/20
Maintenance
10/20
Documentation
16/20
Setup experience
13/20
Why each score
Reliability 10/20
The README describes lazy startup, metadata caching, timeouts, reconnection, output guarding, and OAuth flows, making the happy path plausible. However, the server manifest is unavailable, and the supplied material contains no source code, CI, or committed tests verifying MCP initialization, tool-list handshakes, argument behavior, or failure handling. Static-review uncertainty requires a deduction and prevents a score above 12.
Security and permissions 12/20
The documentation discloses bearer/OAuth credentials, environment interpolation, remote authorization codes, and external HTTP/stdio server boundaries; it warns that OAuth URLs and codes are sensitive, uses 0600 for spilled output, requires consent for URL UIs, and supports tool exclusion and output limits. These are positive controls. However, configuration permits arbitrary commands, working directories, environment variables, remote endpoints, and MCP tool side effects, with no source-level evidence of sandboxing, isolation, auditing, or comprehensive confirmation for dangerous operations. Points are deducted for those gaps.
Maintenance 10/20
The repository is stated to be unarchived and MIT-licensed, providing basic continuity and redistribution clarity. However, the prompt provides only stars and open-issue counts; it lacks evidence of releases, commit activity, dependency updates, a security-response channel, maintainer governance, or CI. Popularity is not scored, so this remains moderate.
Documentation 16/20
The README substantially covers installation, configuration precedence, stdio/HTTP transport, OAuth, lifecycle modes, direct tools, UI behavior, output limits, commands, examples, and limitations. Its breadth and operational detail support a high score. It is still unverified README evidence, with no source-backed compatibility or test evidence and limited demonstrated troubleshooting or security-audit detail, so full marks are not justified.
Setup experience 13/20
The project offers a one-command npm installation, a standard configuration example, shared config paths, first-run onboarding, host-config imports, an interactive panel, and a documented remote OAuth flow. Setup for the intended Pi workflow is therefore fairly clear. It still depends on Pi, Node/npm, external MCP servers, and local configuration state, while platform compatibility and successful connections lack source, CI, or test evidence, so points are deducted.

Static review · not runListed 2026-07-29

Read the FMRS scoring method →

Fit and risk

What it can accessReads local filesRuns commands or codeUses the networkControls a browser

Best for

  • Pi coding-agent users who want lower MCP context overhead
  • Developers who need access to multiple MCP ecosystem services
  • Users who want lazy connections, metadata caching, or optional direct tool registration

Not for

  • Users who do not use Pi
  • Workflows requiring server-process sharing across Pi sessions
  • MCP sampling workflows requiring context inclusion, tools, stop sequences, audio, or image content

Required permissions

  • Read and write Pi MCP configuration, tool metadata caches, and OAuth credential directories
  • Start configured local MCP processes and access their working directories
  • Access configured HTTP MCP endpoints, headers, environment variables, and OAuth credentials
  • Depending on the configured MCP servers, access files, browsers, databases, APIs, or other external resources

Risks and side effects

  • Configured MCP servers may receive the file, network, database, or API access required by their configuration and use
  • OAuth authorization URLs, codes, and tokens are sensitive credentials
  • Oversized text results may be written to the system temporary directory and are not cleaned up automatically
  • Review imported host configurations and their permission scope before relying on them

Setup

Before you start

Runtime：Node.js

Other optional settings (4)
MCP_OAUTH_DIR optional Legacy plaintext tokens. import directory only; persistent credentials live in the OS credential store.
MCP_OUTPUT_GUARD optional Set to 0 to disable the oversized MCP output guard.
MCP_UI_VIEWER optional Controls MCP UI rendering: browser, glimpse, or none.
PI_CODING_AGENT_DIR optional Overrides the Pi agent dir (default ~/.pi), affecting mcp. and cache paths.

Run pi install npm:pi-mcp-adapter, then restart Pi. Put project configuration in .mcp.json or shared user configuration in ~/.config/mcp/mcp.json. You can also run pi-mcp-adapter init to scan host-specific configurations.

MCP config · JSON 
{"mcpServers":{"chrome-devtools":{"command":"npx","args":["-y","chrome-devtools-mcp@latest"]}}}

Works in clients that read an "mcpServers" key. For clients such as VS Code that use a different key, the configurator below converts it.

.vscode/mcp.json
{
  "servers": {
    "chrome-devtools": {
      "command": "npx",
      "args": [
        "-y",
        "chrome-devtools-mcp@latest"
      ]
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal
claude mcp add chrome-devtools -- npx -y chrome-devtools-mcp@latest

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

After installing with `pi install npm:pi-mcp-adapter` and restarting Pi, open the /mcp panel to confirm the adapter loaded; calling mcp({ search: "screenshot" }) should return tools like chrome_devtools_take_screenshot, proving the connection works.

Troubleshooting

  1. Restart Pi after installation
  2. Check the precedence of .mcp.json, ~/.config/mcp/mcp.json, the Pi global override, and .pi/mcp.json
  3. Run /mcp to inspect server status, tools, and configuration; use /mcp reconnect <server> when needed
  4. Run /mcp setup or pi-mcp-adapter init when standard configuration files are absent
  5. For remote OAuth, use auth-start to obtain the URL and auth-complete with the full redirect URL or code
  6. After first enabling directTools, verify the metadata cache; use /mcp reconnect <server> if necessary

Things to try

Once connected, you can ask your AI assistant things like:

  • Use mcp to search for and call chrome_devtools_take_screenshot on the current page
  • Run mcp({}) to see which MCP servers are connected
  • Search with mcp({ search: "screenshot" }) to find screenshot-related tools
  • Start OAuth with mcp({ action: "auth-start", server: "linear-server" })

Tools 1

mcp writes
Searches, lists, describes, connects to, and calls tools from configured MCP servers; it also exposes server instructions, UI messages, and OAuth actions.

Use cases

Using database, browser, and API MCP services from Pi on demand
Discovering MCP tools through search and description
Promoting a selected set of tools with directTools
Completing OAuth flows in remote or headless environments

Supported clients

Pi

Listed from the project's documentation, not tested by this site.

Overview

Pi MCP Adapter is a Pi coding-agent extension that exposes configured MCP services through one proxy tool for on-demand discovery and invocation. It starts servers lazily by default, caches tool metadata, and supports stdio, Streamable HTTP, and SSE fallback to reduce context-window usage.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 63.3k · Tools 2 Compare with this →
Compare with other MCP servers

Source revision cc69d9ad0c03 Data synced 2026-10-19 Read the FMRS scoring method