DottedSign vs OpenMandate

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

DottedSign logoDottedSignAgreements & Coordination · Remote HTTP/SSEAutomate eSignature workflows and signing tasks via natural language commands.43FairAuth: not declared
O
OpenMandateAgreements & Coordination · Remote HTTP/SSE
MCP server for OpenMandate — open protocol for bilateral matching.38FairAuth: no auth required

Verdict: choose DottedSign for agreements & coordination work over a hosted endpoint; choose OpenMandate 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?

DottedSign logoChoose DottedSign when

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

O
Choose OpenMandate when

  • You need dedicated capabilities in the Agreements & Coordination domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: No auth required.
Explore OpenMandate

Feature & specification comparison

Rows where the two servers differ are marked.

SpecDottedSign logoDottedSign
O
OpenMandate
CategoryAgreements & CoordinationAgreements & Coordination
Quality signal43/100 · Fair38/100 · Fair
Install commandConfirmedConfirmed
TransportRemote HTTP/SSERemote HTTP/SSE
AuthNot declaredNo auth required
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars142—
Directory activity 0 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

DottedSign tools

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

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

DottedSign

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

OpenMandate

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "openmandate": {
      "command": "npx",
      "args": [
        "-y",
        "openmandate"
      ]
    }
  }
}

Frequently asked questions

DottedSign is categorized under Agreements & Coordination and uses a remote HTTP/SSE transport. OpenMandate belongs to Agreements & Coordination and uses a remote HTTP/SSE transport. Pick DottedSign for agreements & coordination work and OpenMandate 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.

DottedSign has no declared pricing — check the project's own site. OpenMandate has no declared pricing — check the project's own site. Auth: no auth required. 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 dottedsign and openmandate as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, DottedSign has a quality signal of 43/100 (Fair) with 0 views, 0 installs and 142 GitHub stars. OpenMandate has 38/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.