Connecting Github Public MCP Server with Gateway - Auth issue #309
Unanswered
anirudhgargi
asked this question in
Q&A
Replies: 1 comment
-
Hi, Please check out [Feature Request]: HTTP Header Passthrough #208 and let me know if this would resolve the issue. Please add any comments, suggested test scenarios or ideas to #208 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
In our deployments we would want the agents (users) be able to use their own Github PAT and connect to the Gateway, which passes the Github PAT transparently to the Github MCP.
Example flow.
IDE/Agent
│ Authorization: Bearer
│ X-Upstream-Authorization: Bearer
▼
MCP Gateway (validates JWT, forwards PAT header)
│ Authorization: Bearer
▼
GitHub MCP server (calls api.github.com with PAT scopes)
│
▼
GitHub REST APIs
Issue that i am facing is that the Public Github MCP server does not gets added in our Gateway without a auth credential (either a PAT or OAuth). I cannot provide the user auth here as this is done at the Organization level.
One way, i can think of is we create a dummy PAT when registering MCP server to Gihub MCP, later the request shall have the the PAT of the users when making the actual tool call. Is this a correct way ? Seems like a hack.
Another way i see we stand-up local GH server and make some tweaks. But thinking of future, where there are other public MCP servers to connect to and they shall have some auth to connect.
How does MCP Gateway add these type of MCP servers.
Any suggestions ?
Beta Was this translation helpful? Give feedback.
All reactions