git-mcp-server and mcp-gitee
These are ecosystem siblings, as they are both MCP server implementations, with one providing Git operations for GitHub and the other providing Gitee API 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 mcp-gitee
oschina/mcp-gitee
mcp-gitee is a Model Context Protocol (MCP) server implementation for Gitee. It provides a set of tools that interact with Gitee's API, allowing AI assistants to manage repository, issues, pull requests, etc.
Built in Go, the server supports multiple transport protocols (stdio, SSE, HTTP) and integrates seamlessly with AI development tools like Claude, Cursor, and Cline via standard MCP configuration. It offers granular toolset management through whitelist/blacklist modes, enabling selective exposure of 40+ Gitee API operations across repositories, pull requests, issues, and notifications, with support for both Gitee cloud and self-hosted enterprise instances.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work