Github Mcp Connector

io.github.FerhatDundar由 GitHub 账号 FerhatDundar 发布v0.1.1更新于 Oct 24, 2026

MCP server for GitHub: repos, files, issues, PRs, search. Single Go binary.

已验证STDIO仅桌面知识与记忆开发者工具

概览

AI 生成的概览

一个本地运行的 Go MCP 服务器,为助手提供 18 个工具,用于读写 GitHub 仓库、文件、议题、拉取请求并进行搜索。

可以做什么
识别已认证的 GitHub 用户,列出或查看仓库、分支和提交,并可创建仓库、使用 GitHub 搜索限定符检索。读取文件内容或列出目录,并通过提交创建或更新文件(上限 5 MB)。列出、查看、创建和更新议题,并为议题或拉取请求添加评论。列出和查看拉取请求,新建拉取请求并将其合并。每次调用可选择 markdown 或 JSON 输出。
适用场景
适合需要助手直接操作真实 GitHub 仓库的场景:查看代码与提交历史、提交或分诊议题、提交文件改动,以及在对话中创建或合并拉取请求。
运行要求
以 stdio 本地进程方式运行,提供 macOS、Linux 和 Windows 的 amd64/arm64 预编译包;使用预编译包无需 Go 工具链,从源码构建则需要 Go。需要在 GITHUB_TOKEN 中提供 GitHub 个人访问令牌,并按用途授予 repo 或 public_repo 以及 read:org 权限。GITHUB_API_URL 可指向 GitHub Enterprise Server 的 API,使用 github.com 时留空。需要访问 GitHub 的网络连接。
安装前请注意
该令牌对仓库拥有真实写权限,应尽量缩小权限范围,并只保存在本地配置中。多个工具会写入或修改数据:创建仓库、提交文件、创建和更新议题、发表评论、创建拉取请求,以及被标记为破坏性的合并拉取请求。合并与提交会直接作用于线上仓库,且不易撤销。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Github Mcp Connector,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

🔌 github-mcp-connector

Talk to GitHub from an MCP-speaking agent.

[CI] [CodeQL] [Latest release] [MCP Registry] [Go Reference] [License: MIT] [MCP] [Conventional Commits] [PRs Welcome]


A single static Go binary that speaks the Model Context Protocol and exposes 18 tools for working with GitHub: repositories, branches, commits, file contents, issues, pull requests, and search.

No Python, no uv, no runtime dependency to install — just a binary and an .mcp.json.

✨ Why this exists

An agent that can only talk about your GitHub repos isn't that useful. This gives it hands: it can read and write files in a repo, open and triage issues, push a branch and open a PR, and merge it — all against the real GitHub API, with the same guardrails (size caps, friendly errors, destructive-action annotations) as the sibling connectors.

🧰 Tools

ToolWhat it doesWrite?
github_whoamiGet the user authenticated by GITHUB_TOKEN
github_list_reposList repos for a user/org, or the authenticated user
github_get_repoGet one repository's details
github_create_repoCreate a new repository✍️
github_list_branchesList branches in a repository
github_list_commitsList commits, optionally filtered by branch/path
github_get_file_contentsRead a file's content, or list a directory
github_create_or_update_fileCreate/update a file via a commit (≤ 5 MB)✍️
github_list_issuesList issues in a repository
github_get_issueGet one issue's full details
github_create_issueCreate a new issue✍️
github_update_issueUpdate an issue's title/body/state/labels✍️
github_add_issue_commentComment on an issue or PR✍️
github_list_pull_requestsList pull requests
github_get_pull_requestGet one PR's full details, incl. diff stats
github_create_pull_requestOpen a pull request✍️
github_merge_pull_requestMerge a pull request🗑️ destructive
github_search_repositoriesSearch repositories with GitHub search qualifiers

Every tool accepts an optional response_format: markdown (default, pretty tables for a chat UI) or json (for programmatic use).

🚀 Quickstart

Fastest path: grab a prebuilt bundle from the latest release — download github-mcp-connector-plugin-<version>-<os>-<arch>.zip, unzip it, and point Cowork/Claude at the plugin/ folder inside (see step 4 of SETUP.md). No Go toolchain required.

From source:

bash
# 1. Buildcd go-servergo mod tidygo build -o github-connector-server .cp github-connector-server ../plugin/servers/go/
# 2. Set up auth — a personal access token, see SETUP.mdexport GITHUB_TOKEN=ghp_...
# 3. Run./go-server/github-connector-server   # serves MCP over stdio

