[ MCP SERVER SUMMARY ]
GitHub MCP server summary
GitHub’s official MCP server exposes repository, issue, and pull request operations to AI assistants. Running it through Bifrost lets you centralize credentials, scope tool access per team or virtual key, and audit every GitHub tool call alongside your LLM traffic.
| Property | Details |
|---|---|
| Company | GitHub |
| Connection type | STDIO |
| Authentication | GitHub personal access token |
| Package or endpoint | ghcr.io/github/github-mcp-server |
| Capabilities | Repository search, Issues and pull requests, GitHub Actions workflows |
| Official documentation | GitHub MCP documentation |
Before you start
- Docker or the GitHub MCP binary
- A GitHub personal access token
What you can do with GitHub
- Let coding agents open issues, review PRs, and search repos without distributing PATs to every client
- Apply RBAC so only approved teams can invoke destructive GitHub tools
- Track per-tool latency and cost when agents combine GitHub calls with LLM requests
[ HOW TO CONNECT ]
Connect GitHub to Bifrost in three steps
Install Bifrost
Start the gateway locally or deploy in your VPC.
npx -y @maximhq/bifrost
Add GitHub in MCP Gateway
Open MCP Gateway in the Bifrost dashboard, click New MCP Server, and choose STDIO. Or register via the API below.
• Set Auth Type to none for STDIO — credentials pass via environment variables on the spawned process.
• Use tools_to_execute to limit which GitHub tools each virtual key may call.
Point clients at Bifrost /mcp
Configure Claude Desktop, Cursor, or Claude Code to use your Bifrost endpoint with a virtual key instead of connecting directly to GitHub.
{
"mcpServers": {
"bifrost": {
"url": "http://localhost:8080/mcp",
"headers": {
"Authorization": "Bearer vk_your_virtual_key"
}
}
}
}[ EXAMPLE CONFIG ]
Register GitHub via API
Add this MCP client with a POST to /api/mcp/client. See Connecting to MCP Servers for full options.
curl -X POST http://localhost:8080/api/mcp/client \
-H "Content-Type: application/json" \
-d '{
"name": "github",
"connection_type": "stdio",
"stdio_config": {
"command": "docker",
"args": [
"run", "-i", "--rm",
"-e", "GITHUB_PERSONAL_ACCESS_TOKEN",
"ghcr.io/github/github-mcp-server"
],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "env.GITHUB_PERSONAL_ACCESS_TOKEN"
}
},
"tools_to_execute": ["*"]
}'[ WHY BIFROST ]
Run GitHub through one governed gateway
Access control
Virtual keys, RBAC, and tool allowlists per team or agent.
Cost governance
Attribute MCP tool spend alongside LLM usage in one view.
Observability
Log every tool call with latency, server, and virtual key metadata.
Credential isolation
Upstream secrets stay in the gateway — not on every laptop.
[ FAQ ]
Common questions
Does Bifrost replace the GitHub MCP server?
No. Bifrost connects to the official GitHub MCP server as an upstream client. Your agents connect to Bifrost, which forwards allowed tool calls to GitHub with governance and logging in between.
How do I pass my GitHub token securely?
Store GITHUB_PERSONAL_ACCESS_TOKEN in your Bifrost environment or secret store and reference it with env.GITHUB_PERSONAL_ACCESS_TOKEN in stdio_config. Tokens never leave your gateway perimeter.
Can Claude Desktop use GitHub tools through Bifrost?
Yes. Point Claude Desktop or Cursor at your Bifrost /mcp endpoint with a virtual key. Bifrost exposes the GitHub tools your key is allowed to call.
What connection type should I use for GitHub MCP?
Use STDIO when running the official GitHub MCP container or binary locally. Bifrost spawns the process and pipes MCP messages over stdin/stdout.
[ RELATED SERVERS ]
More MCP integrations
GitLab
GitLab's official MCP server enabling AI tools to securely access GitLab project data, manage issues, and perform repository operations via OAuth 2.0.
Sentry
Use Sentry’s MCP server to investigate errors, issues, traces, and application health from AI coding assistants.
DeployHQ
Manage and inspect software deployments through DeployHQ’s MCP server.