About mcpserverlist-mcp
mcpserverlist-mcp is a stdio MCP server for MCP Server List, aimed at authors preparing servers for directory submission. It proxies the hosted service’s tools and supports reconnecting after a dropped connection.
Key features
- 01Readiness checks for directory submission
- 02Discovery tools usable without an API key
- 03Account and submission tools with an API key
- 04Retries once after reconnecting
Use cases
- 01Check whether an MCP server is ready for listing
- 02Submit or manage server listings through the hosted service
MCP support
It connects to the hosted MCP endpoint and forwards tools/list and tools/call unchanged. Resources and prompts are forwarded when advertised by the remote server.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://mcpserverlist.io/mcpclaude mcp add --transport http sudomichael-mcpserverlist https://mcpserverlist.io/mcp{"mcpServers":{"sudomichael-mcpserverlist":{"type":"http","url":"https://mcpserverlist.io/mcp"}}}Open in Cursor{"servers":{"sudomichael-mcpserverlist":{"type":"http","url":"https://mcpserverlist.io/mcp"}}}Open in VS Code{"mcpServers":{"sudomichael-mcpserverlist":{"type":"http","url":"https://mcpserverlist.io/mcp"}}}{"mcpServers":{"sudomichael-mcpserverlist":{"serverUrl":"https://mcpserverlist.io/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEmcpserverlist-mcp
Stdio MCP server for MCP Server List. It connects to the hosted service at https://mcpserverlist.io/mcp and passes tools through unchanged, so any stdio-only client or directory can use it.
What MCP Server List does
It helps MCP server authors get their server listed in MCP directories. It checks whether your server is ready to submit, and offers a $99 managed submission service that handles the submissions for you.
Install
Run with npx -y mcpserverlist-mcp (Node 20 or newer).
Claude Desktop (claude_desktop_config.json), Cursor (~/.cursor/mcp.json):
{
"mcpServers": {
"mcpserverlist": {
"command": "npx",
"args": ["-y", "mcpserverlist-mcp"]
}
}
}
Claude Code:
claude mcp add mcpserverlist -- npx -y mcpserverlist-mcp
To use an API key, add "env": { "MCP_SERVER_LIST_API_KEY": "..." } to the config above, or pass -e MCP_SERVER_LIST_API_KEY=... to claude mcp add.
Direct remote (no install)
Clients that support Streamable HTTP can connect straight to the hosted server:
claude mcp add --transport http mcpserverlist https://mcpserverlist.io/mcp
Or in a JSON config, { "mcpServers": { "mcpserverlist": { "url": "https://mcpserverlist.io/mcp" } } }.
Environment variables
| Variable | Required | Description |
|---|---|---|
MCP_SERVER_LIST_API_KEY | No | Sent as Authorization: Bearer <key>. Only sent when set. |
MCP_SERVER_LIST_URL | No | Remote endpoint. Default https://mcpserverlist.io/mcp. |
Anonymous vs. API key
Discovery and check tools work without a key. Tools that act on your account (your servers, submissions) need an API key, which you get by calling the create_account tool. Use tools/list for the current set.
Behavior
- Connects to the remote at startup. If that fails, it prints an error to stderr and exits non-zero. Stdout carries only MCP protocol traffic.
- Forwards
tools/listandtools/callunchanged. Resources and prompts are forwarded only if the remote advertises them. The remote's server instructions are mirrored. - If the connection to the remote drops, a request reconnects and retries once.
Development
npm install
npm test # builds, then runs tests against an in-process fake remote
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.