git-mcp-server and github-chat-mcp
One is an MCP server for general Git operations, while the other is an MCP focused on interacting with GitHub repositories via its chat API, making them potential complements where the chat-focused tool could leverage the general Git operations server for deeper repository interactions.
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-chat-mcp
AsyncFuncAI/github-chat-mcp
A Model Context Protocol (MCP) for analyzing and querying GitHub repositories using the GitHub Chat API.
Provides repository indexing and querying capabilities through two core tools, enabling semantic search and architectural analysis of codebases via the GitHub Chat API backend. Integrates directly with Claude Desktop and Cursor through MCP protocol, with uv-based installation and support for environment-based configuration. Built on FastMCP framework with adjustable logging and includes an MCP Inspector for local debugging.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work