Version Control
MCPs for GitHub, GitLab, and Git workflows
TL;DR
Version control MCP servers expose Git hosting APIs (GitHub, GitLab) to agents — branches, PRs, issues, reviews, merges. Claude Code, Cursor, and every AI coding tool relies on these. Pair with file-ops for full dev-loop automation.
About Version Control
Version control MCPs connect agents to GitHub, GitLab, Bitbucket, and Gitea. Agents can read code, create branches, open PRs, review diffs, merge changes, and manage issues — the foundation of every coding agent.
Common use cases
- Let Claude Code open a PR with a full commit message and description
- Auto-generate changelogs from merged PRs
- Triage new issues: label, assign, and post summary in Slack
- Review PRs: comment on risky diffs, approve safe ones
- Sync Linear issues to GitHub branches and back
Related recipes
Auto DB Migrations on Push
Every push to main triggers a Supabase migration automatically. Schema diffs are committed and applied with zero manual steps.
Preview Deploy on Every PR
Open a PR and a Vercel preview URL appears as a comment within minutes. Branches are cleaned up automatically when PRs close.
Issue → Branch → PR Pipeline
A Linear issue assigned to a developer automatically creates a git branch, syncs status changes, and opens a draft PR.
Full CI Pipeline with Slack Alerts
Tests run on every push. Failures post a Slack message with the failing test name, screenshot, and a link to the run.
Code Quality Gates
SonarQube analyzes every PR for code smells, coverage drops, and security hotspots. PRs below the quality gate are blocked.
Related tags
Frequently asked questions
Can agents merge PRs?
Yes, but respect branch protection rules. Most teams require human approval + passing CI before merge — the MCP honors both.
What's the difference between GitHub MCP and just using `gh` CLI?
The MCP exposes GitHub as structured tools with schemas, so the LLM knows exactly what args to pass. `gh` is a CLI — the MCP wraps that into typed tool calls.
Does GitLab have feature parity with GitHub MCP?
Yes for core workflows (branches, PRs, issues). Some advanced features (GitHub Actions ≠ GitLab CI) are vendor-specific.
Can I restrict agent write access?
Yes — use a fine-grained GitHub token scoped to specific repos and permissions (no admin, no org-wide).
Install Version Control MCPs
Browse the full directory or explore all tags to find the right MCPs for your stack.