forgejo-mcp
Related Servers
Alternatives to forgejo-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceA bundled MCP server that lets Claude work with any Gitea instance — gitea.com or self-hosted — covering repositories, files, branches, issues, pull requests and reviews, organisations and teams, Gitea Actions runs and logs, releases, webhooks and notifications. It exposes 126 tools with tiered read/write/destructive/admin permissions, secure token handling, and workflow skills for tasks like pull request review and CI failure analysis.Apache 2.0
- AlicenseBqualityCmaintenanceEnables AI agents to read repositories, manage issues, inspect CI/CD workflow runs, create branches, commit files, and open pull requests on a self-hosted Gitea instance.7MIT
- 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.2281 npm6MIT
- AlicenseCqualityBmaintenanceEnables 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
- AlicenseNot gradedqualityBmaintenanceEnables users to manage self-hosted Git repositories from ChatGPT and compatible Codex clients via OAuth-secured connections, with independent browser approval for write actions. Supports repository, file, branch, issue, pull request, release, and workflow operations while excluding administrative tools.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceA local MCP server that connects Claude directly to your Gitea instance, enabling management of repositories, issues, pull requests, files, and commit history.MIT
TDQS
Scored across 49 tools
Most tools target a clear resource+action, but several list/search pairs overlap: search_issues vs list_issues, list_pull_requests vs search_issues (PRs are issues in Forgejo), and get_file_contents duplicating listing-directory semantics. Descriptions mostly disambiguate, though an agent could still misselect between list and search variants.
Overwhelmingly consistent verb_noun pattern (list_*, get_*, create_*, update_*, merge_*, add_*, remove_*). Minor deviations like create_or_update_file and dispatch_workflow are still readable and purposeful. The 'list_pull_request_*' long forms are consistent within their family.
49 tools is heavy for a single MCP server and exceeds the 25+ threshold. The surface spans repos, files, branches, commits, issues, PRs, reviews, labels, releases, milestones, and Actions CI—workable but burdened with granular tools that could be consolidated or grouped.
Broad, well-rounded coverage of the Forgejo/Gitea domain: full file CRUD, branches, commits, issues, PRs, reviews, labels, releases, and CI status/workflows. Some gaps remain (e.g., deleting/editing releases, managing milestones, listing PR reviewers/assignees, closing organizations), but core workflows are covered.