Git Vertex — local MCP server exposing your Git repositories to AI agents (Claude Code, Cursor, Copilot…). Read-mostly (writes limited to conflict
Connect Git to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Git Vertex — local MCP server exposing your Git repositories to AI agents (Claude Code, Cursor, Copilot…). Read-mostly (writes limited to conflict resolution, disable with --read-only), no cloud. The git mcp server is what makes that connection.
Visualize branches, stage changes, and manage commits with a clean interface.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Tags — create and visualize tags directly in the graphnpm on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
git 2.40 or newer is recommended (2.28 is the hard minimum). Everything works from 2.28 on, with one exception: predicting conflicts before a merge, rebase, cherry-pick or revert uses git merge-tree --merge-base=…, which landed in git 2.40. On an older git that prediction is simply unavailable — the operation still runs, it just runs without the warning, and the app tells you so once at
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Git's toolset — Tags — is a fair guide to whether it matches your workflow. It is maintained by victorquilgars; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Tags | create and visualize tags directly in the graph |
{
"mcpServers": {
"vertex": {
"command": "npx",
"args": ["-y", "npm"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
git 2.40 or newer is recommended (2.28 is the hard minimum). Everything works from 2.28 on, with one exception: predicting conflicts before a merge, rebase, cherry-pick or revert uses git merge-tree --merge-base=…, which landed in git 2.40. On an older git that prediction is simply unavailable — the operation still runs, it just runs without the warning, and the app tells you so once at
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.