Update OpenAPI spec to use v0.1 endpoints and make _meta optional#811
Merged
Update OpenAPI spec to use v0.1 endpoints and make _meta optional#811
Conversation
- Update all API endpoint paths from /v0/ to /v0.1/ - Bump schema version from 2025-10-17 to 2025-12-01 - Regenerate server.schema.json with updated version This ensures sub-registries implementing the spec are adhering to the stable v0.1 version rather than the unstable v0. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
The OpenAPI spec version (2025-12-01) is separate from the server.json $schema version that the backend validates. The example should continue to point to 2025-10-17 which is the currently supported schema version. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
PR #803 decouples server.schema.json versioning from openapi.yaml by using a draft URL scheme. This PR should only update the OpenAPI spec endpoints and version, not the server.schema.json. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
The _meta field and its io.modelcontextprotocol.registry/official extension were never intended to be required parts of the spec. Sub-registries may not use these fields, so they should be optional. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
tadasant
changed the title
Update all API endpoint paths from /v0/ to /v0.1/ in the extensions specification, consistent with the rest of the API documentation. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
domdomegg
approved these changes
Dec 10, 2025
rdimitrov
approved these changes
Dec 10, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prepared by Claude Code, reviewed by me.
Summary
/v0/to/v0.1/in the OpenAPI spec2025-10-17to2025-12-01(in$idandinfo.version)Rationale
This ensures sub-registries implementing the spec are adhering to the stable v0.1 version rather than the unstable v0. The API freeze (v0.1) provides stability guarantees that sub-registries need.
Additional cleanup
Make
_metaoptional inServerResponseThe
_metafield (and itsio.modelcontextprotocol.registry/officialextension) were never intended to be required parts of the spec. Sub-registries may not use these registry-specific metadata fields, so they should be optional.Move extensions docs to use /v0.1/ instead of /v0/
🤖 Generated with Claude Code