[Doc] Update links of the MCP specification #92
Conversation
README.md
Outdated
| If an invalid `protocol_version` value is set, an `ArgumentError` is raised. | ||
|
|
||
| Be sure to check the [MCP spec](https://modelcontextprotocol.io/specification) for the protocol version to understand the supported features for the version being set. | ||
| Be sure to check the [MCP spec](https://modelcontextprotocol.io/specification/2025-06-18) for the protocol version to understand the supported features for the version being set. |
There was a problem hiding this comment.
| Be sure to check the [MCP spec](https://modelcontextprotocol.io/specification/2025-06-18) for the protocol version to understand the supported features for the version being set. | |
| Be sure to check the [MCP spec](https://modelcontextprotocol.io/specification/latest) for the protocol version to understand the supported features for the version being set. |
There was a problem hiding this comment.
(unfortunately it doesn't work for nested links)
There was a problem hiding this comment.
Yeah. The other links don't support URLs like specification/latest/server/tools.
Therefore, the links in this README document point to the specification with the consistent version 2025-06-18.
In the future, if the MCP specification supports URLs such as specification/latest/server/tools, all links may be updated to latest at that time.
There was a problem hiding this comment.
Since the implementation/release of the gem will usually be locked to a certain version of the spec, it's probably fine to use the version in these paths?
There was a problem hiding this comment.
Ah, I see. This section of the README refers to the protocol version, so I've updated the URL to https://modelcontextprotocol.io/specification/versioning. This page may be more appropriate for understanding the specification in relation to protocol versions.
Additionally, since it is currently the redirect target of https://modelcontextprotocol.io/specification, this change also helps avoid an unnecessary redirect.
What do you think?
Follow-up to modelcontextprotocol/modelcontextprotocol@0695a497. This PR updates URLs that were changed due to the redesign of the MCP website: https://modelcontextprotocol.io
koic
force-pushed
the
update_links_of_mcp_specification
branch
from
ca84a3f to
eaa9d58
Compare
3 participants
Motivation and Context
Follow-up to modelcontextprotocol/modelcontextprotocol@0695a497.
This PR updates URLs that were changed due to the redesign of the MCP website:
https://modelcontextprotocol.io
Types of changes
Checklist