"Forgejo" matching MCP servers:

A Model Context Protocol (MCP) server for Forgejo and Gitea instances, enabling AI assistants to interact with repositories, issues, pull requests, and more.

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.

Enables AI assistants to manage Forgejo repositories, issues, pull requests, files, commits, Actions workflow runs, organizations, and notifications through the Forgejo REST API using natural language.

Enables AI agents to interact with a Forgejo instance as an authenticated user, supporting issues, pull requests, repositories, and notifications.

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.

An MCP server for managing your repositories on Forgejo/Gitea server.

Enables assistants to read Forgejo repositories and manage issues and pull requests directly from the working session, using the caller's own token against any Forgejo instance.

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.

A Model Context Protocol (MCP) server that provides Claude Desktop with tools to interact with Forgejo repositories, including listing repos, issues, and reading files.

Enables AI agents to automate project management on self-hosted Forgejo v15, including managing Projects/Kanban boards, columns, cards, issues, and milestones, despite Forgejo lacking a REST API for Projects.

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.

Exposes a streamable HTTP endpoint where each user signs in with their own Forgejo OAuth account and then browses and manages remote repositories, issues, pull requests, Actions, and dispatches under their own permissions. It is read-only by default, with write tools enabled only when explicitly configured and requested, using signed per-user approval grants instead of a shared access token.

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.

Provides ~200 auto-generated tools and resources for LLM agents to interact with Gitea and Forgejo instances via the Model Context Protocol.

Enables cross-repository code search over a local mirror of a self-hosted Gitea or Forgejo instance, covering file contents, file paths, and commit messages across all repositories and branches. It also lets users read a single file from the mirror and list mirrored repositories, all without network access during search or read.

Collection of MCP servers for Forgejo, NetBox, Authentik, and CouchDB, enabling issue tracking, device management, authentication, and database operations via MCP and CLI.

A remote multi-tenant MCP server that lets AI agents read repositories and create work branches with multi-file commits on Forgejo or Gitea instances, while leaving review and merging to a person and blocking destructive or administrative actions.

MCP server for Forgejo that exposes tools for pull requests, repositories, and issues, leveraging the local fj CLI.