Gitee MCP Server vs GitHub (read Only)
A side-by-side look at the Gitee MCP Server and GitHub (read Only) MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Gitee MCP Server for version control work as a local process; choose GitHub (read Only) for version control as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Gitee MCP Server when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
GITEE_ACCESS_TOKEN, GITEE_MODE.
Choose GitHub (read Only) when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 40/100 · Fair | 33/100 · Emerging |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Not declared |
| Required env vars | GITEE_ACCESS_TOKENGITEE_MODE | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Gitee MCP Server | View GitHub (read Only) |
Tools & capabilities
Gitee MCP Server tools
No tool names declared yet. Check the project README from the listing page.
GitHub (read Only) tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Gitee MCP Server
{
"mcpServers": {
"gitee-mcp-server": {
"command": "npx",
"args": [
"-y",
"gitee-mcp"
],
"env": {
"GITEE_ACCESS_TOKEN": "YOUR_GITEE_ACCESS_TOKEN_HERE",
"GITEE_MODE": "YOUR_GITEE_MODE_HERE"
}
}
}
}
GitHub (read Only)
{
"mcpServers": {
"github-read-only": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/AbdulMuhaiminKhan/github-mcp",
"github-mcp"
]
}
}
}
Frequently asked questions
Gitee MCP Server is categorized under Version Control and uses a local stdio subprocess. GitHub (read Only) belongs to Version Control and uses a local stdio subprocess. Pick Gitee MCP Server for version control work and GitHub (read Only) for version control.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Gitee MCP Server has no declared pricing — check the project's own site. GitHub (read Only) has no declared pricing — check the project's own site. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add gitee-mcp-server and github-read-only as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Gitee MCP Server has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. GitHub (read Only) has 33/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars.