docs: document GitHub OIDC audience binding for self-hosters and CI users#1230
Merged
Conversation
…sers Follow-up to #1229. Three small additions so the new audience requirement is discoverable without reading the source: - .env.example lists MCP_REGISTRY_GITHUB_OIDC_AUDIENCE alongside the other registry env vars, with a note that the value must match scheme+host of the URL publishers pass via --registry. - The publisher CLI reference explains the new audience derivation and what self-hosters need to configure server-side. - The GitHub Actions troubleshooting table maps the new "invalid audience" error to the user-facing fix (upgrade mcp-publisher). Co-Authored-By: Claude Opus 4.7 (1M context) <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 #1229. Three small doc additions so the new audience requirement is discoverable without reading the source:
.env.examplelistsMCP_REGISTRY_GITHUB_OIDC_AUDIENCEalongside the other registry env vars, with a note that the value must match the scheme+host that publishers pass via--registry.docs/reference/cli/commands.md) explains that the CLI derives the audience from--registryand that self-hosters must set the matching env var on the registry side.docs/modelcontextprotocol-io/github-actions.mdx) maps the newinvalid audienceerror to the user-facing fix (upgrademcp-publisher).No code changes — docs only.
Test plan
🤖 Generated with Claude Code