mcp-gitee and github-repo-mcp

These are ecosystem siblings, specifically two distinct Model Context Protocol (MCP) server implementations, with one (Ryan0204/github-repo-mcp) targeting GitHub repositories and the other (oschina/mcp-gitee) targeting Gitee, demonstrating the protocol's application across different Git-based platforms rather than direct competition for a single platform or complementary usage.

mcp-gitee
52
Established
github-repo-mcp
44
Emerging
Maintenance 10/25
Adoption 8/25
Maturity 16/25
Community 18/25
Maintenance 2/25
Adoption 7/25
Maturity 18/25
Community 17/25
Stars: 52
Forks: 13
Downloads:
Commits (30d): 0
Language: Go
License: MIT
Stars: 26
Forks: 11
Downloads:
Commits (30d): 0
Language: JavaScript
License: MIT
No Package No Dependents
Stale 6m

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.

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.

Scores updated daily from GitHub, PyPI, and npm data. How scores work