forgejo-mcp
Related Servers
Alternatives to forgejo-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to interact with a Forgejo instance as an authenticated user, supporting issues, pull requests, repositories, and notifications.40 npmMIT
- FlicenseAqualityBmaintenanceEnables assistants to read Forgejo repositories and manage issues and pull requests directly from the working session, using the caller's own token against any Forgejo instance.13-
- AlicenseAqualityDmaintenanceEnables AI assistants to manage Gitea repositories, issues, and pull requests via the tea CLI, including full PR review workflows.154 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to perform GitHub operations such as creating repositories, issues, pull requests, and more through natural language.-
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to interact with GitHub directly by fetching repository information, creating issues, and triggering repository_dispatch events through natural language.MIT
- AlicenseBqualityDmaintenanceEnables AI assistants to interact with Gitea repositories through intelligent tools for issue/PR management, workflow analysis, compliance checking, and content generation, plus 200+ CLI commands for complete CRUD operations.2224 npm6MIT
TDQS
Scored across 50 tools
Most tools pair a unique resource with a unique action, so issue/PR/review/file/workflow tools are easy to tell apart. The only mild ambiguity is among list_repos, list_org_repos, and list_my_repos, which overlap somewhat depending on the owner scope.
Tool names follow a consistent verb_noun snake_case convention throughout, using predictable verbs like list, get, create, update, delete, merge, and dispatch. Even grouped features like get_my_user/list_my_repos and mark_notifications_read follow the same pattern.
50 tools is well above the 25-tool threshold and makes the server heavy for an agent to reason over, even though Forgejo is a broad platform. Several niche read/list operations could be consolidated or exposed as optional subresources.
Core repository, file, issue, pull request, and review workflows are well covered. However, labels and milestones only support list/create with no update/delete, workflow support lacks listing/canceling/rerunning, and pull-review comments cannot be edited or deleted.