me: header-auth Connect snippets when interactive login is unavailable - #15
Merged
Conversation
Without the OAuth facade (no PRM/DCR) the URL-alone `claude mcp add` flow can't authenticate, but the Connect section showed it anyway. When /health reports login: false the CLI and JSON snippets now include the Authorization: Bearer header with a placeholder, plus an opt-in checkbox that embeds the signed-in user's own token (off by default — the CLI command lands in shell history, and the note says to prefer the JSON config where that matters). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
Follow-up to #14. On token-only deployments the Connect section showed the URL-alone
claude mcp addcommand, which can't work there — without interactive login the OAuth facade (PRM + DCR) isn't mounted, so MCP clients must send the bearer token themselves.When
/healthreportslogin: false, the Connect section now:--header "Authorization: Bearer <your-bearer-token>"and the JSON config with a matchingheadersblock;OAuth-enabled deployments are untouched —
login: truekeeps the zero-config snippets exactly as before.Test plan
npm test— 211 passed (frontend-only change)--headerplaceholder variant; checkbox swaps in the real token and back;POST /mcpwith that exact header returns 200; scope checkbox still refreshes both snippets🤖 Generated with Claude Code