GitHub
OfficialGitHub · Dev Tools
61.7k installs
The official GitHub MCP gateway. Your agents can open branches, review pull requests, triage issues, and trigger workflows. Combined with the Universal CLI Proxy, local Claude Code sessions share the same auth as your cloud threads.
Just say it in a thread
No configs, no docs. Once connected, these are the kinds of messages your agents act on.
"List all open issues labeled 'bug' across our repos and rank them by age."
"Open a pull request from the fix/checkout-timeout branch with a clear summary of the change for review."
"Create a branch called feature/pricing-page off main."
"Which issues have been open longer than 30 days with no assignee?"
"Trigger the deploy workflow on main and confirm once it has been dispatched."
"Show me every issue mentioning 'login' opened in the last two weeks."
"How many issues did we close this month compared to last month?"
"Create a release branch release/v2.4 from main and kick off the CI workflow on it."
"Triage today's new issues: group them by label and flag anything that looks like a production incident."
"Open a PR that describes the hotfix and references the related issue number."
Agent-callable tools
github.create_branch
Create a branch from any ref
github.open_pr
Open a pull request with a description
github.list_issues
Query issues across repos
github.trigger_workflow
Dispatch an Actions workflow
Your data stays yours
Credentials live in your vault. We route requests — we never store, log, or train on your data.
Works with every AI
Connect once — portable across Claude, GPT, Gemini, and every local agent you run.
Pairs well with
Best Dev Tools MCP servers
Vercel
Vercel
Deployments, preview URLs, env vars, and logs as agent-callable tools.
Filesystem
anthropic
Secure file operations with configurable access controls. Read, write, move, and search files with directory restrictions.
Fetch
anthropic
Web content fetching with robots.txt compliance. Retrieve and convert web pages to markdown for AI consumption.
Frequently asked questions
Why can't the agent see my private repository?
Access is scoped by the GitHub App installation. The app must be installed on that specific repository (or the whole org), and for organization-owned repos an org owner may need to approve the installation. If a repo was added after connecting, re-run the installation flow and select it explicitly.
Can the agent push directly to main?
No. Writes go through branches and pull requests: the agent creates a branch, commits there, and opens a PR that you review and merge. Your branch-protection rules remain the final gate, exactly as they are for human contributors.
Why did triggering a workflow fail?
The most common causes: the workflow YAML has no workflow_dispatch trigger (it must be declared before it can be dispatched), the workflow file does not exist on the ref you targeted, or the installation lacks the Actions write permission. Check the workflow file on the branch you are dispatching against first.
What permissions should I grant?
Follow least privilege: install the app only on the repositories agents actually need, with contents, pull-request, issues, and Actions scopes. You can widen access later without reconnecting anything else.
Does this work for issue triage across multiple repositories?
Yes — the issue query tool spans every repo the installation covers, so one prompt can sweep bugs, stale issues, or unassigned work across your whole org.
Keep exploring
Give your AI team the GitHub skill
Free forever plan, no credit card. Connected and working in under five minutes.
Connect GitHub free