mcp -registry

This MCP server exposes tools to interact with the MCP Registry. It lets you discover and search for available MCP servers registered in the registry, with support for cursor-based pagination to handle large result sets. You can optionally configure a custom registry URL to query a different MCP registry endpoint. The primary tool exposed is list_mcp_servers, which returns a list of MCP servers along with metadata suitable for semantic analysis, and supports optional parameters for limiting results, providing a pagination cursor, and overriding the registry base URL.

Prerequisites:

• Node.js 20+ (and npm)

Install using npm/npx (recommended):

1. Quick start with npx (no local install required):

npx -y mcp-server-mcp-registry@latest

2. If you prefer to wire it in a project using mcp.json (VS Code quick setup):

{
  "servers": {
    "mcp-registry": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-mcp-registry@latest"
      ]
    }
  }
}

3. Optional: run as a one-off in a shell session (for local exploration):

npx -y mcp-server-mcp-registry@latest help

Prerequisites recap: ensure Node.js 20+ is installed and available in your PATH. You can verify by running node -v and npm -v.

Notes:

• The registry URL can be overridden by configuration or environment to point at a custom MCP Registry endpoint.
• The list_mcp_servers tool supports limit (default 50, range 1-100) and cursor for pagination; use them to browse large registries.
• The MCP data returned is structured for semantic analysis and can be consumed by tooling that performs discovery, motivation extraction, or lifecycle tracking of MCP servers.
• If you encounter network or registry access issues, check your network proxy settings and ensure the registry URL is reachable from your environment.