MCP category
Version Control
Repositories, code review, and source history.
4 MCP servers Selection guide
How to choose a version control MCP server
Start with the endpoint owner, the authentication model, and the data the workflow needs. Test one read-only call before you connect private records. The review guides explain the checks.
The directory
All servers in Version Control
Every entry includes its remote endpoint, transport, authentication, and client setup. Check the provider's docs before connecting private data.
Showing 4 of 4 servers.
GitHubOfficialVersion ControlOfficial GitHub MCP server for repository search, issues, pull requests, code context, and GitHub workflows in MCP-compatible AI clients.api.githubcopilot.comView setupGitLabOfficialVersion ControlGitLab connects AI tools securely to repository, issue, merge request, and DevSecOps data. Its connector gives assistants GitLab project context for understanding code work, collaboration, security workflows, and delivery status.gitlab.comView setupCarbon ForgeVersion ControlCarbon Forge keeps code, files and prose in one record on the server, and people and agents read and write it through the same tools over MCP. Agents open lanes instead of cloning, every landing is one all-or-nothing changeset, and git is a projection pushed to GitHub. Public workspaces are free.carbonforge.devView setupGitHub Repo Change IntelligenceVersion ControlTracks releases, stars, issues and pushes for any public GitHub repository, for dependency and open-source monitoring. A free snapshot is available; paid intel uses x402 USDC settlement or a monthly access key passed as ?key=. Run it locally with npx -y github-repo-change-intelligence.s-github.pixharvest.comView setup
Other MCP categories
Keep exploring the hosted directory.