Skip to main content
Glama
Sqcows

forgejo-mcp

by Sqcows
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to forgejo-mcp

No user-submitted related servers found.

    Related Servers

    • Forgejo MCP Server

      nsvk13
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that provides Claude Desktop with tools to interact with Forgejo repositories, including listing repos, issues, and reading files.
      8
      10
      GPL 3.0

    • Forgejo MCP

      kepatrick
      A
      license
      Not graded
      quality
      A
      maintenance
      A self-hosted MCP server and dashboard that provides governed, auditable AI access to a Forgejo instance, with tools for managing repositories, issues, pull requests, and more.
      3
      Apache 2.0

    • gitea-mcp

      werebear73
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that enables AI assistants to read, create, and manage issues, repositories, and releases on Gitea, Forgejo, or Codeberg instances via personal access tokens.
      21
      143 PyPI
      1
      MIT

    • GitHub MCP Server

      renantrendt
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants to perform GitHub operations including repository management, file operations, issue tracking, and pull request creation.
      2
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.3/5.0

    Scored across 103 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose targeting a specific resource and action. Despite the large number, descriptions are sufficiently detailed to differentiate between similar operations (e.g., list_org_repos vs list_user_repos).

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in snake_case (e.g., create_branch, list_issues, edit_repo). The naming convention is uniform across all 103 tools, with no mixing of styles.

    Tool Count2/5

    103 tools is excessive for any MCP server, even a comprehensive one like Forgejo. This volume can overwhelm agents and makes navigation difficult. Many admin-specific tools could be grouped or reduced.

    Completeness4/5

    Covers most CRUD operations for users, repos, issues, PRs, orgs, teams, labels, milestones, releases, files, branches, and more. Minor gaps exist (e.g., no delete_team or remove_org_member), but overall the surface is comprehensive.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources