Best Version Control MCP Servers for VS Code

Top 5 of 5 Version Control MCP servers that work with VS Code, ranked by security score — every entry below is human-reviewed, not just scraped. Every row has a one-click config for VS Code — no need to open each page.

Setting up MCP servers in VS Code

VS Code's MCP support is native (via GitHub Copilot's agent mode), configured in .vscode/mcp.json per workspace or through the "MCP: Open User Configuration" command for a config that applies everywhere. One thing that trips people up moving a config from Claude Desktop or Cursor: VS Code's top-level key is "servers", not "mcpServers" — the two aren't interchangeable.

Because .vscode/mcp.json is a normal workspace file, it can be committed alongside project code the same way project-scoped Cursor configs can — a team opening the repo in VS Code gets the same MCP servers without extra setup.

#ServerSecurity scoreStarsLanguageConfig
1

GitLab API access via 86 specialized tools for AI model context integration.

6861TypeScript
2

Bitbucket repositories, pull requests, and code management via AI agents.

36159TypeScript
3

Forgejo and Gitea repository management for AI through 103 integrated tools.

308TypeScript
4

Gitea repositories managed directly through custom file upload and sync tools.

2413TypeScript
5

GitLab API access for project management, file operations, and repository automation.

16293JavaScript

Version Control + VS Code: frequently asked questions

How do I add a Version Control MCP server to VS Code?

Add an entry under "servers" in .vscode/mcp.json in your workspace, or run "MCP: Open User Configuration" from the command palette for a global config.

Are Version Control MCP servers safe to use with VS Code?

Check the security score on each server's page before installing — it's computed from real signals (permissions requested, authentication, maintenance activity), not a marketing claim. Every server ranked below has been human-reviewed, not just scraped.

Why does VS Code use "servers" instead of "mcpServers"?

It's simply VS Code's own schema — Claude Desktop, Cursor, and Windsurf all use "mcpServers", but a config copied between them and VS Code needs that one key renamed.

Can I use a global MCP config in VS Code instead of per-workspace?

Yes — run "MCP: Open User Configuration" from the command palette to edit a config that applies across all your workspaces.