Gitea MCP vs Forgejo MCP

In-depth architectural comparison of the Gitea MCP and Forgejo MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Gitea MCP when:

• You need dedicated capabilities in the Version Control domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• You have access to required keys: GITEA_URL, GITEA_TOKEN.
• Primary tools included: Issue and comment management, Repository, branch, label, and milestone queries, Pull request creation, review comments, and merging.

Explore Gitea MCP Details

Choose Forgejo MCP when:

• You need dedicated capabilities in the Version Control domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: API Key required (Free / Open Source).
• You have access to required keys: FORGEJOMCP_SERVER, FORGEJOMCP_TOKEN.
• Primary tools included: .

Feature & Specification Comparison

Specification	Gitea MCP Version Control	Forgejo MCP raohwork Version Control
Summary	Model Context Protocol server for Gitea (and Forgejo, Codeberg).	An MCP server for managing your repositories on Forgejo/Gitea server.
Category & Scope	Version Control	Version Control

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "gitea-mcp": {
      "command": "uvx",
      "args": [
        "gitea-mcp"
      ],
      "env": {
        "GITEA_URL": "YOUR_GITEA_URL_HERE",
        "GITEA_TOKEN": "YOUR_GITEA_TOKEN_HERE"
      }
    }
  }
}

{
  "mcpServers": {
    "raohwork-forgejo-mcp": {
      "url": "http://localhost:8080/sse"
    }
  }
}

Related MCP Server Comparisons