Search every MCP server and agent skill in the PlugMCP directory from inside your agent: ranked results, trust signals and install configs for every client.
{ "mcpServers": { "plugmcp-directory": { "url": "https://plugmcp.ai/mcp-server", "headers": {} } }}Power your agent
The publisher's own URL. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
https://plugmcp.ai/mcp-serverThe Claude button above opens Claude with the name and URL filled in. You still confirm it there.
claude mcp add --transport http plugmcp-directory https://plugmcp.ai/mcp-serverRun in a terminal.
{ "mcpServers": { "plugmcp-directory": { "command": "npx", "args": [ "-y", "mcp-remote", "https://plugmcp.ai/mcp-server" ] } }}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchOverview
The PlugMCP directory as an MCP server. Ask your agent to find an MCP server or skill for a task and it gets ranked, deduplicated results with health, auth and official signals, plus a ready install config for Cursor, Claude Code, Claude Desktop, VS Code, Windsurf, Gemini CLI, Codex or raw JSON. Works without a key at 50 calls a day; a free PlugMCP key raises that to 500, a paid plan to 20,000.
9 tools
FAQ
No. Without a key the directory MCP answers 50 tool calls a day per address. A free PlugMCP key raises that to 500 a day, and a paid plan to 20,000.
As an Authorization: Bearer header. Create the key on the PlugMCP dashboard; it is shown once.
It returns the install config for your client. Your agent or you add it; the server itself runs at its publisher.
From the publisher
README is not crawled yet. No repository on file.