git-mcp-server and gitlab-mr-mcp
These two tools are ecosystem siblings within the MCP framework, with the first providing a generic Git MCP server for comprehensive repository operations and the second offering a specialized GitLab client for merge request and issue management, likely leveraging or extending the MCP protocol.
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.
Provides 28 tools organized by workflow (staging, branching, remote ops, advanced), plus session-based resource management and a structured wrap-up prompt for guided git workflows. Built on pluggable architecture with declarative tool definitions, dependency injection via tsyringe, and support for commit signing—with cross-runtime detection for Bun and Node.js via auto-spawned git processes. Integrates with MCP clients (Cline, Claude Desktop) over stdio or HTTP transports, with configurable git identity, path sanitization for security, and optional OpenTelemetry observability.
About gitlab-mr-mcp
kopfrechner/gitlab-mr-mcp
Interact seamlessly with GitLab repositories to manage merge requests and issues. Fetch details, add comments, and streamline your code review process with ease.
Implements the Model Context Protocol (MCP) standard to expose GitLab operations as tools for AI agents, enabling line-specific code comments on diffs and bulk MR/issue management. Built as a Node.js server that authenticates via GitLab API tokens and integrates with AI clients like Claude Desktop through Smithery, supporting configurable project filtering and access-level restrictions.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work