Skip to main content
Glama
@wyattjoh/forgejo-mcp
by wyattjoh

Related Servers

Alternatives to @wyattjoh/forgejo-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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
    • A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to read a Forgejo, Codeberg, or Gitea instance—including users, repositories, issues, pull requests, search, notifications, comments, reviews, and Actions runs—with opt-in, time-boxed guarded writes for repository, branch, issue, pull request, comment, migration, push-mirror, and workflow operations.
      59
      2
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to interact with the Gitea API through a secure multi-tenant proxy, exposing 257 tools across 22 resource domains for CRUD, search, and repository management. Supports identity passthrough and token-optimized responses while scoping actions to each authenticated user's permissions.
      GPL 3.0
    • A
      license
      Not graded
      quality
      B
      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
    • A
      license
      Not graded
      quality
      A
      maintenance
      A gateway that lets an agent read repositories, issues, and pull requests across multiple GitHub user and organization accounts, with a separate token per owner selected automatically server-side so credentials are never exposed to the client. Optional writes such as creating issues are off by default and require per-request administrator approval.
      MIT