PlugMCP directory

[PlugMCP]

plugmcp-mcp

One MCP server that finds the rest. Your agent searches 70,000+ MCP servers and agent skills, compares them, and gets the exact install config for your client.

[Add to Cursor] [Install in VS Code]

[npm] [MCP Registry] [MIT] [CI]

Ask your agent

Once it is connected, ask in plain words:

• "Find an MCP server that lets Cursor query my Postgres database, and install it."
• "Compare the GitHub and GitLab MCP servers."
• "What MCP servers came out this week?"
• "Give me the Claude Code command for the Linear MCP server."
• "Find an agent skill for editing PDFs and give me the message to install it in Grok Bot."

Install

The fastest path needs no install at all. The directory is a remote MCP server at:

https://plugmcp.ai/mcp-server

Use this package when your client only runs local (stdio) servers, or when you want the server in a lockfile.

Claude Code

claude mcp add --transport http plugmcp https://plugmcp.ai/mcp-server# or local:claude mcp add plugmcp -- npx -y plugmcp-mcp

Cursor, Windsurf, Claude Desktop, and any mcpServers JSON

{  "mcpServers": {    "plugmcp": {      "command": "npx",      "args": ["-y", "plugmcp-mcp"]    }  }}

VS Code (.vscode/mcp.json)

{  "servers": {    "plugmcp": { "type": "http", "url": "https://plugmcp.ai/mcp-server" }  }}

Codex CLI

codex mcp add plugmcp --url https://plugmcp.ai/mcp-server

Grok Bot

Grok Bot has no config file. Send this in a Grok Bot chat and confirm the card:

Add a custom MCP server called plugmcp at https://plugmcp.ai/mcp-server

Every Bot on your account gets it; attach it to a task with @. Then ask for any server or skill with grok-bot as the client, and the reply is the message that adds that one too.

Grok Build and grok.com

• Grok Build: grok mcp add --transport http plugmcp https://plugmcp.ai/mcp-server
• grok.com: open Connectors, choose New Connector, then Custom, and paste https://plugmcp.ai/mcp-server.

ChatGPT

Settings, then Connectors, then Add. Name plugmcp, URL https://plugmcp.ai/mcp-server.

API key (optional)

Every tier is paced, so one busy agent cannot use the whole day at once:

When a limit is hit, the tool result says which one and when it resets. Calls without a key may also wait while the directory is busy; key holders keep working. Create a pb_live_ key at plugmcp.ai/app and pass it as PLUGMCP_API_KEY:

{  "mcpServers": {    "plugmcp": {      "command": "npx",      "args": ["-y", "plugmcp-mcp"],      "env": { "PLUGMCP_API_KEY": "pb_live_..." }    }  }}

For the remote URL, send it as Authorization: Bearer pb_live_.... Details are in auth.md.

Tools

Every tool is read-only.

How it works

plugmcp-mcp is a small stdio server built on the official MCP TypeScript SDK. It forwards tools/list and tools/call to https://plugmcp.ai/mcp-server over Streamable HTTP. The upstream connection opens on the first call and reconnects after a network error. Nothing is stored locally.

Develop

npm cinpm test        # build, then unit tests against an in-memory upstreamnpm run smoke   # run the built server over stdio against plugmcp.ai

Release

Push a v* tag that matches package.json. The publish workflow runs the tests, publishes to npm (NPM_TOKEN secret), then publishes server.json to the MCP Registry as ai.plugmcp/directory, signed with the plugmcp.ai domain key (MCP_REGISTRY_PRIVATE_KEY secret).

Related

• awesome-mcp-servers: the curated shelves from the same directory.
• plugmcp.ai/mcp: browse the full directory.
• plugmcp.ai/directory-mcp: setup guide for every client.

License

MIT