Conversation
Add `auth.type: github-oidc` option to the HTTP MCP servers section in the guide. The compiler has supported this field since the gateway OIDC implementation (gh-aw-mcpg PR #2878) but the how-to guide only showed static `headers`-based authentication. Fixes documentation gap surfaced by #23605. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
pelikhan
approved these changes
Mar 31, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the MCP servers guide to document GitHub Actions OIDC-based upstream authentication for HTTP MCP servers, closing a gap where only static headers auth was previously shown.
Changes:
- Clarifies that HTTP MCP servers can authenticate via static
headersor dynamicauth. - Adds a “GitHub Actions OIDC Authentication” section with required
permissions: id-token: writeand anauth.type: github-oidcexample. - Links readers to the MCP Gateway reference spec section for detailed behavior and rules.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
Self-Healing Documentation Fixes
This PR was automatically created by the Daily Documentation Healer workflow.
Gaps Fixed
auth.type: github-oidcdocumentation toguides/mcps.md. The compiler (pkg/workflow/mcp_config_validation.go) already supports this field, and the gateway spec (mcp-gateway.md§7.6) already documents the protocol-level behavior, but the how-to guide for workflow authors only showed staticheaders-based authentication. Users following the guide had no indication that dynamic OIDC token acquisition was available.Root Cause
DDUw missed issue #23605 because it was created and closed on the same day (2026-03-31, before DDUw's daily 6am UTC run). When DDUw ran, the issue did not yet appear in the "recently closed" window. The spec and schema updates (§7.6 and
mcp-gateway-config.schema.json) were applied directly by the issue author, so no[docs]PR was ever created — leaving the user-facing guide (guides/mcps.md) undocumented.💡 DDUw Improvement Suggestions
DDUw Improvement Suggestions
Pattern: Issues closed as
completedby the author on the same day they were filed, without a[docs]PR, can slip through DDUw's Step 1c scan if DDUw has already run that day.Specific failure: Step 1c scans for
closed:>=7-days-ago, but the check for whether a[docs]PR exists only looks at merged PRs — it does not check whether the documentation file already reflects the change. If the author fixed docs directly (commit, not PR), DDUw Step 1c would treat the issue as "unaddressed" but the guide check would find the docs already present and skip. Theguides/mcps.mdcase was different: the spec was updated but the guide was not, so neither DDUw's PR check nor its doc-present check would have caught the gap.Suggested addition to Step 1c: When an issue describes a new feature or field, also search semantic docs (
search("field-name usage example")) for guide pages, not just reference pages. Reference pages are often updated first (as was the case here withmcp-gateway.md), leaving how-to guides stale.Related Issues
References: §23799486262