Github Mcp Server
Let coding agents drive GitHub—repos, issues, PRs, and more—with a token-efficient MCP surface instead of bloated API dumps.
Overview
github-mcp-server is an MCP server for the Build phase that exposes a large, token-efficient GitHub toolset for coding agents.
What is this MCP server?
- Advertises 112 GitHub-oriented MCP tools in one server
- Claims ~98% token reduction via AI-optimized compact responses
- stdio PyPI package github-mcp-server v2.5.7
- Maintained fork lineage from crypto-ninja/mcp-server-for-Github for agent-centric workflows
- 112 tools advertised in server description
- 98% token reduction claimed for compact responses
- Package version 2.5.7, PyPI identifier github-mcp-server
Community signal: 4 GitHub stars.
What problem does it solve?
Standard GitHub API results flood agent context, so everyday repo tasks become slow, expensive, or truncated mid-session.
Who is it for?
Solo builders who delegate GitHub housekeeping and repo research to agents several times per week.
Skip if: Teams that forbid PAT-based GitHub access in local agents or only need rare read-only git clone workflows.
What do I get? / Deliverables
You register github-mcp-server so agents use compact GitHub tools for issues, PRs, and repo work with far smaller responses.
- Agent-accessible GitHub MCP tool surface (112 tools per project description)
- Compact API-shaped responses intended for lower token use during agent sessions
Recommended MCP Servers
Journey fit
GitHub is the default hub while building and integrating automation; this server keeps agent context on the repo layer during active development. Integrations subphase is for wiring external developer platforms into the agent loop via MCP.
How it compares
High-surface GitHub MCP integration, not the official minimal GitHub MCP sample or a code-review-only skill.
Common Questions / FAQ
Who is github-mcp-server for?
Indie developers using AI coding agents who want many GitHub operations in one MCP server with responses tuned for LLM context limits.
When should I use github-mcp-server?
Use it during build and integration work whenever agents must list repos, manage issues, or inspect pull requests without hand-rolling API calls.
How do I add github-mcp-server to my agent?
Install github-mcp-server from PyPI, add a stdio MCP entry in your client, and configure a GitHub token with scopes required by the tools you plan to call.