A
licenseA
qualityD
maintenanceEnables AI assistants to manage Gitea repositories, issues, and pull requests via the tea CLI, including full PR review workflows.
15
19 npm
MIT
Gitea MCP Tool
by SupenBysz
Related Servers
Alternatives to Gitea MCP Tool
No user-submitted related servers found.
Related Servers
- -licenseBqualityNot gradedmaintenanceEnables comprehensive Git and GitHub operations through 30 DevOps tools including repository management, file operations, workflows, and advanced Git features. Provides complete Git functionality without external dependencies for seamless integration with Gitea and GitHub platforms.18819 npm-
- AlicenseNot gradedqualityBmaintenanceConnects AI tools to GitHub and local git repositories, enabling natural language management of issues, PRs, code analysis, and workflows.1MIT
- AlicenseCqualityCmaintenanceEnables AI assistants to manage Forgejo repositories, issues, pull requests, files, commits, Actions workflow runs, organizations, and notifications through the Forgejo REST API using natural language.50MIT
- AlicenseAqualityAmaintenanceEnables AI assistants to perform Git workflows with semantic commit messages, pre-PR secret audits, conflict resolution, and release changelog generation.5MIT
- AlicenseAqualityAmaintenanceAn MCP server providing comprehensive Gitea API coverage with 186 tools for managing repositories, issues, pull requests, and CI/CD workflows. It enables autonomous AI agents to perform complex development and administrative tasks directly through a Gitea instance.7MIT
TDQS
B3.3/5.0
Scored across 22 tools
Disambiguation4/5
Most tools have distinct purposes, but there is some overlap in the compliance and workflow categories that could cause confusion. For example, gitea_compliance_check_all and the individual compliance checks (branch, commit, pr) might be ambiguous about when to use each, and the workflow tools like gitea_workflow_check_issues and gitea_workflow_generate_report have overlapping functions in analyzing issues. However, descriptions help clarify boundaries.
Naming Consistency5/5
Tool names follow a highly consistent pattern with the prefix 'gitea_' followed by a category (e.g., compliance, context, workflow) and a descriptive verb_noun combination. All tools use snake_case uniformly, making them predictable and easy to parse. This consistency aids in understanding the tool set at a glance.
Tool Count3/5
With 22 tools, the count is on the higher side for a server focused on Gitea integration, which might feel heavy and potentially overwhelming. While it covers compliance, context, issues, PRs, and workflow automation, some tools could be consolidated or omitted without losing functionality, indicating borderline appropriateness for the scope.
Completeness4/5
The tool set provides comprehensive coverage for compliance checks, issue and PR creation, workflow automation, and context management in Gitea. Minor gaps exist, such as missing tools for updating or deleting issues/PRs, and limited operations on repositories beyond compliance (e.g., no list_repos or get_repo). However, agents can work around these with the available tools for core workflows.
Maintenance
ActivityInactive
ResponsivenessNo issues