One MCP server for the contract-ops suite: all nine local-first CLIs as agent tools.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag β we're steadily working through the catalog.
π‘ Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows)
Inspect callable tools, capabilities, and parameters exposed to AI agents by Contract Ops Mcp.
extract_contractAny contract (.md/.txt/.html/.docx/.pdf) β structured JSON (parties, dates, clauses, β¦)
lint_contractInternal-consistency findings (placeholders, broken refs, defined-term/numbering/date defects)
compare_versionsClause-aware drift between two versions (exit 0 clean Β· 2 substantive Β· 3 cosmetic Β· 4 moved)
fill_templateFill a template's placeholders with typed params (deterministic)
convert_to_pdfDOCX β PDF (needs a PDF backend, e.g. LibreOffice)
review_ndaScore an NDA against a house playbook, with evidence
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.
The CLIs themselves must be installed (the server shells out to them). Fastest way to get all nine:
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.
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.
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.CONTRACT_OPS_MCP_BASE_DIR (default: the working directory). Set it to widen the sandbox.execFile (no shell interpolation).MIT. Part of the contract-ops CLI suite. See AGENTS.md for the agent contract.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/contract-ops-mcp)<a href="https://allmcps.com/mcp/contract-ops-mcp"><img src="https://allmcps.com/api/badge/contract-ops-mcp?style=directory" alt="Contract Ops Mcp on AllMCPs" /></a>