Explainer
An MCP server is a program that exposes named tools an AI client can list and call. The client, such as Cursor or Claude, sends a request.
The server runs the tool and returns structured data. PlugMCP is a directory of those servers, plus an optional host when you want keys and logs.
Client
Cursor, Claude, VS Code
MCP
tools/list, tools/callServer
The publisher's process
Protocol
The client starts a session, asks for the tool list, picks one, and sends arguments. The server returns a result the client can show or chain into the next call.
{
"jsonrpc": "2.0",
"id": 1,
"method": "initialize",
"params": {
"protocolVersion": "2025-06-18",
"capabilities": {},
"clientInfo": { "name": "cursor" }
}
}
{
"jsonrpc": "2.0",
"id": 1,
"result": {
"protocolVersion": "2025-06-18",
"capabilities": { "tools": {} },
"serverInfo": { "name": "docs-server" }
}
}
Categories
Hosting
The publisher runs it. Credentials stay with that publisher, or in your client if they ask for a key. A listing on PlugMCP is a page about their server. It is not our gateway unless you create a hosted copy.
Hosting on PlugMCP is the wrong choice when you only want to install someone else's server. Use the listing. Host when you need our keys, call logs, and a URL you control.
To find a server, open the MCP server directory. Categories and best-of pages sit next to it.
| Question | Install the listing | Host on PlugMCPOptional |
|---|---|---|
| Who runs it | The publisher | PlugMCP gateway |
| Install | Publisher URL or command | A URL you control |
| Credentials | Publisher or your client | PlugMCP keys |
| Call logs | No | Yes |
| Account needed | No | Yes |
Questions
Short answers. The directory has the rest.