Tod vs Forgejo MCP

In-depth architectural comparison of the Tod 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 Tod when:

• You need dedicated capabilities in the Version Control domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: API Key required (Free / Open Source).
• You have access to required keys: ONEDEV_SERVER_URL, ONEDEV_ACCESS_TOKEN, ONEDEV_TRUST_CERTS_FILE.
• Primary tools included: Run CI/CD jobs against local changes, branches, or tags, Stream CI job logs in real time, Check out issues and pull requests with submodule handling.

Explore Tod 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.

Feature & Specification Comparison

Specification	Tod theonedev Version Control	Forgejo MCP raohwork Version Control
Summary	A MCP server for OneDev for CI/CD pipeline editing, issue workflow automation, and pull request review	An MCP server for managing your repositories on Forgejo/Gitea server.
Category & Scope	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": {
    "theonedev-tod": {
      "command": "npx",
      "args": [
        "-y",
        "theonedev-tod"
      ],
      "env": {
        "ONEDEV_SERVER_URL": "YOUR_ONEDEV_SERVER_URL_HERE",
        "ONEDEV_ACCESS_TOKEN": "YOUR_ONEDEV_ACCESS_TOKEN_HERE",
        "ONEDEV_TRUST_CERTS_FILE": "YOUR_ONEDEV_TRUST_CERTS_FILE_HERE"
      }
    }
  }
}

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

Related MCP Server Comparisons