Update from code changes: MCP always-allowed clients#6395
Merged
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
densumesh
approved these changes
Jul 6, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
Updates the search MCP redirect URI guidance to reflect that popular clients (Claude, ChatGPT, Cursor, Devin) are now always allowed and do not need to be added to a deployment's allowlist.
Changes
ai/model-context-protocol.mdxto state that popular clients are always allowed and the dashboard is only for custom domains.es/ai/model-context-protocol.mdx.Context
Predefined-client toggles were removed from the dashboard MCP settings page. Known first-party MCP clients are now allowed server-side by default, so users only configure the dashboard when they need to allow additional custom clients.
Note
Low Risk
Documentation-only wording updates across MCP auth setup pages; no application code or security behavior changes in this PR.
Overview
Updates the Enable authenticated MCP section in
model-context-protocol.mdx(and es, fr, zh locales) so OAuth redirect guidance matches the product change: Claude, ChatGPT, Cursor, and Devin can complete OAuth without being on a deployment allowlist.The docs no longer imply that web tools must be allowlisted by default or that the MCP server is localhost-only. Allowed OAuth redirect URIs in the dashboard is framed as custom redirect domains for additional web clients only. The setup step was renamed accordingly and no longer tells readers to add common domains like
claude.aiorvscode.dev/redirect.Reviewed by Cursor Bugbot for commit 7835ca4. Bugbot is set up for automated code reviews on this repo. Configure here.