Full-featured Gitee MCP server covering all Gitee API v5 endpoints
If you already use MCP, the mcp mcp server is the piece that lets your assistant work with it directly. Full-featured Gitee MCP server covering all Gitee API v5 endpoints.
Set the GITEE_ACCESS_TOKEN environment variable to your Gitee personal access token.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Machine — readable spec: https://gitee.com/api/v5/doc_jsonRepositories — create, update, delete, list, file operations, branches, tags, commitsIssues — create, update, comment, labels, milestonesEnterprises — members, repos, issuesGists — create, fork, star, commentActivity — notifications, starring, watchingSearch — repos, users, issuesConfiguration is passed through the environment: GITEE_ACCESS_TOKEN, GITEE_API_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Set the GITEE_ACCESS_TOKEN environment variable to your Gitee personal access token. Optionally override the API base URL (defaults to https://gitee.com/api/v5):
The server ships on npm as mcp-gitee, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP's toolset — Machine, Repositories, Issues and 4 more — is a fair guide to whether it matches your workflow. It is maintained by caindez; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Machine | readable spec: https://gitee.com/api/v5/doc_json |
| Repositories | create, update, delete, list, file operations, branches, tags, commits |
| Issues | create, update, comment, labels, milestones |
| Enterprises | members, repos, issues |
| Gists | create, fork, star, comment |
| Activity | notifications, starring, watching |
| Search | repos, users, issues |
{
"mcpServers": {
"gitee-1": {
"command": "npx",
"args": ["-y", "mcp-gitee"],
"env": {
"GITEE_ACCESS_TOKEN": "your-value",
"GITEE_API_URL": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Set the GITEE_ACCESS_TOKEN environment variable to your Gitee personal access token. Optionally override the API base URL (defaults to https://gitee.com/api/v5):
| Variable | Description | Required |
|---|---|---|
| GITEE_ACCESS_TOKEN | Credential the server authenticates with. | Yes |
| GITEE_API_URL | Endpoint or connection string the server talks to. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.