fix: Update spec links to new modelcontextprotocol.io location #1491
+2
−2
Conversation
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
The spec has moved from spec.modelcontextprotocol.io to modelcontextprotocol.io/specification/. Updated all references to point to the 2025-06-18 versioned spec.
felixweinberger
added
the
documentation
felixweinberger
requested changes
Oct 17, 2025
There was a problem hiding this comment.
Good find!
Can we point to https://modelcontextprotocol.io/specification/latest instead potentially?
I think that should always point to the latest released spec.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Summary
The MCP specification has moved from
spec.modelcontextprotocol.iotomodelcontextprotocol.io/specification/. This PR updates all references in the README to point to the new location.Changes
modelcontextprotocol.io/specification/2025-06-18Discussion Point
This PR uses the versioned spec URL (
/specification/2025-06-18) for stability. We should discuss whether to:/specification/draft(always points to latest, but may change)