Skip to main content
Glama
Sign In
forgejo-mcp-server

forgejo-mcp-server

by Birdiz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to forgejo-mcp-server

No user-submitted related servers found.

    Related Servers

    • forgejo-mcp

      openmanbo
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to interact with a Forgejo instance as an authenticated user, supporting issues, pull requests, repositories, and notifications.
      387 npm
      MIT

    • Git MCP Server

      EnesOzturk11
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to inspect local Git repositories and interact with the GitHub API for reading commits, diffs, files, issues, comments, pull requests, and project boards.
      10
      129 npm
      ISC

    • github-mcp

      Seey215
      A
      license
      C
      quality
      D
      maintenance
      Enables AI assistants to directly operate GitHub repositories, such as listing issues, through the Model Context Protocol.
      2
      230 npm
      2
      Apache 2.0
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A4.4/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: identity, repos, issues, PRs, branches, commits, and files. Even where issue and PR numbering overlaps, the descriptions clearly separate issue-side from PR-side operations.

    Naming Consistency4/5

    The forgejo_ prefix plus verb_noun pattern is consistent across nearly all tools: list_repos, get_issue, create_pull_request, list_commits, get_file. The only minor deviation is forgejo_whoami, which uses a bare verb instead of verb_noun.

    Tool Count5/5

    13 tools is a well-scoped size for a Forgejo server covering authentication, repositories, issues, pull requests, branches, commits, and file access. Each tool addresses a clear need without redundancy or bloat.

    Completeness4/5

    Issue management is well covered with list/get/create/update/comment, and PRs have list/get/create plus branch discovery and file reading. The main gap is the lack of PR update or merge operations, but the core read-and-create workflows agents commonly need are present.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources