M
modelcontextprotocol/registry
Community registry of MCP servers
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · HTTP 200 · 打开的是厂商自己的官网
安装与配置
远端端点（Claude Desktop / Cursor / Windsurf 共用 mcpServers）
{
"mcpServers": {
"modelcontextprotocol-registry": {
"url": "https://business-contact-finder-mcp.ottobot2025.workers.dev/mcp"
}
}
}把这段粘进 Claude Desktop / Cursor 的 mcpServers 配置即可。端点来自公开证据，我们没有替你安装或托管它。 官方 Registry 记录：这个端点没有列出任何请求头。这不等于免密 —— 以项目文档为准。
VS Code（.vscode/mcp.json —— 键名是 servers，远程要 type: http）
{
"servers": {
"modelcontextprotocol-registry": {
"type": "http",
"url": "https://business-contact-finder-mcp.ottobot2025.workers.dev/mcp"
}
}
}VS Code 的配置文件和另外三家不同：顶层键是 <code>servers</code>，远程端点还要写 <code>"type": "http"</code>。复制到 .vscode/mcp.json。
Claude Code（命令行）
claude mcp add --transport http modelcontextprotocol-registry https://business-contact-finder-mcp.ottobot2025.workers.dev/mcp
Claude Code 不收 JSON 文件，用这条命令直接加。
配置项的键名以你的客户端为准：客户端与 CLI
- 来源明细
- 收录自 abordage/awesome-mcp 榜单（我们从中收集的条目之一） · 条目类型：MCP 服务
- 收录与活跃
- 收录于 2026-11-05 · 最近见到 2026-11-14 · 共见到 10 次 · 被 10 个来源列出
- 评分构成
- 综合分 1,003 · 10 个来源 · mcp
常见问题（答案都来自我们的记录）
怎么安装？
我们【没有】从该仓库取到安装命令（我们的 install 覆盖率只有约 4%）。请看它的 README 或 releases 页。
它适合谁 / 用来做什么？
我们把它归在这些标签下: MCP 服务。标签来自条目自身，不是我们强加的分类。
谁维护它、还在更新吗？
我们收录于 2026-11-05；最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。
# MCP Registry
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
The MCP registry provides MCP clients with a list of MCP servers, like an app store for MCP servers.
📤 Publish my MCP server | ⚡️ Live API docs | 👀 Ecosystem vision | 📖 Full documentation
## Development Status
2025-10-24 update: The Registry API has entered an API freeze (v0.1) 🎉. For the next month or more, the API will remain stable with no breaking changes, allowing integrators to confidently implement support. This freeze applies to v0.1 while development continues on v0. We'll use this period to validate the API in real-world integrations and gather feedback to shape v1 for general availability. Thank you to everyone for your contributions and patience—your involvement has been key to getting us here!
2025-09-08 update: The registry has launched in preview 🎉 (announcement blog post). While the system is now more stable, this is still a preview release and breaking changes or data resets may occur. A general availability (GA) release will follow later. We'd love your feedback in GitHub discussions or in the #registry-dev Discord (joining details here).
Registry Working Group:
Radoslav (Rado) Dimitrov (Stacklok) @rdimitrov - WG Lead
Tadas Antanavicius (PulseMCP) @tadasant
Bob Dickinson (TeamSpark) @BobDickinson
Preeti (Pree) Dewani (Ravenmail) @pree-dew
## Contributing
We use multiple channels for collaboration - see modelcontextprotocol.io/community/communication.
Often (but not always) ideas flow through this pipeline:
Discord - Real-time community discussions
Discussions - Propose and discuss product/technical requirements
Issues - Track well-scoped technical work
Pull Requests - Contribute work towards issues
### Quick start:
#### Pre-requisites
Docker
Go - version per the go directive in go.mod; the Go toolchain fetches it for you
ko - Container image builder for Go (installation instructions)
golangci-lint - version per the golangci-lint-action pin in ci.yml, so local lint matches CI
#### Running the server
bash
# Start full development environment
make dev-compose
This starts the registry at localhost:8080 with PostgreSQL. The database uses ephemeral storage and is reset each time you restart the containers, ensuring a clean state for development and testing.
Note: The registry uses ko to build container images. The make dev-compose command automatically builds the registry image with ko and loads it into your local Docker daemon before starting the services.
By default, the registry seeds from the production API with a filtered subset of servers (to keep startup fast). This ensures your local environment mirrors production behavior and all seed data passes validation. For offline development you can seed from a file without validation with MCPREGISTRYSEEDFROM=data/seed.json MCPREGISTRYENABLEREGISTRYVALIDATION=false make dev-compose.
The setup can be configured with environment variables in docker-compose.yml - see .env.example for a reference.
Alternative: Running a pre-built Docker image
Pre-built Docker images are automatically published to GitHub Container Registry. Note that the image does not bundle PostgreSQL, so you need to run your own and point the registry at it via MCPREGISTRYDATABASEURL (see docker-compose.yml for a working example):
📤 Publish my MCP server | ⚡️ Live API docs | 👀 Ecosystem vision | 📖 Full documentation
## Development Status
2025-10-24 update: The Registry API has entered an API freeze (v0.1) 🎉. For the next month or more, the API will remain stable with no breaking changes, allowing integrators to confidently implement support. This freeze applies to v0.1 while development continues on v0. We'll use this period to validate the API in real-world integrations and gather feedback to shape v1 for general availability. Thank you to everyone for your contributions and patience—your involvement has been key to getting us here!
2025-09-08 update: The registry has launched in preview 🎉 (announcement blog post). While the system is now more stable, this is still a preview release and breaking changes or data resets may occur. A general availability (GA) release will follow later. We'd love your feedback in GitHub discussions or in the #registry-dev Discord (joining details here).
Registry Working Group:
Radoslav (Rado) Dimitrov (Stacklok) @rdimitrov - WG Lead
Tadas Antanavicius (PulseMCP) @tadasant
Bob Dickinson (TeamSpark) @BobDickinson
Preeti (Pree) Dewani (Ravenmail) @pree-dew
## Contributing
We use multiple channels for collaboration - see modelcontextprotocol.io/community/communication.
Often (but not always) ideas flow through this pipeline:
Discord - Real-time community discussions
Discussions - Propose and discuss product/technical requirements
Issues - Track well-scoped technical work
Pull Requests - Contribute work towards issues
### Quick start:
#### Pre-requisites
Docker
Go - version per the go directive in go.mod; the Go toolchain fetches it for you
ko - Container image builder for Go (installation instructions)
golangci-lint - version per the golangci-lint-action pin in ci.yml, so local lint matches CI
#### Running the server
bash
# Start full development environment
make dev-compose
This starts the registry at localhost:8080 with PostgreSQL. The database uses ephemeral storage and is reset each time you restart the containers, ensuring a clean state for development and testing.
Note: The registry uses ko to build container images. The make dev-compose command automatically builds the registry image with ko and loads it into your local Docker daemon before starting the services.
By default, the registry seeds from the production API with a filtered subset of servers (to keep startup fast). This ensures your local environment mirrors production behavior and all seed data passes validation. For offline development you can seed from a file without validation with MCPREGISTRYSEEDFROM=data/seed.json MCPREGISTRYENABLEREGISTRYVALIDATION=false make dev-compose.
The setup can be configured with environment variables in docker-compose.yml - see .env.example for a reference.
Alternative: Running a pre-built Docker image
Pre-built Docker images are automatically published to GitHub Container Registry. Note that the image does not bundle PostgreSQL, so you need to run your own and point the registry at it via MCPREGISTRYDATABASEURL (see docker-compose.yml for a working example):
收录徽章（可选）
想把收录标记放进 README 就复制这行，可选，不影响收录。
[](https://anclum.com/zh/s/modelcontextprotocol-registry/)
- 来源
- awesome · https://github.com/modelcontextprotocol/registry
- 按领域浏览
- MCP 服务
- 收录来源
- 10 个独立来源
- 收录于
- 今天
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。