What is the key difference between Gread and Relayer?

Gread belongs to the Version Control category with local stdio execution, while Relayer belongs to the Version Control category with cloud HTTP/SSE execution.

How do I install Gread or Relayer in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Gread and Relayer free or paid?

Gread operates under a Free / Open Source model (No auth required). Relayer operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Gread lists 0 tools with 0 views and 61 GitHub stars. Relayer lists 0 tools with 0 views and 0 GitHub stars.

Can I use both Gread and Relayer together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Gread vs Relayer

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

At a Glance & Executive Verdict

Gread

Version Control · Local stdio

Quality: 48/100 (Fair) | Auth: No auth required

Relayer

Version Control · Remote HTTP/SSE

Quality: 25/100 (Emerging) | Auth: No auth required

Verdict Summary: Choose Gread if you need specialized Version Control tools running via a local process. Choose Relayer if your workspace requires Version Control integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.

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 Relayer 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 Relayer Details

Feature & Specification Comparison

Specification	Gread Version Control	R Relayer Version Control
Summary	An MCP server that gives your AI access to the source code and docs of all public github repos	Conversationally set up & manage an XNS Relayer over stdio: install, claim, VPD, S3, backups.
Category & Scope	Version Control	Version Control
Quality signal

Tools & Capabilities Breakdown

Gread Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

Relayer Tools (0)

No explicit tool names declared in metadata yet. Check project README on main listing page.

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).

Gread Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "gread": {
      "command": "npx",
      "args": [
        "-y",
        "skills"
      ]
    }
  }
}

Relayer Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "relayer": {
      "url": "https://gitlab.com/scpcorp/relayer-mcp"
    }
  }
}

Frequently Asked Questions

Gread is categorized under Version Control and uses a local stdio subprocess. In contrast, Relayer belongs to Version Control using remote streaming HTTP/SSE transport. Select Gread when you need capabilities focused on version control and Relayer when you require tools for version control.

More alternatives to Gread More alternatives to Relayer Version Control category hub