| Filename | Latest commit message | Latest commit date |
|---|---|---|
1df37373c4## Description This PR addresses #300 by adding explicit versioning to the MCP Registry API OpenAPI specification. ## Changes - Added `version: "2025-07-09"` field to the `info` section of the OpenAPI specification - Maintains consistency with existing date-based versioning used across all schema files ## Rationale As outlined in #300, the OpenAPI spec was missing an explicit version field, which could lead to: - Compatibility issues as the API evolves - Lack of clarity for API consumers - Missing functionality in OpenAPI tooling that expects a version field This follows the MCP specification's date-based versioning approach. Closes #300 |
||
| .. | ||
| server-json | ||
| server-registry-api | ||
| architecture.md | ||
| design_principles.md | ||
| ecosystem-diagram.excalidraw.svg | ||
| faq.md | ||
| MCP Developers Summit 2025 - Registry Talk Slides.pdf | ||
| 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