Gread vs Reviewgate

In-depth architectural comparison of the Gread and Reviewgate 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 Gread 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).

Explore Gread Details

Choose Reviewgate when:

• You need dedicated capabilities in the Version Control domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Reviewgate Details

Feature & Specification Comparison

Specification	Gread Version Control	Reviewgate ReviewGate Version Control
Summary	An MCP server that gives your AI access to the source code and docs of all public github repos	Code review against the rules your team actually wrote, not generic best practice. A cheap generator finds problems, an independent judge refutes them against full files, so the noise stays down. Two tools for the agent loop (getteamrules, reviewchanges), plus a pre-push gate and a bot on GitLab/GitHub pull requests. Single binary, no Node or Docker; bring your own model key.
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": {
    "gread": {
      "command": "npx",
      "args": [
        "-y",
        "skills"
      ]
    }
  }
}

{
  "mcpServers": {
    "reviewgate-reviewgate": {
      "url": "https://reviewgate.dev**"
    }
  }
}

Related MCP Server Comparisons