blog: multi-user MCP with per-backend header forwarding#2329
Open
mohitgurnani1 wants to merge 3 commits into
Open
blog: multi-user MCP with per-backend header forwarding#2329mohitgurnani1 wants to merge 3 commits into
mohitgurnani1 wants to merge 3 commits into
Conversation
dosubot
Bot
added
the
size:XL
Adds a blog post covering per-backend header forwarding in MCPRoute (added in envoyproxy#2047, shipped in v0.6): the multi-user MCP problem with shared service accounts, when to choose header forwarding vs OAuth flows vs token exchange, PAT passthrough and OIDC/JWT configurations, and production experience running it at Nutanix across 10+ MCP backends. Includes three diagrams with draw.io sources under diagram-sources. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Signed-off-by: Mohit Gurnani <mohit.gurnani@nutanix.com>
mohitgurnani1
force-pushed
the
blog-multi-user-mcp
branch
from
July 6, 2026 00:30
ef209ec to
1f06ca8
Compare
dosubot
Bot
added
size:L
The decision-path image was committed but not referenced from the post. Embed it after the auth-pattern comparison table. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Signed-off-by: Mohit Gurnani <mohit.gurnani@nutanix.com>
Replace the company-specific production narrative with a generic enterprise scenario, per feedback. Matches the framing used by other feature blogs on the site. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Signed-off-by: Mohit Gurnani <mohit.gurnani@nutanix.com>
missBerg
self-requested a review
July 6, 2026 15:16
Contributor
|
Will take a look at this one! |
missBerg
added
area/mcp
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
3 participants
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.
Description
Adds a blog post covering per-backend header forwarding in MCPRoute (added in #2047, shipped in v0.6): the multi-user MCP problem with shared service accounts, how to choose between header forwarding, OAuth flows, and token exchange for downstream identity, and a practical walkthrough of both configuration levels (PAT passthrough and OIDC/JWT forwarding). Includes three diagrams; draw.io sources are included under site/blog/2026/diagram-sources.
Also adds my author entry to authors.yml.
Note: I used Claude Code (AI) as a writing and diagramming assistant. I fully understand and own all content in this PR.
Related Issues/PRs (if applicable)
Related PR: #2047
Related Issue: #1966
Related PR: #2092
Special notes for reviewers (if applicable)
Verified locally with a full Docusaurus build (npm run build passes; the only broken-anchor warnings are pre-existing in old versioned docs). All YAML examples in the post are validated against the v1beta1 MCPRoute schema.