Pi MCP Adapter — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow Pi and MCP client compatibility as adapter behavior changes

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Pi users connecting many MCP servers with lazy startup, discovery and approval controls.

What we know

A Pi adapter that proxies MCP servers through a single tool with on-demand discovery, lazy startup, OAuth and optional direct tools.

Maintenance / activity evidence

Observed Oct 5, 2026 (UTC)fix: require the Pi peers the adapter imports at runtime ( 806)

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Activity source · commits ↗Activity source · releases ↗

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Proxy access to connected MCP servers with optional destructive-tool approval. Writes: Install/configure servers; Invoke downstream write tools.
OAuth and server-specific credentials
Sensitive access: OAuth tokens, Downstream MCP data

Gateway risk is inherited from configured servers, although the adapter provides trust and approval controls.

Security source · repository notice ↗

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

1,578 repository stars · 1.5M package downloads / 30 days

Stars observed Oct 6, 2026. Downloads observed Oct 6, 2026.

All limitations / Review context

Which MCP transport and context-management features remain supported?

The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.

Gateway risk is inherited from configured servers, although the adapter provides trust and approval controls.
Proxy access to connected MCP servers with optional destructive-tool approval.
OAuth and server-specific credentials
Connected-server data passes through the adapter; tokens use OS keychain by default.
Reviewed write actions: Install/configure servers; Invoke downstream write tools
Sensitive access: OAuth tokens, Downstream MCP data
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.
No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
The fetched official SECURITY.md path returned HTTP 404; it was not treated as positive evidence.
Proxy calls can obscure individual underlying tool names to some permission extensions.
Each session may run separate server processes unless multiplexed.

Original activity observations

2026-10-05T07:24:45Z: fix: require the Pi peers the adapter imports at runtime ( 806)

Technical identity

github.com/nicobailon/pi-mcp-adapter

Exact implementation source: https://github.com/nicobailon/pi-mcp-adapter ↗
Reviewed resource type: Gateway
Repository identity: nicobailon/pi-mcp-adapter
Package identity: npm:pi-mcp-adapter

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 6, 2026

GitHub repository ↗
nicobailon/pi-mcp-adapter
Recorded repository material and project history.
Package registry ↗
pi-mcp-adapter
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.

Setup · Watchlist

Gateway setup

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
**Pi agent adapter**, not an upstream MCP server: install `pi install npm:pi-mcp-adapter`, use `/mcp-adapter setup` to import/select actual MCP servers. Adapter may replace Pi built-in MCP support.
pi extension install · Publisher instructions
pi install npm:pi-mcp-adapter
Configure / authenticate
Publisher instructions
Pi MCP Adapter extends Pi MCP tooling; host Pi is required. Sign-in tokens may live in OS keychain; import from other hosts is a separate explicit operation.
Check connection
Suggested check
Use publisher `pi-mcp-adapter doctor` and `/mcp-adapter setup`; verify a configured upstream server tool independently.
Remove / uninstall / revoke
MCP100 setup guide
Pi extension removal: verify actual installed Pi extension manager syntax using `pi --help` before executing; re-enable Pi built-in MCP in settings if this adapter had replaced it.
Distinguish client registration removal from software uninstall, persistent data deletion and provider OAuth/API-key revocation.
pi remove pi-mcp-adapter

Official Documentation & Sources

What it does

A Pi adapter that proxies MCP servers through a single tool with on-demand discovery, lazy startup, OAuth and optional direct tools.

Capability: Developer Tools
Resource type: Gateway
Industry: Software & Technology
Best fit: Pi users connecting many MCP servers with lazy startup, discovery and approval controls.

Representative uses

Install and use MCP servers from Pi
Import Cursor, Claude, Codex and VS Code configs
Search tools on demand
Authenticate OAuth servers and approve destructive tools

Limitations

Proxy calls can obscure individual underlying tool names to some permission extensions.
Each session may run separate server processes unless multiplexed.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: OAuth and server-specific credentials
Permissions: Proxy access to connected MCP servers with optional destructive-tool approval.
Data handling: Connected-server data passes through the adapter; tokens use OS keychain by default.
Cost: free
Risk and cautions: Gateway risk is inherited from configured servers, although the adapter provides trust and approval controls.

Access scope and cautions

Write actions: Install/configure servers Invoke downstream write tools
Sensitive access: OAuth tokens Downstream MCP data
Risk level: moderate

FAQ

Based on reviewed evidence as of 2026-10-06. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Install and use MCP servers from Pi; Import Cursor, Claude, Codex and VS Code configs; Search tools on demand; Authenticate OAuth servers and approve destructive tools.

What setup and authentication are documented?

Recorded installation/entrypoint step: pi install npm:pi-mcp-adapter. Recorded transport: stdio, streamable_http, sse, other. Recorded environment-variable notes: PI_CODING_AGENT_DIR. No configuration values are supplied here. Prerequisites: Pi. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Built-in OAuth; tokens stored in OS keychain by default.

Can it modify data or perform write operations?

Documented write actions include: Install/configure servers; Invoke downstream write tools. Recorded permission boundary: Proxy access to connected MCP servers with optional destructive-tool approval.

What data-handling boundary should I consider?

Connected-server data passes through the adapter; tokens use OS keychain by default. Recorded sensitive-access context: OAuth tokens; Downstream MCP data.

What limitations and risks should I check before use?

Gateway risk is inherited from configured servers, although the adapter provides trust and approval controls. Proxy calls can obscure individual underlying tool names to some permission extensions. Each session may run separate server processes unless multiplexed. A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.

Is this an official MCP?

Nico Bailon is listed as Community implementation in MCP100’s current evidence.