Version Control MCP servers

Git hosts, reviews and pull requests.

Version control MCP servers connect an assistant to your repositories: the code, the history, the issues, the pull requests. They split into two shapes, and the difference matters more than it first appears.

Local servers operate on a checkout on your machine through git itself. They can read history, diff branches, stage and commit — no network, no token, no hosted service involved.

Hosted servers talk to the platform's API instead. That is where issues, reviews, pull requests and organisation-wide code search live. They need a token, and the scope of that token is the whole of their permission model.

Version Control MCP servers in this directory

What people build with version control MCP servers

Reviewing a pull request properly

The agent reads the diff, the linked issue and the surrounding code, then comments on what the change actually does rather than on the patch in isolation.

Explaining why code is the way it is

History answers questions the current file cannot. Ask why a workaround exists and get the commit, the message and the issue that produced it.

Triage across an organisation

Search issues across every repository for the same failure and find the three teams that have each fixed it separately.

Opening the follow-up change

When the fix is agreed, the agent branches, commits and opens the pull request in the same session.

Choosing a version control MCP server

  • Pick local if the work is on code you have checked out. It is faster, needs no credentials, and cannot touch anything on the server.
  • Pick hosted if the work involves issues, reviews or repositories you have not cloned.
  • Scope the token to specific repositories. A fine-grained token limited to the two repositories you are working in is a much smaller problem if it leaks than an organisation-wide one.
  • Use a read-only token until you actually want the agent writing. Reviewing and explaining need nothing more.

Before you connect one

The token is the whole security boundary. Grant the narrowest scope that works, prefer fine-grained tokens where the platform offers them, keep the token in your client config rather than in a repository, and rotate it if it has ever been in a chat window.

Frequently asked questions

Can the agent push to main?

Only if the token allows it and no branch protection stops it. Branch protection is the reliable control here — it applies to the agent for exactly the same reason it applies to you.

Does a version control MCP server work with private repositories?

Yes. It sees precisely what the token sees, so a token with access to your private repositories gives the agent access to them too.

Do I need a local clone?

For a local git server, yes — it operates on a working copy. Hosted servers work entirely through the platform's API and need nothing checked out.

Will it commit without asking?

That depends on your client, not the server. Most MCP clients confirm before running a tool that writes; check that setting is on before you connect a write-capable token.

Install any of these

Every server on this page carries a one-line install command on its own listing. Paste it into your client config and restart — the version control tools appear in your next session.

Or keep browsing: all MCP server categories · the full MCP server list · Agent Skills.