mcp-gitee
Related Servers
Alternatives to mcp-gitee
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceMCP Tool Server for Gitee, supporting the management of repository files/branches, Issues, and Pull Requests.2059 npm7MIT
- AlicenseAqualityBmaintenanceMCP server for managing Gitea repositories via the Gitea API, enabling operations on issues, comments, labels, milestones, and repository info.7243 npm1MIT
- AlicenseNot gradedqualityBmaintenanceGitee API integration, repository, issue, and pull request management, and more.65MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for the GitCode API, enabling AI assistants to interact with GitCode repositories, issues, pull requests, and more.1MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server for managing your repositories on Forgejo/Gitea server.69Mozilla Public 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server for the GitHub API, enabling file operations, repository management, search functionality, issues, pull requests, and more.64 npmMIT
TDQS
Scored across 267 tools
The 267 tools are clearly delineated by action and resource (e.g., gitee_create_issue, gitee_list_issues, gitee_update_issue). Each tool's description provides a distinct purpose, and there is no ambiguity between tools handling different resources or operations.
All tool names follow a uniform 'gitee_verb_noun' pattern in snake_case, such as 'gitee_add_collaborator', 'gitee_delete_issue_comment'. No mixed conventions or irregularities are present.
With 267 tools, the surface is overly large. Many tools list subtypes (e.g., 5 different list tools for issues) that could be consolidated with parameters. This number risks overwhelming agents and hindering quick selection.
The tool set covers a comprehensive range of GitEE features: full CRUD for issues, pull requests, releases, gists, organizations, enterprises, and more. Essential operations like branch protection, webhooks, and notifications are all present.