C
Consiliency/pmcp
Gateway that reveals MCP tools gradually, to save context
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
- Copy the command above
- Paste it as one entry under
mcpServersinclaude_desktop_config.json— local servers take command + args (example: clients) - Restart your client
Client config (built from the install command this repo gives)
{
"mcpServers": {
"consiliency-pmcp": {
"command": "uvx",
"args": ["pmcp"]
}
}
}Parsed from the README we fetched on 2026-11-04; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"consiliency-pmcp": {
"command": "uvx",
"args": ["pmcp"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio consiliency-pmcp -- uvx pmcp
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Source
- collected from the abordage/awesome-mcp list · type: MCP server
- Harvest history
- first seen 2026-11-05 · last seen 2026-11-14 · seen 10× · listed by 10 sources
- Score
- score 1,003 · 10 sources · mcp
- Install
uvx pmcp
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
uvx pmcp. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
first catalogued 2026-11-05；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.
# PMCP - Progressive MCP
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
A gateway that lets your AI coding assistant use dozens of external tools without loading them all up front.
PMCP sits between your assistant (Claude Code, Codex, and others) and the services it can plug into — GitHub, Jira, databases, 90+ more. Instead of loading every tool's full schema before you've asked a question, it offers a short menu first and fetches the detailed schema only when a tool is actually used.
## Why it exists
Assistants reach external services through MCP (Model Context Protocol) — a common interface for an AI to talk to other software. When an assistant connects to a dozen MCP servers directly, it loads all of their tool definitions into context at once.
Context is limited and metered: every tool definition costs tokens and crowds out room for the actual work. Loading 50+ tools you may never call is slow and expensive, and adding a new service usually means restarting the assistant. Anthropic has highlighted context bloat as a key challenge with MCP tooling.
PMCP is the single connection point that keeps this compact and on-demand.
## Who it's for
Developers and teams running AI coding assistants with many connected tools — especially anyone hitting "too many tools" or context-full limits.
## What you get
Lower token cost — the assistant sees a compact capability card, not 50+ full schemas, before doing real work.
Load tools only when needed — downstream servers stay dormant until first use ("lazy by default"), and eager-start only when listed in autoStart.
Add tools without restarting — provision a new server on demand from a manifest of 90+.
One stable connection — your assistant sees ~26 steady meta-tools instead of a shifting set of many.
Guardrails built in — output size caps and optional secret redaction.
Works out of the box — core capability matching needs no API key.
## Quick Start
### Installation
bash
# With uv (recommended)
uv pip install pmcp
# Or run directly without installing
uvx pmcp
# With pip
pip install pmcp
### Upgrading from 2.x
3.0.0 refuses several things 2.7.3 accepted. Most importantly, a repository's
.mcp.json, .pmcp/manifest.yaml and .mcp-gateway-policy.yaml are ignored
until you approve them with pmcp trust approve .
MIGRATING.md has an upgrade checklist, a section for each
breaking change (with a check, the fix and how to verify it), and how to roll
back. To stay on 2.x for now, pin pmcp Capability matching is built-in — no API key needed. gateway.requestcapability
> uses a pure-Python matcher that can return direct CLI guidance for installed
> native tools, MCP server candidates, or registry search guidance.
### Configure with pmcp setup
PMCP includes a wizard-style helper that can render ready-to-use MCP client config for Claude and OpenCode.
The generated config only connects your client to the PMCP gateway. Downstream MCP
servers stay lazy until first use unless you add them to autoStart in your
.mcp.json.
Use pmcp setup to print the generated config:
bash
pmcp setup --client claude --mode stdio # Claude local stdio
pmcp setup --client claude --mode http # Claude shared-service HTTP
pmcp setup --client opencode --mode stdio # OpenCode local stdio
pmcp setup --client opencode --mode http # OpenCode shared-service HTTP
PMCP sits between your assistant (Claude Code, Codex, and others) and the services it can plug into — GitHub, Jira, databases, 90+ more. Instead of loading every tool's full schema before you've asked a question, it offers a short menu first and fetches the detailed schema only when a tool is actually used.
## Why it exists
Assistants reach external services through MCP (Model Context Protocol) — a common interface for an AI to talk to other software. When an assistant connects to a dozen MCP servers directly, it loads all of their tool definitions into context at once.
Context is limited and metered: every tool definition costs tokens and crowds out room for the actual work. Loading 50+ tools you may never call is slow and expensive, and adding a new service usually means restarting the assistant. Anthropic has highlighted context bloat as a key challenge with MCP tooling.
PMCP is the single connection point that keeps this compact and on-demand.
## Who it's for
Developers and teams running AI coding assistants with many connected tools — especially anyone hitting "too many tools" or context-full limits.
## What you get
Lower token cost — the assistant sees a compact capability card, not 50+ full schemas, before doing real work.
Load tools only when needed — downstream servers stay dormant until first use ("lazy by default"), and eager-start only when listed in autoStart.
Add tools without restarting — provision a new server on demand from a manifest of 90+.
One stable connection — your assistant sees ~26 steady meta-tools instead of a shifting set of many.
Guardrails built in — output size caps and optional secret redaction.
Works out of the box — core capability matching needs no API key.
## Quick Start
### Installation
bash
# With uv (recommended)
uv pip install pmcp
# Or run directly without installing
uvx pmcp
# With pip
pip install pmcp
### Upgrading from 2.x
3.0.0 refuses several things 2.7.3 accepted. Most importantly, a repository's
.mcp.json, .pmcp/manifest.yaml and .mcp-gateway-policy.yaml are ignored
until you approve them with pmcp trust approve .
MIGRATING.md has an upgrade checklist, a section for each
breaking change (with a check, the fix and how to verify it), and how to roll
back. To stay on 2.x for now, pin pmcp Capability matching is built-in — no API key needed. gateway.requestcapability
> uses a pure-Python matcher that can return direct CLI guidance for installed
> native tools, MCP server candidates, or registry search guidance.
### Configure with pmcp setup
PMCP includes a wizard-style helper that can render ready-to-use MCP client config for Claude and OpenCode.
The generated config only connects your client to the PMCP gateway. Downstream MCP
servers stay lazy until first use unless you add them to autoStart in your
.mcp.json.
Use pmcp setup to print the generated config:
bash
pmcp setup --client claude --mode stdio # Claude local stdio
pmcp setup --client claude --mode http # Claude shared-service HTTP
pmcp setup --client opencode --mode stdio # OpenCode local stdio
pmcp setup --client opencode --mode http # OpenCode shared-service HTTP
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/consiliency-pmcp/)
- Source
- awesome · https://github.com/Consiliency/pmcp
- Browse by field
- MCP servers
- Listed by
- 10 independent sources
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.