Add PAT/SAT authentication to MCP Server setup docs#37957
Open
rgwood-dd wants to merge 1 commit into
Open
Conversation
rgwood-dd
changed the title
rgwood-dd
force-pushed
the
reilly.wood/mcp-server-pat-sat-auth
branch
from
02ebb3c to
6730603
Compare
Contributor
|
Contributor
Preview links (active after the
|
Document Personal and Service Access Tokens as the preferred header-based auth option for the MCP Server, passed as a bearer token in the Authorization header. Verified against the MCP server that a PAT authenticates this way. Keep OAuth as the recommended method for most users, and the API and application key pair as the other header option. Links out to the PAT/SAT docs for scopes and token management. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
rgwood-dd
force-pushed
the
reilly.wood/mcp-server-pat-sat-auth
branch
from
6730603 to
efa9097
Compare
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.
What does this PR do? What is the motivation?
The MCP Server setup docs only documented two auth options: OAuth and the older API key + application key header pair. It did not mention the newer PAT+SAT approaches, this PR fixes that.
I verified against the MCP server that a PATs work.
Merge instructions
Merge readiness:
Additional notes