Skip to main content
Glama
nsvk13

Forgejo MCP Server

by nsvk13
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Forgejo MCP Server

No user-submitted related servers found.

    Related Servers

    • fj-mcp

      jairov4
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Forgejo that exposes tools for pull requests, repositories, and issues, leveraging the local fj CLI.
      -

    • my-mcp-server

      15972289829
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that allows integration with Claude Desktop by creating and managing custom tools that can be executed through the MCP framework.
      56 npm
      -

    • gitea-mcp

      datamathcode
      A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that connects Claude directly to your Gitea instance, enabling management of repositories, issues, pull requests, files, and commit history.
      MIT

    • @vbcdx/forgejo-plugin

      VBCDX
      A
      license
      Not graded
      quality
      C
      maintenance
      This 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.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct resource (issue, PR, file, repository) with specific actions, so there is no ambiguity. An agent can clearly differentiate between creating issues, listing pull requests, or getting file content.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case (e.g., create_issue, get_file_content), making them predictable and easy to understand.

    Tool Count5/5

    With 8 tools covering core operations for issues, pull requests, repositories, and file content, the scope is well-balanced for a Git forge server—neither too sparse nor overwhelming.

    Completeness3/5

    The tool set covers create and read operations for issues and PRs, plus repository and file access, but notably lacks update/delete operations (e.g., update_issue, merge_pull_request) and repository creation, leaving notable gaps for full lifecycle management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources