Self Hosted GitHub MCP Server
Let your agent manage GitHub repos, issues, and workflows via a self-hosted MCP server using a personal access token.
Overview
GitHub MCP is a MCP server for the Build phase that connects MCP hosts to GitHub using PAT auth and stdio transport for repo and workflow actions.
What is this MCP server?
- Self-hosted GitHub MCP with PAT authentication
- stdio transport designed to work across MCP-capable hosts
- mcpb release v0.1.0 from GitHub releases
- GITHUB_TOKEN requires repo and workflow scopes
- Transport-agnostic FastMCP-style hosting from adelaidasofia/github-mcp
- Server version 0.1.0 mcpb stdio
- Required env GITHUB_TOKEN (secret)
- Repository github.com/adelaidasofia/github-mcp
What problem does it solve?
Jumping between your agent session and GitHub UI slows issue triage, PR checks, and workflow tweaks on a solo shipping cadence.
Who is it for?
Developers who self-host MCP and want a PAT-driven GitHub bridge compatible with multiple agents.
Skip if: Orgs that mandate GitHub Apps only, forbid PATs on laptops, or need full GitHub Enterprise policy guardrails out of the box.
What do I get? / Deliverables
After configuring GITHUB_TOKEN, your agent can perform GitHub API operations as MCP tools alongside your codebase.
- Agent-callable GitHub repository and workflow operations via MCP tools
- Reduced context switching between coding sessions and GitHub.com
Recommended MCP Servers
Journey fit
GitHub is the default integration surface while building, but the same MCP connection supports ship reviews and operate iteration. This server is explicit GitHub API wiring—repos and automation—not generic backend code generation.
How it compares
Self-hosted GitHub PAT MCP server, not the git commit skill inside your repo or GitHub’s cloud-only catalog entry.
Common Questions / FAQ
Who is GitHub MCP for?
Solo developers using self-hosted MCP who want GitHub repo and workflow access via a personal access token.
When should I use GitHub MCP?
Use it while building, shipping, or iterating whenever agent-driven GitHub reads and writes beat manual dashboard hops.
How do I add GitHub MCP to my agent?
Create a classic or fine-grained PAT with repo and workflow scopes, set GITHUB_TOKEN, install github-mcp mcpb v0.1.0, and register the stdio server.