forgejo-mcp-rs
Related Servers
Alternatives to forgejo-mcp-rs
- AlicenseBqualityCmaintenanceA Model Context Protocol (MCP) server for Forgejo and Gitea instances, enabling AI assistants to interact with repositories, issues, pull requests, and more.10017MIT
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables multiple users and hosted assistants to connect to a private Forgejo instance through OAuth or token pass-through, acting only with each user's own token permissions. Provides MCP tools to browse repositories, files, commits, issues, pull requests, actions, and releases, and to perform guarded writes such as creating issues, branches, files, and pull requests.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables self-hosted, read-only remote interaction with GitHub repositories, allowing listing repositories, searching code, and inspecting commits, pull requests, issues, and diffs via authenticated MCP clients.598 npmMIT
- AlicenseAqualityCmaintenanceEnables any MCP client to read GitHub repositories, branches, tags, pull requests, files and Actions workflow runs, and optionally create branches and pull requests, comment, assign, approve, trigger workflows, merge and delete. Read-only by default, with separate opt-in switches for write and destructive operations, working against github.com or GitHub Enterprise Server.11MIT
- AlicenseNot gradedqualityBmaintenanceA remote multi-tenant MCP server that lets AI agents read repositories and create work branches with multi-file commits on Forgejo or Gitea instances, while leaving review and merging to a person and blocking destructive or administrative actions.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceThis MCP server enables users to interact with Forgejo instances through a finite, audited catalog of 33 tools covering users, repositories, issues, pull requests, and more, with explicit write controls and verified result envelopes.18 npmMIT
- AlicenseNot gradedqualityCmaintenanceGives any MCP client read-only tools for private GitHub repositories, with OAuth-based authentication and an allowlist of GitHub logins.MIT
TDQS
Scored across 59 tools
Each tool targets a distinct resource and action, and overlapping areas are explicitly disambiguated by the descriptions (e.g. get_combined_status vs get_commit_statuses, get_file_contents vs get_repo_tree, list_issues vs list_pull_requests). The cross-references between related tools make misselection unlikely despite the large surface.
The set predominantly follows a verb_noun snake_case convention (list_repos, get_issue, create_pull_request, delete_branch), which is predictable. Minor deviations like version, whoami, write_status, and enable_write_mode/disable_write_mode keep it from being perfect but do not impede understanding.
With 59 tools, the server is far above the practical 3-15 tool range and presents a heavy surface for an agent to navigate. The breadth of Forgejo's API partially justifies the scope, but the count is still excessive for reliable tool selection.
Core lifecycle coverage is strong across repositories, branches, files, commits, issues, pull requests, releases, assets, workflows, notifications, organizations, keys, and mirrors. Minor gaps remain, such as dedicated label/milestone CRUD, tag listing, webhook/team management, and comment editing/deletion, but no major workflow is blocked.