Best Version Control MCP Servers for VS Code
Top 9 of 9 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.
| # | Server | Security score | Stars | Language | Config |
|---|---|---|---|---|---|
| 1 | Configure environment variables directly for seamless PAT or OAuth authentication. | 73 | 1,970 | TypeScript | |
| 2 | Use a TypeScript-based bridge to fetch activity and project data. | 73 | 64 | TypeScript | |
| 3 | GitLab MCP ServerOfficial GitLab API access for project management, file operations, and repository automation. | 16 | 296 | JavaScript | |
| 4 | Kibana instance data access for MCP clients via API-based integrations. | 15 | 80 | TypeScript | |
| 5 | Operates as an MCP server to provide context from remote Forgejo instances. | 10 | 10 | TypeScript | |
| 6 | Bitbucket repositories, pull requests, and code management via AI agents. | 6 | 162 | TypeScript | |
| 7 | Leverage TypeScript-based integration to modify existing files in your self-hosted Gitea environment. | 0 | 14 | TypeScript | |
| 8 | Repository operations like status, diffs, and commits for MCP-compatible clients. | 0 | 2 | JavaScript | |
| 9 | Azure DevOps task, pull request, and wiki management for AI coding assistants. | 0 | 2 | TypeScript |
Version Control + VS Code: frequently asked questions
›What's the best Version Control MCP server for VS Code?
GitLab MCP Server currently ranks highest among Version Control MCP servers, with a security score of 73/100. GitLab MCP Server (73/100) is the next best option. Every server below has a one-click VS Code config.
›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. The same steps apply to GitLab MCP Server, the top-ranked Version Control server below.
›Are Version Control MCP servers safe to use with VS Code?
1 of the 9 Version Control MCP servers below is officially maintained by its vendor; the rest are independently reviewed. Every score comes from real signals — permissions requested, authentication, maintenance activity — not a marketing claim. All of them are compatible with VS Code.
›How many Version Control MCP servers work with VS Code?
9 Version Control MCP servers have a ready-to-use VS Code config right now, ranked by security score below.
›Where do I put the Version Control MCP server config for VS Code?
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. A Version Control server goes in the exact same place as any other VS Code MCP server — there's no category-specific config location.
›Do I need to restart VS Code after adding a Version Control MCP server?
Yes — run "MCP: Open User Configuration" from the command palette to edit a config that applies across all your workspaces. That's true whether you're adding GitLab MCP Server or any other Version Control server.