内容摘录
<div align="center">
<img src="assets/logo.png" width="120" alt="ToolSDK MCP Registry" />
ToolSDK MCP Registry
**The Enterprise MCP Registry & Gateway.** A unified infrastructure to discover, secure, and execute Model Context Protocol (MCP) tools. Exposes local processes (STDIO) and remote servers (StreamableHTTP) via a unified HTTP API with built-in Sandbox and OAuth 2.1 support.
<a href="https://www.npmjs.com/package/@toolsdk.ai/registry">
<img src="https://img.shields.io/npm/v/@toolsdk.ai/registry.svg?style=flat-square" alt="npm version" />
</a>
<a href="https://github.com/toolsdk-ai/toolsdk-mcp-registry/actions/workflows/test.yaml">
<img src="https://github.com/toolsdk-ai/toolsdk-mcp-registry/actions/workflows/test.yaml/badge.svg" alt="Build Status" />
</a>
<img src="https://img.shields.io/badge/MCP_Servers-4541-blue?style=flat-square" alt="MCP Servers Count" />
<img src="https://img.shields.io/badge/LICENSE-MIT-ff69b4?style=flat-square" alt="License" />
<br />
<a href="https://www.producthunt.com/products/toolsdk-ai">
<img src="https://api.producthunt.com/widgets/embed-image/v1/top-post-badge.svg?post_id=997428&theme=light&period=daily" alt="Product Hunt" height="40" />
</a>
<a href="#mcp-servers">🔍 <b>Browse 4541+ Tools</b></a>
•
<a href="#quick-start">🐳 <b>Self-hosted</b></a>
•
<a href="#install-via-package-manager">📦 <b>Use as SDK</b></a>
•
<a href="#submit-new-mcp-servers">➕ <b>Add Server</b></a>
•
<a href="https://www.youtube.com/watch?v=J_oaDtCoVVo" target="_blank">🎥 <b>Video Tutorial</b></a>
<a href="https://toolsdk.ai" target="_blank">
<img src="assets/hero.png" alt="ToolSDK.ai - MCP Servers Hosting" />
</a>
---
</div>
Start Here
🔍 I want to **find an MCP Server** → Browse Directory
🔌 I want to **integrate MCP tools** into my AI app → Integration Guide
🚀 I want to **deploy an MCP Gateway** → Deployment Guide
➕ I want to **submit my MCP Server** → Contribution Guide
[!IMPORTANT]
**Pro Tip**: If a server is marked as validated: true, you can use it instantly with **Vercel AI SDK**:
**Want validation?** Ask AI: *"Analyze the make build target in the Makefile and the scripts it invokes, and determine how an MCP server gets marked as validated: true."*
Getting Started
<a id="docker-self-hosting"></a>
Deploy Enterprise Gateway (Recommended)
Deploy your own **private MCP Gateway & Registry** in minutes. This provides the full feature set: Federated Search, Remote Execution, Sandbox, and OAuth.
⚡ Quick Deploy (One-Liner)
Start the registry immediately with default settings:
*Did this save you time? Give us a **Star on GitHub** — it helps others discover this registry!*
**Configuration:**
Set MCP_SANDBOX_PROVIDER=LOCAL in .env file if you want to disable the sandbox (not recommended for production).
*See Configuration Guide for full details.*
[!TIP]
**Tip for Private Deployment**: This registry contains 4541+ public MCP servers. If you only need a specific subset for your private environment, you can prune the packages/ directory.
📖 See Package Management Guide for details.
That's it! Your self-hosted MCP registry is now running with:
🌐 **HTTP API** with OpenAPI documentation
🛡️ **Secure Sandbox execution** for AI agent tools
🔍 **Full-text search** (Meilisearch)
🎉 Access Your Private MCP Registry
🌐 **Local Web Interface**: http://localhost:3003
📚 **Swagger API Docs**: http://localhost:3003/swagger
🔍 **Search & Execute** 4541+ MCP Servers remotely
🤖 **Integrate** with your AI agents, chatbots, and LLM applications
🌐 Remote Tool Execution Example
Execute any MCP tool via HTTP API - perfect for AI automation, chatbot integrations, and serverless deployments:
<details>
<summary><strong>Alternative: Use as Registry SDK (Data Only)</strong></summary>
<a id="use-as-sdk"></a>
Alternative: Use as Registry SDK (Data Only)
If you only need to access the **list of MCP servers** programmatically (without execution or gateway features), you can use the NPM package.
Usage
Perfect for building your own directory or analysis tools:
Access via Public API (No Installation Required)
Fetch the complete MCP server registry programmatically:
</details>
Why ToolSDK MCP Registry?
**ToolSDK MCP Registry** is an enterprise-grade gateway for Model Context Protocol (MCP) servers. It solves the challenge of securely discovering and executing AI tools in production environments.
Key Features
**Federated Registry** - Unified search across local private servers and the official @modelcontextprotocol/registry.
**Unified Interface** - Access local STDIO tools and remote StreamableHTTP servers via a single, standardized HTTP API.
**Secure Sandbox** - Execute untrusted tools in isolated environments (supports E2B, Daytona, Sandock).
**OAuth 2.1 Proxy** - Built-in OAuth 2.1 implementation to handle complex authentication flows for your agents. Integration Guide
**Private & Self-Hosted** - Full control over your data and infrastructure with Docker deployment.
**Developer-Friendly** - OpenAPI/Swagger documentation and structured JSON configs.
Use Cases
**Enterprise AI Gateway** - Centralize tool access for all your internal LLM applications.
**Secure Tool Execution** - Run community MCP servers without risking your local environment.
**Protocol Adaptation** - Connect remote agents (via HTTP API) to local CLI tools (via STDIO).
**Unified Discovery** - One API to search and manage thousands of tools.
Architecture
---
What You Get
This open-source project provides:
**Structured Registry** - 4541+ MCP servers with metadata
**Unified Gateway** - HTTP API to query and execute tools remotely
**Auto-Generated Docs** - Always up-to-date README and API documentation
✅ Validated Packages = One-Line Integration (ToolSDK)
Some packages in this registry are marked as validated: true.
[!NOTE]
**What does validated: true mean for you?**
You can load the MCP package directly via our ToolSDK NPM client and get ready…