Github Mcp Connector

io.github.FerhatDundarPublished by GitHub account FerhatDundarv0.1.1Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

A local Go-based MCP server that gives an assistant 18 tools to read and write GitHub repositories, files, issues, pull requests and search.

What you can do
Identify the authenticated GitHub user and list or inspect repositories, branches and commits, including creating repositories and searching with GitHub qualifiers. Read file contents or list directories, and create or update files through commits up to 5 MB. List, read, create and update issues, and add comments to issues or pull requests. List and inspect pull requests, open new ones, and merge them. Choose markdown or JSON output per call.
When to use it
Useful when an assistant should work directly against real GitHub repositories: reviewing code and history, filing or triaging issues, committing file changes, and opening or merging pull requests without leaving the chat.
Requirements
Runs as a local process over stdio, distributed as prebuilt bundles for macOS, Linux and Windows on amd64/arm64; no Go toolchain needed for the bundles, though building from source needs Go. Requires a GitHub personal access token in GITHUB_TOKEN with repo or public_repo and read:org scopes as needed. GITHUB_API_URL can point at a GitHub Enterprise Server API; leave it unset for github.com. Network access to GitHub is required.
Before you install
The token grants real write access to your repositories; scope it narrowly and store it only in local configuration. Several tools write or change data: creating repositories, committing files, creating and updating issues, commenting, opening pull requests, and merging pull requests, which is marked destructive. Merges and commits act on live repositories and are not easily undone.

Installation

In SourceWeft

  1. Open Github Mcp Connector in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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

Source: README.md at commit efbca9a

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts