Forgejo Model Context Protocol Server Reaches Version 3.0.0 for Self-Hosted Repositories
The agentic-forges project released forgejo-mcp v3.0.0, exposing Model Context Protocol endpoints for self-hosted Forgejo and Gitea code platforms. The update enables IDE agents like Claude Code, Cursor, and Codex to interface with private Git repositories without routing source code through external clouds.
Impact: Medium
Why it matters
You can now connect agentic IDEs directly to self-hosted Git instances to triage issues, inspect trees, and commit patches within your own infrastructure.
TL;DR
- 01forgejo-mcp v3.0.0 connects agentic IDEs to self-hosted Forgejo and Gitea servers via Model Context Protocol.
- 02Maintains code privacy by running repository tool calls against private infrastructure rather than SaaS platforms.
- 03Compatible with standard MCP hosts including Cursor, Claude Code, and Codex.
Model Context Protocol Integration for Self-Hosted Git
The forgejo-mcp project published release v3.0.0, expanding Model Context Protocol tooling for self-hosted code hosting platforms. The server allows agents running in Claude Code, Cursor, or Codex to interact natively with Forgejo and Gitea instances.
Developers can register the server inside their client configuration by specifying target instance URLs and personal access tokens, granting agents fine-grained tool access to issues, pull requests, and repository file structures without compromising local network boundaries.
Try it in 2 minutes
{
"mcpServers": {
"forgejo": {
"command": "npx",
"args": ["-y", "forgejo-mcp@3.0.0"],
"env": {
"FORGEJO_INSTANCE_URL": "https://forgejo.internal.net",
"FORGEJO_TOKEN": "your_api_token_here"
}
}
}
}json
✓ When to use
- When running air-gapped or private developer teams on Forgejo or Gitea.
- When deploying autonomous triage and review agents across self-hosted codebases.
✕ When NOT to use
- Do not configure on public shared workstations where environment variables can expose raw API tokens.
- Avoid using if your team relies strictly on managed GitHub or GitLab SaaS with native IDE connectors.
What to do today
- Register the forgejo-mcp server in your Claude Code or Cursor mcpServers config file.
- Generate a dedicated Forgejo API token with least-privilege repository permissions.
Sources