Forgejo MCP

What raohwork/forgejo-mcp MCP server does

The raohwork/forgejo-mcp MCP server lets an MCP-compatible AI assistant work with repositories hosted on Forgejo or Gitea. It is intended for repository administration and project coordination rather than local source-code editing. Operations are performed against the configured Forgejo or Gitea instance using an access token.

Issue workflows include creating, editing, and viewing issues, along with adding, removing, or replacing labels. The server can also manage issue comments and attachments and set issue dependencies. For project organization, it supports label and milestone creation, modification, and deletion, plus repository search and listing.

Release features cover version releases and their attachments. Other supported areas include viewing pull requests, managing wiki pages, and viewing Forgejo or Gitea Actions tasks. These capabilities make it a fit for assistants that need to inspect repository status or carry out structured project-management changes.

How it works

The raohwork/forgejo-mcp MCP server provides two operating modes. Stdio mode runs locally and communicates with an AI client over standard input and output. HTTP mode starts a web service for remote MCP connections and can be configured for SSE or Streamable HTTP.

HTTP deployments support either a single shared token or multi-user authentication. Supplying a token when the service starts makes that token apply to operations handled by the server. Without a startup token, clients must send an Authorization: Bearer <token> header with each request. The latter arrangement allows different users to provide their own tokens.

Clients send natural-language requests to the configured MCP connection, while the server translates the requested repository operations for the Forgejo or Gitea instance. The README identifies Claude Desktop and Gemini CLI as local integration examples.

Setup and configuration

Create an access token in the Forgejo or Gitea user settings under Applications and Access Tokens before configuring a client. The README recommends repository and issue write permissions when write operations are needed; choose scopes appropriate to the actions the assistant must perform.

You can run the server with Docker, install it using Go, or download a precompiled binary from the project releases. Stdio configurations pass the server URL and token as command-line arguments. For HTTP, start the service with an address such as :8080 and the target server URL, then configure a client with an SSE endpoint or the Streamable HTTP endpoint.

The supported environment variables are FORGEJOMCP_SERVER for the Forgejo or Gitea URL and FORGEJOMCP_TOKEN for the access token. Using environment variables keeps these values out of client configuration files. The README also recommends limiting token permissions and rotating tokens periodically.

Tools and capabilities

The raohwork/forgejo-mcp MCP server supports these repository-management areas:

• Create, edit, and view issues
• Add, remove, and replace issue labels
• Manage issue comments, attachments, and dependencies
• Create, edit, and delete labels and milestones
• Search and list repositories
• Manage releases and release attachments
• View pull requests
• Manage wiki pages
• View Forgejo or Gitea Actions tasks

Limitations and notes

The material describes repository management through Forgejo and Gitea, but does not document support for other hosting platforms. It also does not specify individual MCP tool names, detailed API coverage, or client-specific setup beyond the provided stdio and HTTP examples.

Write access depends on the permissions granted to the access token. A token with insufficient scopes may not be able to perform issue, repository, label, milestone, or release changes. HTTP deployments should be configured with the appropriate authentication mode: a startup token for one shared identity, or per-request bearer tokens for multi-user access.