Forgejo MCP Server
Forgejo and Gitea repository management for AI assistants and automation tools.
Data last scanned today · Reviewed yesterday
Overview
This server acts as an interface between your AI assistant and Forgejo or Gitea instances, enabling direct management of repositories. It facilitates tracking project progress, categorizing issues, and generating automated documentation or release notes based on the repository content. Capabilities include handling issue lifecycles, organizing milestones, managing labels, and accessing wiki pages or pull request data. The server supports deployment via Docker or direct execution as a binary for integration into local AI environments.
Our verdict
With a high-risk security score of 9/100, this server is not suitable for environments requiring strict access controls. The primary security concern is the total lack of authentication mechanisms, meaning any entity with access to the configuration can use the server. Additionally, the tool lacks read-only modes, providing full write access to the configured Forgejo or Gitea instance by default. It is recommended only for isolated development or private, low-sensitivity projects.
- Supports both stdio and http communication modes
- Zero direct dependencies minimizes supply-chain surface area
- Provides comprehensive issue and release management functionality
- No authentication method implemented
- Lacks read-only operational modes
- Last code commit occurred 264 days ago
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| ChatGPT | ||||
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf |
Frequently asked questions
›What permission scopes should I grant to my Forgejo/Gitea access token?
It is recommended to grant at least repository and issue write permissions to the token for full functionality.
›Does this MCP server support multiple users simultaneously?
Yes, when run in HTTP mode without a provided token, the server operates in multi-user mode and requires clients to provide an Authorization: Bearer token header with each request.
›How can I securely manage my access token instead of putting it directly into the configuration file?
You can set the FORGEJOMCP_SERVER and FORGEJOMCP_TOKEN environment variables and then omit the --server and --token flags from your configuration.
›What is the difference between stdio and HTTP mode?
Stdio mode is recommended for local AI integrations like Claude Desktop, while HTTP mode enables remote access and multi-user setups via a web server.
Alternatives
Changelog
- FixAdd missing tool and fix milestone bug
2025-10-28
- NewUpgraded MCP SDK from v0.2.x to v0.4.0
2025-09-12
- FixMinor improvements
2025-08-14
- New
- New
- ImprovedInitial release
2025-08-05
Badge
Maintain this server? Add the live badge to your README.