Skip to main content
Glama
krunkmetalist

Gitea MCP Server

by krunkmetalist
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Gitea 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.
      81 npm
      MIT

    • Gitea MCP Tool

      SupenBysz
      A
      license
      B
      quality
      D
      maintenance
      Enables 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.
      22
      84 npm
      6
      MIT

    • Gitea for ChatGPT

      Tracht-Digital-Solutions
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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

    • forgejo-mcp

      jerdog
      A
      license
      C
      quality
      B
      maintenance
      Enables Claude to manage repositories, files, branches, commits, issues, pull requests, labels, releases, and CI workflows on Forgejo and Gitea instances, including Codeberg and self-hosted or private deployments, through the shared /api/v1 REST API. It runs locally over stdio with token-based auth and an optional read-only mode that hides all write tools.
      49
      41 npm
      MIT

    • Gitea

      Tracht-Digital-Solutions
      A
      license
      Not graded
      quality
      A
      maintenance
      A 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
    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 7 tools

    Disambiguation5/5

    Each tool targets a clearly distinct resource and action: listing repositories, managing issues (list/create), workflow runs, branches, pull requests, and file commits. No two tools share overlapping purposes.

    Naming Consistency5/5

    All tools follow a consistent verb_noun snake_case pattern (list_repositories, create_issue, create_pull_request, commit_files). The convention is uniform throughout the set.

    Tool Count5/5

    Seven tools is well-scoped for a Gitea integration, covering core repository, issue, CI, branch, PR, and file operations without bloat.

    Completeness3/5

    The surface is write-heavy and lacks lifecycle coverage: issues have list+create but no get/update/close, PRs can only be created (no get/list/merge), and branches/files have no read or delete operations. Notable gaps that would block common workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources