GitHub
Let your coding agent create issues, open PRs, inspect workflows, and manage repositories on GitHub without leaving the chat.
Overview
GitHub MCP Server is a MCP server for the Build phase that connects AI assistants to GitHub so they can manage repositories, issues, pull requests, and workflows through natural language.
What is this MCP server?
- Remote streamable-http endpoint at api.githubcopilot.com/mcp with Bearer PAT or app token
- Stdio package ghcr.io/github/github-mcp-server:1.2.0 with GITHUB_PERSONAL_ACCESS_TOKEN
- Natural-language control of repos, issues, PRs, and GitHub workflows
- Official GitHub-maintained MCP server (version 1.2.0 in server schema)
- Works with Claude Code, Cursor, and other MCP-capable agents
- Server schema version 1.2.0
- One remote: streamable-http at https://api.githubcopilot.com/mcp/
- One OCI stdio package: ghcr.io/github/github-mcp-server:1.2.0
Community signal: 30.5k GitHub stars.
What problem does it solve?
You keep pasting GitHub URLs and manually clicking through issues and PRs while your agent could act on the repo if it had authenticated API access.
Who is it for?
Solo builders using Claude Code or Cursor who want the agent to operate their GitHub repos, issues, and CI workflows during active development.
Skip if: Teams that forbid agents from holding production GitHub tokens, or builders who only need read-only browsing without MCP setup.
What do I get? / Deliverables
After you register the server with a PAT or app token, your agent can list, create, and update GitHub resources in-thread, cutting context switches during implementation and release prep.
- Agent-callable tools for GitHub repos, issues, PRs, and workflow operations
- Authenticated remote or local stdio MCP connection documented in server.json
- Reduced manual GitHub UI context switching during agent-assisted coding
Recommended MCP Servers
Journey fit
GitHub is where solo builders store code and run CI; wiring the agent to GitHub belongs on the Build shelf under integrations because that is when you need repo and PR actions most often. Issues, pull requests, and Actions are third-party platform hooks—not frontend UI or deploy knobs—so integrations is the correct subphase.
How it compares
Official GitHub API MCP integration, not a code-review methodology skill or a hosted marketplace of prompts.
Common Questions / FAQ
Who is GitHub MCP Server for?
It is for indie developers and small teams who ship on GitHub and want their MCP-enabled coding agent to manage repos, issues, PRs, and workflows conversationally.
When should I use GitHub MCP Server?
Use it during Build and Ship when you are implementing features, filing bugs, updating PRs, or checking Actions status and want the agent to call GitHub directly.
How do I add GitHub MCP Server to my agent?
Add either the remote URL https://api.githubcopilot.com/mcp/ with an Authorization token header, or run the OCI stdio package ghcr.io/github/github-mcp-server:1.2.0 with GITHUB_PERSONAL_ACCESS_TOKEN set in your MCP client config.