Schelling Protocol vs DottedSign

A side-by-side look at the Schelling Protocol and DottedSign MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Schelling Protocol logoSchelling ProtocolAgreements & Coordination · Local subprocess (stdio)Universal coordination protocol for AI agents. Discovery, matching, and negotiation.37FairAuth: not declaredDottedSign logoDottedSignAgreements & Coordination · Remote HTTP/SSEAutomate eSignature workflows and signing tasks via natural language commands.44FairAuth: not declared

Verdict: choose Schelling Protocol for agreements & coordination work as a local process; choose DottedSign for agreements & coordination over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Schelling Protocol logoChoose Schelling Protocol when

  • You need dedicated capabilities in the Agreements & Coordination domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: SCHELLING_SERVER_URL.
Explore Schelling Protocol

DottedSign logoChoose DottedSign when

  • You need dedicated capabilities in the Agreements & Coordination domain.
  • You prefer a remote HTTP/SSE transport.
Explore DottedSign

Feature & specification comparison

Rows where the two servers differ are marked.

SpecSchelling Protocol logoSchelling ProtocolDottedSign logoDottedSign
CategoryAgreements & CoordinationAgreements & Coordination
Quality signal37/100 · Fair44/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsSCHELLING_SERVER_URLNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars5142
Directory activity 3 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Schelling Protocol tools

No tool names declared yet. Check the project README from the listing page.

DottedSign tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Schelling Protocol

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "schelling-protocol": {
      "command": "npx",
      "args": [
        "-y",
        "create-schelling-agent"
      ],
      "env": {
        "SCHELLING_SERVER_URL": "YOUR_SCHELLING_SERVER_URL_HERE"
      }
    }
  }
}

DottedSign

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "dottedsign": {
      "url": "https://mcp.dottedsign.com/dottedsign-api/mcp"
    }
  }
}

Frequently asked questions

Schelling Protocol is categorized under Agreements & Coordination and uses a local stdio subprocess. DottedSign belongs to Agreements & Coordination and uses a remote HTTP/SSE transport. Pick Schelling Protocol for agreements & coordination work and DottedSign for agreements & coordination.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Schelling Protocol has no declared pricing — check the project's own site. DottedSign has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add schelling-protocol and dottedsign as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Schelling Protocol has a quality signal of 37/100 (Fair) with 3 views, 0 installs and 5 GitHub stars. DottedSign has 44/100 (Fair) with 0 views, 0 installs and 142 GitHub stars.