| Filename | Latest commit message | Latest commit date |
|---|---|---|
694a4d8879Fixes #96 ## Motivation and Context See #96 ## How Has This Been Tested? Has some unit and integration tests, still needs proper testing of the different registry types ## Breaking Changes Yes, new package uploads will need extra verification ## 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) - [x] New feature (non-breaking change which adds functionality) - [x] Breaking change (fix or feature that would cause existing functionality to change) - [ ] Documentation update |
||
| .. | ||
| publisher | ||
| server-json | ||
| server-registry-api | ||
| admin-operations.md | ||
| architecture.md | ||
| design_principles.md | ||
| ecosystem-diagram.excalidraw.svg | ||
| faq.md | ||
| MCP Developers Summit 2025 - Registry Talk Slides.pdf | ||
| moderation-guidelines.md | ||
| new_package_registry.md | ||
| README.md | ||
| roadmap.md | ||
| versioning.md | ||
Official Registry Documentation
This extends the main README.
Project Documentation
faq.md- Frequently asked questions about the MCP Registrydesign_principles.md- Core constraints and principles guiding the registry designroadmap.md- High-level roadmap for the MCP Registry developmentMCP Developers Summit 2025 - Registry Talk Slides.pdf- Slides from a talk given at the MCP Developers Summit on May 23, 2025, with an up-to-date vision of how we are thinking about the official registry.
API & Technical Specifications
openapi.yaml- OpenAPI specification for the official registry APIapi_examples.md- Examples of what data will actually look like coming from the official registry APIarchitecture.md- Technical architecture, deployment strategies, and data flowsserver.jsonREADME - description of theserver.jsonpurpose and schemanew_package_registry.md- steps to add a new package registry for local server packages