git-mcp-server and gitlab-mcp-server
These are complements: the Git-focused MCP server provides low-level repository operations (clone, commit, branch, diff) while the GitLab-focused MCP server layers GitLab-specific abstractions (projects, issues, merge requests, CI/CD) on top, allowing an AI agent to both manipulate repositories directly and manage GitLab's platform features in the same session.
About git-mcp-server
cyanheads/git-mcp-server
An MCP (Model Context Protocol) server enabling LLMs and AI agents to interact with Git repositories. Provides tools for comprehensive Git operations including clone, commit, branch, diff, log, status, push, pull, merge, rebase, worktree, tag management, and more, via the MCP standard. STDIO & HTTP.
This server helps AI agents or large language models (LLMs) manage code repositories. It allows them to perform common Git operations like cloning projects, committing changes, creating branches, merging code, and publishing updates. It's designed for developers who are building AI systems that need to interact with and modify source code.
About gitlab-mcp-server
Alosies/gitlab-mcp-server
A fully-typed TypeScript MCP server for comprehensive GitLab API integration with Claude Desktop. Manage projects, issues, merge requests, CI/CD pipelines, and job logs with advanced features for large-scale DevOps workflows.
This tool integrates GitLab with Claude Desktop, allowing you to manage your software development projects using natural language commands. You can input requests like 'List my GitLab projects' or 'Create a merge request,' and it will interact with GitLab to provide information or execute actions. It's designed for software developers, DevOps engineers, and project managers who use GitLab for code hosting and project management.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work