- Notifications
You must be signed in to change notification settings - Fork1.4k
Updated links to MCP Specification indocs/host-integration.md
#641
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Merged
+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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Pull Request Overview
This PR updates hyperlinks indocs/host-integration.md
to point from the draft MCP specification to the newly released 2025-06-18 version.
- Replaced the general MCP specification link
- Updated the OAuth authorization flow link
Comments suppressed due to low confidence (3)
docs/host-integration.md:67
- It looks like the list marker (
-
) was removed from this line, which may break the Markdown list formatting. Consider re-adding it for consistent bullet styling.
For more detail, see the [official MCP specification](https://modelcontextprotocol.io/specification/2025-06-18).
docs/host-integration.md:87
- The leading list marker (
-
) was removed here as well. Restoring it will keep this line in the intended list context.
The expected flow for obtaining a valid access token via OAuth is depicted in the [MCP Specification](https://modelcontextprotocol.io/specification/2025-06-18/basic/authorization#authorization-flow-steps). For convenience, we've embedded a copy of the authorization flow below. Please study it carefully as the remainder of this document is written with this flow in mind.
docs/host-integration.md:67
- [nitpick] If the site supports a stable
latest
alias, consider using/specification/latest
instead of a hard-coded date to automatically track future updates.
For more detail, see the [official MCP specification](https://modelcontextprotocol.io/specification/2025-06-18).
LuluBeatson approved these changesJul 7, 2025
fc11713
intomain 16 checks passed
Uh oh!
There was an error while loading.Please reload this page.
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
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.
This is a simple documentation update. Now that the draft MCP Specification has been promoted to "latest," we were overdue to update these hyperlinks.