Gitee
Related Servers
Alternatives to Gitee
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceFull-featured MCP server exposing 200+ Gitee API v5 endpoints for repository, issue, pull request, user, enterprise, gist, and search management.10011 npmMIT
- AlicenseAqualityBmaintenanceMCP server for managing Gitea repositories via the Gitea API, enabling operations on issues, comments, labels, milestones, and repository info.7243 npm1MIT
- AlicenseBqualityDmaintenanceMCP server for interacting with Gitea, enabling issue and PR management, repository browsing, file reading, and safe git command execution.1137 npm1MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for GitHub operations, providing tools for repository management, issues, pull requests, and code search.-
- AlicenseNot gradedqualityDmaintenanceAn MCP server for managing your repositories on Forgejo/Gitea server.69Mozilla Public 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server for the GitCode API, enabling AI assistants to interact with GitCode repositories, issues, pull requests, and more.1MIT
TDQS
Scored across 20 tools
Every tool has a clearly distinct purpose targeting specific resources and actions in the Gitee domain. There is no overlap between tools like create_issue, update_issue, and get_issue, or between list_branches and get_branch, making misselection unlikely.
All tool names follow a consistent verb_noun pattern with snake_case throughout, such as create_issue, list_branches, and update_pull_request. This predictability aids agents in understanding and using the toolset effectively.
With 20 tools, the count is slightly high but reasonable for a comprehensive Gitee API server covering repositories, issues, pull requests, branches, files, and users. It might feel heavy but each tool appears to earn its place in the domain.
The toolset provides complete CRUD/lifecycle coverage for Gitee operations, including repository management (create, fork), issue handling (create, get, list, update, comment), pull request workflows (create, get, list, update, merge), branch operations, file management, and user info. No obvious gaps exist for core workflows.