Schelling Protocol vs Zopaf

In-depth architectural comparison of the Schelling Protocol and Zopaf 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 Schelling Protocol when:

• You need dedicated capabilities in the Agreements & Coordination domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Schelling Protocol Details

Choose Zopaf when:

• You need dedicated capabilities in the Agreements & Coordination domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: create_session, add_issue, set_issue_range.

Explore Zopaf Details

Feature & Specification Comparison

Specification	Schelling Protocol Agreements & Coordination	Zopaf Agreements & Coordination
Summary	Universal coordination protocol for AI agents. Discovery, matching, and negotiation.	Negotiation math engine. Pareto frontier, counteroffer generation, zero LLM tokens.
Category & Scope	Agreements & Coordination	Agreements & Coordination

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": {
    "schelling-protocol": {
      "command": "npx",
      "args": [
        "-y",
        "create-schelling-agent"
      ]
    }
  }
}

{
  "mcpServers": {
    "zopaf": {
      "url": "https://zopaf-mcp-production.up.railway.app/mcp"
    }
  }
}

Related MCP Server Comparisons