<!-- Provide a brief summary of your changes --> ## Motivation and Context Added a fully client-side browser for MCP registry APIs to the `community-projects.md` documentation page: https://vemonet.github.io/mcp-registry I built it because I was missing a way to easily configure a server and export the configuration (existing browsers I have found show the available parameters, but you still need to manually build the JSON): - It shows a user friendly form that enables to configure MCP servers based on their registry entry, making it easier to understand and fill the configuration required for deploying a server (instead of having to read through JSON, and manually build another JSON). Then users can either copy the generated config or install in client with custom URL handler like VSCode/cursor in 1 click - It is a thin client UI layer over the existing registry API, it does not offer additional classification, complex filtering, or semantic search (we don't use an additional server or database). So it is more of a tool to make it user friendly to directly access a raw registry content and inspects available servers, than an opinionated browser with advanced search capabilities ## How Has This Been Tested? <!-- Have you tested this in a real application? Which scenarios were tested? --> ## Breaking Changes <!-- Will users need to update their code or configurations? --> ## Types of changes <!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [x] Documentation update ## Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. --> - [x] I have read the [MCP Documentation](https://modelcontextprotocol.io) - [x] My code follows the repository's style guidelines - [ ] New and existing tests pass locally - [ ] I have added appropriate error handling - [x] I have added or updated documentation as needed ## Additional context <!-- Add any other context, implementation notes, or design decisions -->
3 KiB
3 KiB
Community Projects
The following is a list of notable community-driven projects in the ecosystem related to the MCP Registry.
Featured Projects
Browsers 🔎
Browse the official MCP Registry in your browser!
- MCP Bench🔎 - Explore the MCP registry with richer filters, community stars, and LLM-generated classification tags.
- MCP Registry Database🔎 - A minimal, web browsable, live database of the official MCP Registry source code.
- TeamSpark AI Server Registry🔎 - Browse and discover servers from the official MCP Registry (source code).
- MCP Registry UI🔎 - A fully client‑side app to search, filter, configure, and install servers from MCP Registry APIs (source code).
MCP Registry Clients
- REST API - HTTP API
- go-mcp-registry - Go SDK
- mcp-registry-spec-sdk - TypeScript client for the MCP Registry
- LangChain4j MCP Registry Java client - Java API
Other
- MCP Registry Cheat Sheet - MCP Registry Cheat Sheet for MCP server developers, client developers, and registry admin
- MCP Registry Remote MCP Server - Open Remote MCP server for the Registry at
https://registry-mcp.remote-mcp.com - MCP Server for MCP Registry - MCP Server to discover and search for available MCP servers in the registry
- mcp-insights - Analytics and insights for the MCP Registry
- mcp-registry-cli - CLI tool to navigate the MCP registry servers
- OtherVibes/mcp-publish-action - GitHub Action for publishing MCP servers to the official registry
- ToolSDK MCP Registry - Extends the MCP Registry with API-based MCP execution, private deployment, and secure sandbox isolation.
Adding Your Project
To add your community project, submit a pull request adding a one-line entry above with format: [project-name](link) - brief description
Disclaimer
This is not an exhaustive list, and inclusion does not imply endorsement. Projects are maintained by third parties and may not be actively supported, secure, or compatible with the latest MCP Registry version. Please review each project independently and use at your own risk!