Repository navigation
Make draft schema URL point to actual location #814
Description
(Issue drafted by Claude Code, finalized by me)
Context
Follow-up from PR #803 (#803 (comment))
In PR #803, the schema URL label was updated to clarify that the in-repo schema is a draft version, using the URL:
https://static.modelcontextprotocol.io/schemas/draft/server.schema.json
Problem
This draft schema URL does not actually exist, which could confuse users who try to access it directly. While the label helps distinguish the in-repo version from finalized versions in static hosting, the non-existent URL is misleading.
Proposed Solution
Update the reference to point more directly at the current draft location (e.g., a raw GitHub URL to the schema in the repo)
Priority
Low priority - the main goal of distinguishing draft vs released schemas was achieved in #803. This is a polish improvement.
Activity
[-]Make draft schema URL accessible or point to actual location[/-][+]Make draft schema URL point to actual location[/+]deerajkumar18 commentedon Jan 10, 2026
@tadasant I'd like to work on this issue .
update schema url point to the actual location (#884)
rdimitrov commentedon Oct 23, 2026
The draft schema reference is now corrected on
main: both the schema$idand the contributing guide use the real raw GitHub URL, https://raw.githubusercontent.com/modelcontextprotocol/registry/main/docs/reference/server-json/draft/server.schema.json . The obsolete static/schemas/draft/URL still returns 404, but the maintained reference no longer points there. Closing this reference-correction request as completed.