Skip to main content
Glama
727,809 tools. Updated 2026-10-31 06:34

"Forgejo" matching MCP tools:

  • Reports the MCP server and connected Forgejo/Gitea instance details, including release numbers, flavor, and reachability, so you can confirm compatibility before using release-dependent tools.
    MIT
  • Triggers a Forgejo or Gitea Actions workflow via workflow_dispatch using owner, repo, workflow file, and ref, with optional inputs; requires write access.
    MIT
  • Authenticate to Forgejo to establish a session and cache it for reuse. Force a fresh login to override cached credentials when needed.
    -
  • Check Forgejo authentication status and authenticate with environment credentials when required, ensuring a valid session for project management automation.
    -
  • Search repositories on a Forgejo instance using a query string. Supports pagination and maximum results per page.
    MIT

Matching MCP Servers

  • 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
  • List all organizations on the Forgejo instance with support for pagination via page and limit parameters.
    MIT
  • Find users on a Forgejo instance using a search query, with options to paginate results and set a maximum number of users per page.
    MIT
  • Retrieve the NodeInfo of a Forgejo instance to obtain metadata about its software version, protocols, and features.
    MIT
  • Retrieve all Actions workflows defined in a Forgejo or Gitea repository by owner and repo to inspect CI pipeline configurations.
    MIT
  • Search Forgejo/Gitea repositories by keyword, with optional topic filtering and pagination, to locate projects, code hosts, or organization repos.
    MIT
  • Trigger a workflow_dispatch run in a Forgejo/Gitea repository to manually start CI workflows with optional inputs.
    MIT
  • Posts a Markdown comment on a Forgejo issue or pull request using the repository owner, name, and issue number; check prior comments before retrying to avoid duplicate posts.
    MIT
  • Read a Forgejo/Gitea Actions job log by owner, repo, and job ID, returning the tail first to expose failures; adjust byte windows and optionally keep timestamps.
    MIT
  • Lists notification threads from Forgejo, Codeberg, or Gitea accounts, newest first: unread by default, read included with all=true, without marking anything as read.
    MIT
  • List issues in a repository with filters for state, labels, milestones, author, assignee, mentions, and text search. Pull requests are excluded; use the dedicated pull request tool instead.
    MIT
  • List every status reported against a commit, branch, or tag, including each check’s context, state, and target URL, to inspect CI history; use get_combined_status for a single pass/fail verdict.
    MIT
  • Merge a pull request in Forgejo, Codeberg, or Gitea using a chosen merge style, an optional head SHA guard, and optional head branch deletion.
    MIT
    Destructive
  • Set up automatic push mirroring from a Forgejo/Codeberg repository to an external Git remote, so changes sync without a local git push.
    MIT
  • Lists files changed by a Forgejo pull request with per-file additions, deletions, and rename details; use filenames with the diff tool to inspect hunks.
    MIT
  • Lists pull requests in a repository with filters for state, base/head branch, author, sort order, and pagination. Use it to find open PRs for a branch or browse closed requests.
    MIT