MCP.Market

Self-hosted GitHub MCP server

by adelaidasofia·io.github.adelaidasofia/github-mcp·v0.1.0

Self-hosted GitHub MCP server. PAT auth, stdio transport, transport-agnostic so it works with…

B73/100grade B
What users say
No reviews yet
Be the first
Safety scan
B73/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Self-hosted GitHub MCP server yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Self-hosted GitHub MCP server tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • –Code scanpackage could not be scannedn/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 4 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 73/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Self-hosted GitHub MCP server compares

Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
73/100
higher than 35% of 1,119 Developer tools servers

Install Self-hosted GitHub MCP server in Claude Code, Cursor or VS Code

The registry entry has no remote endpoint or installable package.

What the publisher says

From the Self-hosted GitHub MCP server repository's README, as published. We do not edit it. Read it on GitHub

github-mcp

<!-- mycelium-badges:start -->

<!-- mycelium-badges:end -->

Self-hosted GitHub MCP server. Personal-access-token auth, stdio transport, transport-agnostic so it works with Claude Code (any account), Codex CLI, Cursor, or any MCP-compliant client. No claude.ai OAuth dependency.

Written in Python on top of FastMCP. Slots into the same install pattern as other community Python MCP servers.

Why this exists

The official github/github-mcp-server (Go, 60+ tools) is excellent if you want a kitchen-sink server tied to a single agent platform's auth flow. This one is scoped for operators who:

  • Switch between multiple Claude accounts, Codex CLI, Cursor, or other MCP clients and want the same GitHub auth across all of them.
  • Prefer a small, audited tool surface scoped to PR + repo file + Dependabot operations.
  • Want a Python install that lives alongside their other MCP servers.

If neither applies, run github/github-mcp-server instead — that's the right call.

Tool surface (v0.1.0)

Future versions expand: workflows, releases, issues, rulesets, secret-scan alerts, branch protection, repo settings.

Secret hygiene (read this first)

v0.1.1+ reads the PAT from macOS Keychain by default. Env-var fallback is still supported for non-macOS / CI, but the Keychain path is the recommended setup because the secret never enters argv or process env — safe from ps aux, pgrep -fl, lsof, /proc//environ, panic dumps, CI logs, debuggers, or any LLM agent running an introspection command.

# One-time setup (macOS):
security add-generic-password -s github-mcp -a "$USER" -w "<your-fine-grained-PAT>"

# Update later (e.g. after rotation):
security delete-generic-password -s github-mcp -a "$USER" 2>/dev/null
security add-generic-password -s github-mcp -a "$USER" -w "<new-PAT>"

Do NOT install with an inline --env:

# BAD — bakes the PAT into ~/.claude.json + every Claude child spawn's --mcp-config argv.
# Any pgrep / ps aux dumps it.
claude mcp add github --scope user --env GITHUB_TOKEN=github_pat_... -- <command>

# GOOD — no --env block. The server reads from Keychain at call time.
claude mcp add github --scope user -- <command>

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Self-hosted GitHub MCP server: common questions

Is Self-hosted GitHub MCP server safe?
Mostly: it is graded B (73/100). Read the Self-hosted GitHub MCP server safety report
Does Self-hosted GitHub MCP server need an API key?
Yes. The registry entry asks for GITHUB_TOKEN.
Is Self-hosted GitHub MCP server maintained?
The last commit was 40 days ago (2026-09-23). The latest release is v0.1.0.
What can I use instead of Self-hosted GitHub MCP server?
Servers from other publishers that do the same job: Nora MCP server, Folio MCP server and HomeLab Monitor MCP server.

Alternatives to Self-hosted GitHub MCP server

Same job from other publishers: the closest match first, then the best rated.

  • Nora
    Operate self-hosted OpenClaw and Hermes agent fleets on Docker or Kubernetes from MCP clients.
    B
  • Folio
    Self-hosted Git-backed team wiki: search, read and edit pages, data tables and whiteboards.
    A
  • HomeLab Monitor
    Self-hosted homelab dashboard with a built-in read-only MCP server (hosts, Docker, GPU, services).
    A
  • clawops
    Deploy self-hosted OpenClaw to AWS, GCP, Azure or a local VM — a CLI and an MCP server in one.
    C
  • GitDiagram
    Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
    A

More from adelaidasofia →