How do I install Contract Ops?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Contract Ops need an API key?

No required environment variable is listed on this record.

What transport does Contract Ops use?

Contract Ops runs locally over stdio.

When was Contract Ops last checked?

Last checked 2026-11-09. One MCP server for the contract-ops suite: all nine local-first CLIs as agent tools.

Contract Ops MCP server

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

npx -y [email protected]

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1claude mcp add io.github.drbaher-contract-ops-mcp -- npx -y contract-ops-mcp@0.3.0

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.drbaher-contract-ops-mcp": {4      "command": "npx",5      "args": [6        "-y",7        "[email protected]"8      ]9    }10  }11}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version: 0.3.0
Last checked

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

contract-ops-mcp

One MCP server for the whole contract-ops CLI suite — wire it up once and an agent (Claude, Cursor, Codex, …) gets all nine local-first CLIs as tools: extract, draft, lint, compare, convert, review, and the template + signed-contract vaults. Signing stays human-gated.

Run this

// e.g. Claude Desktop / Cursor MCP config
{
  "mcpServers": {
    "contract-ops": { "command": "npx", "args": ["-y", "contract-ops-mcp"] }
  }
}

The CLIs themselves must be installed (the server shells out to them). Fastest way to get all nine:

curl -fsSL https://cli.drbaher.com/install.sh | sh     # local
# …or run the server + CLIs in one container: ghcr.io/drbaher/contract-ops

Call suite_status any time to see which CLIs are present and how to install any that aren't.

Prefer a ready-made agent? contract-ops-agent is a terminal agent that already wraps this server in an enclosure — the model's only tools are the contract-ops tools, no shell/filesystem/signing by construction. Bring your own model (Claude, OpenAI, or any OpenAI-compatible endpoint): npm i -g contract-ops-agent.

Tools

Curated, ergonomic tools (typed inputs, JSON out) for the common operations, plus two escape hatches for the long tail:

Tool	What it does
`extract_contract`	Any contract (.md/.txt/.html/.docx/.pdf) → structured JSON (parties, dates, clauses, …)
`lint_contract`	Internal-consistency findings (placeholders, broken refs, defined-term/numbering/date defects)
`compare_versions`	Clause-aware drift between two versions (exit 0 clean · 2 substantive · 3 cosmetic · 4 moved)
`fill_template`	Fill a template's placeholders with typed params (deterministic)
`convert_to_pdf`	DOCX → PDF (needs a PDF backend, e.g. LibreOffice)
`review_nda`	Score an NDA against a house playbook, with evidence
`template_vault_find` / `template_vault_get`	Search / resolve versioned templates (read-only)
`contract_vault_query` / `contract_vault_due` / `contract_vault_risk`	Query the signed-contract register; project renewal/notice deadlines; renewal-exposure (read-only)
`verify_signature` / `verify_receipt` / `audit_show`	Verify a signed PDF / a receipt bundle / walk the audit log (read-only)
`catalog(cli)`	Return any CLI's full `--catalog json` — discover the long tail
`run(cli, args)`	Escape hatch: run any suite CLI with raw args (no shell)
`suite_status`	Which CLIs are installed (+ versions) and how to install the rest

The curated set and catalog/run are discovery-driven — they ride the suite's uniform --catalog json contract, so they stay in sync as the CLIs evolve.

Safety

Signing is human-gated. Only sign-cli's read/verify operations are exposed (verify_signature, verify_receipt, audit_show) — never request-create or sign. This is enforced: the run/catalog escape hatches reject any sign subcommand outside a read-only allowlist, so request-create/send/sign/approve can't be reached here. Those stay behind sign-cli's own MCP server with its per-signer approval tokens, so this server can't become an unguarded signing path.
Filesystem lockdown. File-path arguments to the curated tools are confined to CONTRACT_OPS_MCP_BASE_DIR (default: the working directory). Set it to widen the sandbox.
No shell. CLIs are invoked with execFile (no shell interpolation).

License

MIT. Part of the contract-ops CLI suite. See AGENTS.md for the agent contract.

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Contract Ops?

Does Contract Ops need an API key?

What transport does Contract Ops use?

When was Contract Ops last checked?

Documentation

contract-ops-mcp

Run this

Tools

Safety

License