A
licenseB
qualityD
maintenanceMCP server for interacting with Gitea, enabling issue and PR management, repository browsing, file reading, and safe git command execution.
11
37 npm
1
MIT
gitea-mcp
by amonstack
Related Servers
Alternatives to gitea-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server for managing your repositories on Forgejo/Gitea server.69Mozilla Public 2.0
- AlicenseBqualityDmaintenanceMCP Tool Server for Gitee, supporting the management of repository files/branches, Issues, and Pull Requests.2059 npm7MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for OpenDev Gitea and Gerrit APIs, enabling repository browsing, code review, and change management for LLM agents.Apache 2.0
- FlicenseNot gradedqualityCmaintenanceUnified MCP server for Git forge management across GitHub, GitLab, Gitea, and Bitbucket, enabling repository, issue, PR, and CI/CD operations via CLI tools and APIs.-
- AlicenseAqualityCmaintenanceAn MCP server that enables AI assistants to read, create, and manage issues, repositories, and releases on Gitea, Forgejo, or Codeberg instances via personal access tokens.21120 PyPIMIT
TDQS
A3.9/5.0
Scored across 72 tools
Disambiguation3/5
Most tools target distinct resources and actions, but the sheer number creates confusion risk: list_issues can include PRs, get_release vs get_release_by_tag are near-duplicates, and the dependency/block pairs (add_issue_dependency vs add_issue_block) require careful reading. The detailed descriptions help, but some overlap exists.
Naming Consistency4/5
The vast majority follow a clear verb_noun snake_case pattern (create_issue, list_releases, update_milestone). Minor deviations like gitea_status, is_pull_merged, and the edit/update and remove/delete alternations keep it from being perfect, but the pattern is largely predictable.
Tool Count1/5
72 tools is an extreme agent-facing surface, far beyond the 25+ 'too many' threshold and into the 50+ extreme-mismatch range. Several tools are near-variants (label-set mutations, dependency/block pairs, attachment variants), and two project tools are explicit no-op placeholders.
Completeness3/5
Core workflows for issues, PRs, labels, milestones, releases, wiki, and Actions are extensively covered with full CRUD. However, repository lifecycle is incomplete (no create_repo/delete_repo/get_repo), project boards are placeholders, and PR reviews and release attachments are missing.
Maintenance
ActivityMaintained
ResponsivenessResponsive