Skip to content

[Doc] Update links of the MCP specification #92

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

koic
Copy link
Member

@koic koic commented Jul 26, 2025

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

  • 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

  • I have read the MCP Documentation
  • 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

README.md Outdated
@@ -340,7 +340,7 @@ MCP::Server.protocol_version = nil

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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(unfortunately it doesn't work for nested links)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 koic force-pushed the update_links_of_mcp_specification branch from ca84a3f to eaa9d58 Compare July 27, 2025 17:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants