One MCP server for the contract-ops suite: all nine local-first CLIs as agent tools.
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.
// 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.
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.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y contract-ops-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-drbaher-contract-ops-mcp": {
"command": "npx",
"args": [
"-y",
"contract-ops-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencecontract-ops-mcpnpmio.github.DrBaher/contract-ops-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.