github-mcp-proxy

github-mcp-proxy

A self-hosted GitHub MCP server with per-repository guardrails for AI agents, enabling fine-grained access control and audit trails.

Category
访问服务器

README

github-mcp-proxy

A self-hosted GitHub MCP server running on Cloudflare Workers, designed for personal / small-team use with per-repository guardrails for AI agents.

Any MCP-capable agent (Claude, Codex, ChatGPT, Cursor, Cline, …) can be plugged in — with tight control over which repos it can touch and how.

[!WARNING] If you need security or stability, use the official GitHub MCP server. Fork freely; security issues are your responsibility once forked.

Why

Generic GitHub tokens give an agent full account access. This server narrows that down:

  • Per-repo permission levels — read / issues / full
  • Branch protection — new branches must match a prefix (default claude/); main/master never writable
  • Commit-message policy — Conventional Commits, validated server-side
  • Label whitelist — allowedLabels per repo; the server never auto-creates labels on GitHub
  • Forbidden paths — .github/workflows/** always blocked
  • Audit trail — every write auto-appends Signed-off-by / Assisted-by trailers or a footer identifying the agent and model

Architecture

 MCP agent ──(Streamable HTTP + OAuth)──▶ Cloudflare Worker
                                              │
                                              ├── workers-oauth-provider  (OAuth 2.1 server to MCP clients)
                                              ├── GitHub OAuth            (OAuth client to github.com)
                                              ├── KV                      (session tokens)
                                              ├── Durable Object          (MCP agent state)
                                              └── Octokit                 (GitHub REST)

Config (ghmcp.config.ts) is bundled with the Worker at deploy time — no runtime KV reads, typechecked via satisfies.

Quick start

git clone <your-fork>
cd kz-github-mcp
npm install
cp ghmcp.config.sample.ts ghmcp.config.ts   # edit: repos you want to expose
cp wrangler.sample.jsonc wrangler.jsonc      # edit: KV id + worker name
cp .env.example .env                         # edit: for local dev only

Create a GitHub OAuth App (Homepage = https://<worker>.<subdomain>.workers.dev, Callback = /callback), then:

wrangler kv namespace create "OAUTH_KV"      # add the id to wrangler.jsonc
wrangler secret put GITHUB_CLIENT_ID
wrangler secret put GITHUB_CLIENT_SECRET
wrangler secret put COOKIE_ENCRYPTION_KEY    # openssl rand -hex 32
npm run deploy

Local development: same flow with a second OAuth App pointing at http://localhost:8788, credentials in .env, then npm run dev.

Continuous deployment (optional)

.github/workflows/deploy.yml deploys to Cloudflare on every push to main. Set two repo secrets in GitHub Settings → Secrets and variables → Actions:

Secret Where to get it
CLOUDFLARE_API_TOKEN Cloudflare dashboard → My Profile → API Tokens → create a token with the "Edit Cloudflare Workers" template
CLOUDFLARE_ACCOUNT_ID Cloudflare dashboard → right sidebar of any Workers page

The GitHub OAuth credentials (GITHUB_CLIENT_ID, GITHUB_CLIENT_SECRET, COOKIE_ENCRYPTION_KEY) live as Wrangler secrets on the Worker itself, not in GitHub Actions — you only need to set them once with wrangler secret put.

See docs/ARCHITECTURE.md for how it works, docs/CONFIG.md for every config field.

Connect an AI agent

Claude (claude.ai) — Settings → Connectors → Add custom connector → paste https://<worker>.<subdomain>.workers.dev/sse.

Claude Code / Codex / Cursor / Cline — add to the client's MCP config:

{
  "mcpServers": {
    "github": {
      "command": "npx",
      "args": ["mcp-remote", "https://<worker>.<subdomain>.workers.dev/sse"]
    }
  }
}

Any MCP host — point it at the same /sse endpoint. OAuth flow runs on first connect.

Tools

Prefixed with ghmcp_. Each declares a minimum permission level; the server denies calls below that.

Category Tools Min level
User get_me read
Repo list_repos, get_file_content, search_code read
Issues list_issues, get_issue, search_issues, list_issue_comments read
Issues create_issue, update_issue, add_issue_comment issues
PRs list_pull_requests, get_pull_request read
PRs create_pull_request issues
Files create_or_update_file, create_branch full
Actions list_workflow_runs, get_workflow_run_logs read

Any tool can be disabled via disabledTools in the config.

Validation

npm run validate-config

Uses the gh CLI to confirm that every repo in ghmcp.config.ts exists and that every label in allowedLabels is present on GitHub. Runs automatically as a prebuild hook, so a typo fails npm run build.

License

Originally forked from cloudflare/ai/demos/remote-mcp-github-oauth. MIT-licensed.

This tool is MIT-licensed. — see LICENSE.

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。

官方
精选
本地
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。

官方
精选
本地
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选
Neon MCP Server

Neon MCP Server

用于与 Neon 管理 API 和数据库交互的 MCP 服务器

官方
精选
Exa MCP Server

Exa MCP Server

模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选