modelcontextprotocol/registry
Watch
1
0
Fork
You've already forked registry
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update OpenAPI spec to use v0.1 endpoints and make _meta optional (#811)

Browse source 
Prepared by Claude Code, reviewed by me.

## Summary
- Update all API endpoint paths from `/v0/` to `/v0.1/` in the OpenAPI
spec
- Bump OpenAPI spec version from `2025-10-17` to `2025-12-01` (in `$id`
and `info.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 `_meta` optional in `ServerResponse`

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 registry-specific metadata fields, so
they should be optional.

### Move extensions docs to use /v0.1/ instead of /v0/

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude <noreply@anthropic.com>
This commit is contained in:
Tadas Antanavicius 2025-12-10 13:58:01 -08:00 • committed by GitHub
commit fdcb38537f
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 13 additions and 14 deletions
Download patch file Download diff file Expand all files Collapse all files

14
docs/reference/api/extensions.md
View file

@ -13,10 +13,10 @@ A standardized way for registries to provide experimental or community-driven fe
## URL Structure
Extensions live under the `/v0/x/` prefix:
Extensions live under the `/v0.1/x/` prefix:
```
/v0/x/<namespace>/<extension>[/<path>]
/v0.1/x/<namespace>/<extension>[/<path>]
```
**Components:**
@ -26,9 +26,9 @@ Extensions live under the `/v0/x/` prefix:
**Examples:**
```
/v0/x/com.example/search?q=database
/v0/x/com.example/stats
/v0/x/io.github.username/custom-feature
/v0.1/x/com.example/search?q=database
/v0.1/x/com.example/stats
/v0.1/x/io.github.username/custom-feature
```
## Conventions
@ -50,7 +50,7 @@ Clients consuming extensions **MUST** gracefully handle missing extensions.
A simple server stats extension:
```bash
GET /v0/x/com.example/stats
GET /v0.1/x/com.example/stats
```
```json
@ -63,7 +63,7 @@ GET /v0/x/com.example/stats
## Future Considerations
- **Extension discovery**: A potential `/v0/x` endpoint to list available extensions
- **Extension discovery**: A potential `/v0.1/x` endpoint to list available extensions
- **Extension metadata**: Standardized metadata format for extension capabilities
- **Defining common extensions**: Like semantic conventions from OpenTelemetry, develop common extensions that registries can adopt (possibly under an experimental namespace)
- Search extension for free-text search across server metadata ([#389](https://github.com/modelcontextprotocol/registry/issues/389))