GitHub MCP Server
MCP server entry for GitHub repository, issue, pull request, and coding workflow context.
Host support
Source boundary
GitHub documentation describes MCP as a way to provide external context to Copilot and related coding workflows.
Sources
| Source | Type | Verified | Citation |
|---|---|---|---|
| GitHub Copilot MCP docs | docs | 2026-09-15 | Official GitHub documentation for MCP context concepts. |
| GitHub MCP Server repository | github | 2026-09-15 | Public repository for GitHub's MCP server implementation. |
Relationships
| Type | Source | Target | Citation |
|---|---|---|---|
| works_with | codex | github-mcp-server | This planning edge requires current host and MCP server configuration verification before production use. |
| works_with | cursor | github-mcp-server | Cursor documentation includes MCP configuration surfaces for coding workflows. |
| exposes | github-mcp-server | browser-tool | Initial graph edge groups GitHub MCP as a tool-capable server entry. |
| works_with | github-mcp-server | github-copilot | GitHub Copilot MCP documentation describes MCP context integration. |
Compatibility
| Type | Target | Status | Evidence |
|---|---|---|---|
| framework_mcp | github-mcp-server | verify_required | CrewAI tool workflows can be evaluated with MCP server access, but GitHub MCP transport, auth, and tool permission boundaries must be verified. |
| server_host | codex | verify_required | GitHub MCP Server can be considered for coding-agent host workflows, but local host configuration, authentication, and transport support must be verified. |
| server_host | cursor | verify_required | Cursor supports MCP configuration surfaces, but GitHub MCP server auth, transport, and permission scope must be verified in the target workspace. |
| server_host | github-copilot | supported | GitHub Copilot documentation describes MCP context support and GitHub MCP workflows. |
| framework_mcp | github-mcp-server | verify_required | Agent Framework can orchestrate tool-using agents, while GitHub MCP Server exposes repository tools through MCP; integration should be verified per host and transport. |
| framework_mcp | github-mcp-server | verify_required | Both entries participate in agent tool orchestration, but a production integration should verify transport, auth, and runtime assumptions. |
What should a coding-agent MCP server selection check first?
Check host support, transport, authentication, repository permission scope, destructive tool behavior, and whether human review is required before file or repository mutations.
Why should MCP server pages include permission risk?
MCP servers can expose tools that read, write, delete, send messages, or call external services. Risk labels help developers and agents decide where human review is required.
Should debugging agents start from Sentry MCP Server or GitHub MCP Server?
Start from Sentry MCP Server when the task begins with runtime errors or incidents. Start from GitHub MCP Server when repository, issue, pull request, or code review context is the primary source of truth.