Open Agreements vs Nexus Legal MCP

In-depth architectural comparison of the Open Agreements and Nexus Legal MCP 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 Open Agreements when:

• You need dedicated capabilities in the Legal domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: Standard agreement template filling, MCP and local CLI workflows, DOCX rendering.

Explore Open Agreements Details

Choose Nexus Legal MCP when:

• You need dedicated capabilities in the Legal domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: API Key required (Paid Service).
• You have access to required keys: NEXUS_API_KEY.
• Primary tools included: ISO 31000 legal analysis and audit workflows, Monte Carlo litigation scenario simulation, Multi-jurisdiction case-law and legislation search.

Feature & Specification Comparison

Specification	Open Agreements open-agreements Legal	Nexus Legal MCP djtellado Legal
Summary
Category & Scope	Legal	Legal
Quality signal

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": {
    "open-agreements-open-agreements": {
      "command": "npx",
      "args": [
        "-y",
        "open-agreements-open-agreements"
      ]
    }
  }
}

{
  "mcpServers": {
    "djtellado-nexus-legal-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@nexus-legal/mcp"
      ],
      "env": {
        "NEXUS_API_KEY": "YOUR_NEXUS_API_KEY_HERE"
      }
    }
  }
}

Related MCP Server Comparisons