toolsdk-mcp-registry: Discover and Run MCP Servers

Overview

ToolSDK MCP Registry combines a structured directory of MCP server packages with a gateway that can expose local STDIO servers and remote Streamable HTTP servers through HTTP APIs. It addresses the gap between finding tools and making them available to AI applications through a common interface.

The project is suited to developers and teams that want to browse registry data, run a private registry, or centralize MCP tool access. It is available as a Docker deployment, an npm package for registry data, and public JSON indexes. See the repository README for setup and API details.

Key Features

• Registry data for thousands of MCP server packages, organized with metadata and categories.
• Federated search across local private servers and the official MCP registry.
• HTTP API for searching and executing registered tools.
• Gateway that exposes STDIO-based packages through Streamable HTTP endpoints.
• Optional sandbox execution, with providers including E2B, Daytona, and Sandock.
• OAuth 2.1 proxy support for authentication flows.
• Registry data access through an npm package and public JSON indexes.
• OpenAPI and Swagger documentation for the API.

Use Cases

• AI application developers can discover MCP packages and integrate their tools without maintaining a separate directory.
• Platform teams can self-host a gateway to centralize access to internal and community MCP servers.
• Teams with STDIO-only tools can make them accessible to clients using Streamable HTTP.
• Developers evaluating MCP tools can retrieve the registry JSON for building directories or analysis utilities.

Getting Started

For the self-hosted gateway, run:

docker compose up -d

For registry data only, install the npm package with npm install @toolsdk.ai/registry. Refer to the README for configuration, API examples, and integration guidance.

Alternatives

• mcphub: MCPHub focuses on routing and managing existing MCP servers, while ToolSDK MCP Registry catalogs servers and provides search and execution.
• anythingmcp: AnythingMCP generates MCP tools from business-system APIs, while ToolSDK MCP Registry focuses on discovering and executing MCP servers.

Considerations

• The gateway runs MCP packages, so teams should review package trust and configure sandboxing and authentication for their deployment. The README says disabling the sandbox is not recommended for production.
• Self-hosting uses Docker Compose and may require configuration for sandbox providers, OAuth, and package environments.
• The repository reports 156 open issues, so users should check the issue tracker for known problems relevant to their setup.
• Registry data can be used independently, but execution and gateway features require running the service.