Improve MCP docs setup and authentication flow#438
Draft
thebiglabasky wants to merge 1 commit into
Draft
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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
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
list-test-session-resultstool to the tools reference.Why
The OAuth client instructions grew incrementally, and the later API-key section was inserted in the middle of the client sequence. That made readers choose between auth methods and clients at the same level, while service-key account/role behavior was spread across setup, security, and troubleshooting. The Codex OAuth limitation also described callback-port behavior that is no longer current.
User impact
Readers now choose an auth method before entering client-specific instructions. OAuth remains the recommended interactive path, while user and service API keys have clear fallback and automation guidance. Troubleshooting follows the same structure as setup, making auth, role, account, and missing-tool failures easier to isolate.
Validation
checkly/monorepoorigin/main.claude,devin,opencode, andcodexcommand syntax; exercised the Codex bearer-token setup in an isolated config.npm exec -- mint broken-linkspython3 .github/scripts/check_frontmatter.pypython3 .github/scripts/check_redirect_destinations.pynpm run generate-sitemapgit diff --check