Creativity · MCP — server
MCP Gitea Server
Gitea (and its fork Forgejo) is the most popular self-hosted Git forge for teams avoiding GitHub lock-in. The MCP Gitea Server lets Claude talk to a Gitea instance — list issues, open PRs, comment on diffs, manage releases — all without leaving the chat.
MCP facts
- Kind
- server
- Ecosystem
- anthropic-mcp
- Language
- Go
- Transports
- stdio
Capabilities
- Tools: list_repos, list_issues, open_pr, comment_on_pr, create_release
- Personal Access Token with scoped permissions
- Works with Gitea 1.20+ and Forgejo
Install
go install github.com/community/mcp-gitea@latest Configuration
{
"mcpServers": {
"gitea": {
"command": "mcp-gitea",
"env": {
"GITEA_URL": "https://git.example.com",
"GITEA_TOKEN": "<pat>"
}
}
}
} Frequently asked questions
Does it work with Forgejo?
Yes — Forgejo remains Gitea-API-compatible. Point GITEA_URL at your Forgejo host.
How does it compare to the GitHub MCP server?
Same mental model — repos, issues, PRs — but against your own infrastructure. Ideal for teams with compliance or cost constraints.
Webhooks?
The MCP server doesn't host webhooks; that's for a separate service. You can use its tools to set up webhook configs programmatically.
Sources
- Gitea API Documentation — accessed 2026-04-20
- Model Context Protocol — accessed 2026-04-20