modelcontextprotocol/registry
Watch
1
0
Fork
You've already forked registry
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
registry/docs/reference/server-json/CONTRIBUTING.md
deerajkumar18 b5f38fcc2a
 update schema url point to the actual location (#884) 
<!-- Provide a brief summary of your changes -->

## Motivation and Context
This PR ensures that the draft URL points to the actual draft schema 
improvement suggested in
https://github.com/modelcontextprotocol/registry/issues/814


## 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: -->
- [x] 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)
- [ ] Documentation update

## Checklist
<!-- Go over all the following points, and put an `x` in all the boxes
that apply. -->
- [ ] I have read the [MCP
Documentation](https://modelcontextprotocol.io)
- [ ] My code follows the repository's style guidelines
- [ ] New and existing tests pass locally
- [ ] I have added appropriate error handling
- [ ] I have added or updated documentation as needed

## Additional context
<!-- Add any other context, implementation notes, or design decisions
-->
2026-02-10 13:32:58 -08:00

1.6 KiB
Raw Permalink Blame History

Contributing to server.json Schema

This document describes the process for making and releasing changes to the server.json schema.

Making Changes

  1. Modify the OpenAPI spec: Edit docs/reference/api/openapi.yaml with your schema changes. The ServerDetail component defines the server.json structure.

  2. Regenerate the schema: Run make generate-schema to update server.schema.json from the OpenAPI spec.

  3. Update the changelog: Add your changes to the "Draft (Unreleased)" section in CHANGELOG.md.

  4. Open a PR: Submit a pull request to this repository for review.

Releasing Changes

When the draft changes are ready for release:

  1. Update the changelog: Move changes from "Draft (Unreleased)" to a new dated section (e.g., ## 2025-XX-XX).

  2. Update the schema URL: Change the $id in the schema and the example URL in openapi.yaml from draft to the release date (e.g., 2025-XX-XX).

  3. Merge the PR: Get approval and merge the changes to main.

  4. Publish to static hosting: Open a PR on modelcontextprotocol/static to add the new versioned schema file. This "locks in" the released schema at its versioned URL.

Schema Versioning

  • Draft schema: https://raw.githubusercontent.com/modelcontextprotocol/registry/main/docs/reference/server-json/draft/server.schema.json - For in-progress changes, may change without notice.
  • Released schemas: https://static.modelcontextprotocol.io/schemas/YYYY-MM-DD/server.schema.json - Stable, versioned by release date.