Or make build — see the Makefile for every shortcut (test, vet, fmt, lint, tidy).

Full walkthrough — including wiring this up as a Claude/Cowork plugin — is in SETUP.md.

🔐 Configuration

Everything is environment variables, passed through by the plugin's .mcp.json:

VariablePurposeDefault
GITHUB_TOKENPersonal access token (classic or fine-grained). Needs repo/public_repo and read:org scopes depending on what you use it for.— (required)
GITHUB_API_URLGitHub Enterprise Server API base URL, e.g. https://github.example.com/api/v3.(unset — github.com)

🧪 Quality bar

This isn't a toy script — it's got the same checks you'd expect from a production Go service:

  • ✅ Unit tests for every input-validation path (go test ./...)
  • ✅ go vet + gofmt clean
  • ✅ golangci-lint (govet, staticcheck, errcheck, gosec, and more)
  • ✅ govulncheck — no known vulnerabilities in the dependency graph
  • ✅ CodeQL static security analysis on every push
  • ✅ End-to-end verified — every tool (repos, branches, commits, file read/write, issues, comments, PRs, merge, search) was exercised against a real, dedicated GitHub sandbox repo, not mocks
  • ✅ Dependabot keeps Go modules and Actions current

All of it runs in CI on every push and PR.

🏷️ Releases & versioning

Versions follow semver and are cut automatically by release-please from Conventional Commits on main:

  • fix: ... → patch (v0.1.0 → v0.1.1)
  • feat: ... → minor (v0.1.1 → v0.2.0)
  • feat!: ... / BREAKING CHANGE: footer → major (v0.2.0 → v1.0.0)

Every merged PR updates a standing "chore(main): release vX.Y.Z" PR with an auto-generated CHANGELOG.md. Merging that PR:

  1. tags the release and publishes it on GitHub
  2. builds and attaches zipped, ready-to-install plugin bundles for linux/darwin/windows × amd64/arm64
  3. regenerates server.json from those exact assets (fresh version + SHA-256 hashes) and publishes it to the official MCP Registry via mcp-publisher, authenticated with GitHub OIDC — no stored secrets

See .github/workflows/release-please.yml and .github/workflows/publish-mcp-registry.yml (also runnable by hand for an existing tag via workflow_dispatch).

📁 Layout

github-mcp-connector/├── README.md                  ← you are here├── SETUP.md                   ← step-by-step setup guide├── CONTRIBUTING.md             ← how to contribute├── CODE_OF_CONDUCT.md├── SECURITY.md                 ← vulnerability reporting├── CODEOWNERS├── LICENSE                     ← MIT├── Makefile                    ← build / test / lint shortcuts├── .golangci.yml                ← lint rules├── release-please-config.json  ← semver/changelog automation config├── .release-please-manifest.json├── server.json                  ← MCP Registry manifest (regenerated fresh per release by CI)├── scripts/│   └── render-server-json.sh    ← rebuilds server.json from a release's zip assets├── .github/│   ├── workflows/│   │   ├── ci.yml                     ← build, vet, test, lint, govulncheck│   │   ├── codeql.yml                 ← security scanning│   │   ├── pr-title.yml               ← Conventional Commits PR title check│   │   ├── release-please.yml         ← version PRs, tagging, GitHub releases│   │   ├── publish-mcp-registry.yml   ← publishes server.json to the MCP Registry│   │   └── rebuild-release-assets.yml ← manual re-attach fallback│   ├── ISSUE_TEMPLATE/│   ├── PULL_REQUEST_TEMPLATE.md│   └── dependabot.yml├── go-server/                  ← the MCP server source│   ├── main.go│   ├── main_test.go│   ├── go.mod / go.sum│   └── README.md└── plugin/                     ← installable Cowork/Claude plugin    ├── .claude-plugin/plugin.json    ├── .mcp.json                ← holds credentials locally — never commit real ones    └── servers/go/              ← compiled binary goes here

🤝 Contributing

PRs and issues are very welcome — see CONTRIBUTING.md for the full guide (setup, coding conventions, how to add a new tool) and the Code of Conduct.

main is protected: every change, including the maintainer's, lands via pull request with CI green. PR titles must follow Conventional Commits — that's what drives the automatic versioning above.

Found a security issue? Please follow SECURITY.md instead of opening a public issue.

📄 License

MIT © FerhatDundar

来源:README.md,提交 efbca9a

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v0.1.1最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分