git-mcp-server and github-repo-mcp
The two tools are ecosystem siblings because B appears to be a specialized MCP server for GitHub repositories, potentially built upon or leveraging the general Git MCP server capabilities offered by A.
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-repo-mcp
Ryan0204/github-repo-mcp
Model Context Protocol server for Github Repo // Reading Github Repo
Exposes three tools—`getRepoAllDirectories`, `getRepoDirectories`, and `getRepoFile`—enabling AI assistants to browse public GitHub repositories and retrieve file contents through the Model Context Protocol. Uses stdio transport for integration with MCP clients (Cursor, Claude Desktop, Windsurf) and supports optional GitHub token authentication to increase API rate limits beyond the unauthenticated 60-request/hour threshold.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work