Remote MCP: Support RFC 7591 DCR & OIDC refresh tokens for Google Gemini Web/Mobile Custom Apps (with stateless Cloud Run workaround)
维护者通常 2 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 8/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- go
- 领域
- api, authentication
调研方向
The payload names the endpoints /.well-known/oauth-authorization-server, /register and the /mcp Streamable HTTP route, plus the token exchange that needs Accept: application/json. Start by finding where the server's OAuth discovery and token handling live, then decide whether RFC 7591 registration and refresh tokens belong in this server or upstream. Done would mean a maintainer-agreed design, since the issue asks for a feature and links an external workaround rather than a specific change.
由索引模型根据 Issue 内容生成。
描述
Problem Description
When connecting the hosted remote GitHub MCP endpoint to MCP clients that rely on the standard MCP Authorization specification—specifically Google Gemini Web & Mobile Custom Apps and Gemini CLI—connections either fail during initial setup or silently drop after ~24 hours:
- Missing Dynamic Client Registration (RFC 7591): Clients attempting automated registration against
/.well-known/oauth-authorization-server//registerfail, forcing users to manually create and manage a custom GitHub OAuth App with a static Client ID and Client Secret. - Discovery Path & Token Refresh Quirks: Standard GitHub OAuth Apps do not issue non-expiring OIDC refresh tokens by default, and token endpoint exchanges without explicit
Accept: application/jsonreturnapplication/x-www-form-urlencodedpayloads. When mobile/web MCP clients attempt background validation or token refresh across sessions, the connector is silently disabled.
Workaround / Community Reference Implementation
Until native RFC 7591 DCR (or CIMD) and seamless refresh token support are available on the hosted remote MCP endpoint, I built an open-source, stateless Cloud Run OAuth 2.1 + DCR proxy that sits in front of the hosted GitHub MCP server:
👉 https://github.com/wihl/gemini-github-connector
- Full RFC 9728, RFC 8414, and RFC 7591 (
/register) support: Gemini Web & iOS Mobile connect immediately without manual OAuth Client ID/Secret entry. - Stateless HMAC-SHA256 signed JWTs (Zero Database): Backed by GCP Secret Manager so Cloud Run scale-to-zero events and background refreshes never invalidate the session.
- Strict
application/jsontoken responses: Proxies Streamable HTTP/mcptraffic upstream using your Secret Manager GitHub PAT.
Deploys to Cloud Run free tier in ~2 minutes via ./scripts/deploy.sh. Sharing this here both as a feature request for seamless Gemini Web/Mobile compatibility and as a drop-in workaround for anyone trying to use github-mcp-server from Gemini Mobile/Web today.
- 主要语言
- Go
- 星标
- 34.2k
- 派生
- 5.3k
- 平均合并
- 5 天 18 小时
- 30 天内合并 PR
- 13
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
github/github-mcp-server 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 69/100
github/github-mcp-server#3760 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
github/github-mcp-server#3758 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 69/100
github/github-mcp-server#3729 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
github/github-mcp-server#3722 ·
维护者通常 2 天内回复
-
Insiders Feedback: PR created UI doesn't link to the PR可能已有人在做 @genius-0963 于 5 天前认领。 未关闭bug insiders user-experience
难度 2/5 1-3 小时 新手友好度 65/100
github/github-mcp-server#3658 ·
维护者通常 2 天内回复
查看 github/github-mcp-server 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 72/100
open-feature/flagd-schemas#237 ·
-
enhancement
难度 2/5 1-3 小时 新手友好度 72/100
superplanehq/superplane#9234 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
betterleaks/betterleaks#469 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
prime-radiant-inc/evener#5901 ·
维护者通常 1 天内回复