git-mcp-server and github-mcp-server
The "cyanheads/git-mcp-server" is a competitor to "github/github-mcp-server," as both provide Model Context Protocol (MCP) servers enabling LLMs and AI agents to interact with Git repositories, differing in their origin and feature set.
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 github-mcp-server
github/github-mcp-server
GitHub's official MCP Server
Exposes GitHub's API capabilities through the Model Context Protocol, enabling AI agents to browse repositories, manage issues and pull requests, analyze code patterns, and trigger CI/CD workflows via natural language. Operates as both a remote HTTP service (hosted by GitHub with OAuth/PAT authentication) and a local binary, integrating seamlessly with VS Code, Claude Desktop, Cursor, and other MCP-compatible hosts. Provides granular toolset configuration, policy governance controls, and an insiders track for experimental features like security analysis and workflow intelligence.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work