git-mcp-server and gitlab-mcp
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-mcp
mcpland/gitlab-mcp
A MCP server for GitLab with powerful, safe, policy-controlled access
Exposes 80+ tools across GitLab resources (MRs with code-context analysis, pipelines, wikis, releases, file management) via stdio or Streamable HTTP transports with flexible auth (OAuth 2.0 PKCE, PAT, remote token scripts, cookie-based). Enforces granular access control through read-only mode, tool allowlists/denylists, and project-scoped restrictions, while supporting enterprise networking (proxy, custom CAs, multi-instance rotation) and multiple output formats with size limits.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work