| Filename | Latest commit message | Latest commit date |
|---|---|---|
d3d137e170<!-- 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 --> |
||
| .. | ||
| administration | ||
| contributing | ||
| design | ||
| modelcontextprotocol-io | ||
| reference | ||
| community-projects.md | ||
| README.md | ||
MCP Registry Documentation
The MCP registry provides MCP clients with a list of MCP servers, like an app store for MCP servers.
I want to...
- 📤 Publish my MCP server → Publishing Guide
- 📥 Consume registry data → API Usage Guide
- 🔌 Understand the registry's purpose → Ecosystem vision
- 📋 Look up specific information → server.json spec | API spec | CLI reference
- 🤝 Add reference to my community project → Community Projects
Documentation Index
- 📄 Public-facing docs - Published on modelcontextprotocol.io
- 🏗️ Design documentation - Architecture, vision, and roadmap
- 📖 Reference - Technical specifications
- 🔧 Contributing guides - How to contribute
- 🔒 Administration - Admin operations