- Home
- MCP servers
- MCP Registry
MCP Registry
- javascript
2
GitHub Stars
javascript
Language
6 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"wei-mcp-registry-mcp-server": {
"command": "npx",
"args": [
"-y",
"mcp-registry-mcp-server"
]
}
}
}You can run an MCP Registry server locally to query and explore published MCP servers. This server enables AI assistants and applications to discover, search, and retrieve MCP server information programmatically, helping you build richer, data-driven integrations.
How to use
You will interact with the MCP Registry through your MCP client or toolchain. Use a client that supports MCP to list registered servers, search by name or tag, view versions for a specific server, and fetch detailed information about a chosen server. You can also perform health checks to ensure the registry is responsive. Focus your prompts on concrete actions like listing servers, filtering by keywords, checking version histories, and retrieving server details.
How to install
Prerequisites you need before running the server:
• Node.js 18.0.0 or higher is required.
Install and run the MCP Registry MCP server using the standard input/output (stdio) configuration. This approach starts a local process that communicates with your MCP client over stdio.
Example configuration
{
"mcp-registry-mcp-server": {
"type": "stdio",
"command": "npx",
"args": ["-y", "mcp-registry-mcp-server"]
}
}
Start locally with stdio config
Use the following command to start the MCP Registry MCP server in an environment that supports npx. This will launch the server as a local process and expose its MCP endpoints through stdio for your client to use.
npx -y mcp-registry-mcp-server
Configuration notes
The stdio configuration shown above uses npx to run the mcp-registry-mcp-server package. You can adapt this to your tooling by placing the provided JSON configuration into your MCP client setup and ensuring your client connects via stdio to the spawned process.
Troubleshooting
If you encounter issues starting the server, verify your Node.js version, ensure you have network access for npm to fetch packages, and confirm that the command and arguments in your stdio configuration are exactly as shown. Check for common problems like missing dependencies or permissions errors and consult your client’s MCP integration logs for details.
Available tools
list_servers
Browse all registered MCP servers with optional search and pagination.
list_server_versions
View all available versions for a specific MCP server.
get_server
Get detailed information about a specific MCP server version.
health_check
Check if the MCP registry is operational.