Glossary Terms Definitions Library

mcp-clauses

Say "draft a service agreement for Beta Corp, 4,500 EUR, 14-day terms" and get a real .docx built from your own clause library. This MCP server keeps the contract and proposal paragraphs you reuse, scope, payment terms, late fees, IP assignment, confidentiality, termination, liability cap and twenty more, as searchable clauses with {{variables}} in them. It ships with 25 generic freelance starters, finds the right ones by ranked search, fills the variables you supply, leaves every fact you did not supply as a visible bracketed prompt like [late fee percent], and writes the assembled document to Word or markdown. Every document opens with the line that it is a generic template and not legal advice. Everything runs locally: no upload, no account, no native dependency.

In the [official MCP Registry](https://registry.modelcontextprotocol.io/v0.1/servers/io.github.theluckystrike%2Fcontract-clause-library-proposal-template-docx/versions/latest) (io.github.theluckystrike/contract-clause-library-proposal-template-docx).

Stop pasting last year's contract into a new file and hoping you changed every name.

60-second install

npm publish for @theluckystrike/mcp-clauses is pending. Until then, the .mcpb one-click bundle or a clone+build is the working path, both are verified below.

One-click (.mcpb): download clauses.mcpb from the latest release and double-click it in Claude Desktop: https://github.com/theluckystrike/mcp-servers/releases/latest

(claude_desktop_config.json):

{

"mcpServers": { "clauses": { "command": "npx", "args": ["-y", "@theluckystrike/mcp-clauses"] } } }

Claude Code:

claude mcp add clauses -- npx -y @theluckystrike/mcp-clauses

(.cursor/mcp.json):

{

"mcpServers": { "clauses": { "command": "npx", "args": ["-y", "@theluckystrike/mcp-clauses"] } } }

The npx form above starts working the moment the package is published. Until then, use the .mcpb bundle above, or build from source with exactly these three commands:

git clone https://github.com/theluckystrike/mcp-servers.git && cd mcp-servers

npm install npm run build -w packages/mcp-license -w servers/docx -w servers/clauses

Then point your client's command at node with one arg: the absolute path to servers/clauses/dist/index.js.

To run in Pro mode set MCP_LICENSE_KEY in the same config block, or call license_activate once with your key.

This is not legal advice

The 25 starter clauses are generic freelance templates written in plain language. They are not drafted for your country, your trade or your deal, and no clause here has been reviewed by a lawyer. Every starter carries the note generic template, not legal advice, and every document contract_assemble writes opens with the same line. Treat the output as a first draft to take to a qualified lawyer, not as a contract to sign.

Tools

Resource: clauses://categories returns every category in the library with its clause count, in assembly order. Prompt: draft_contract picks clauses that fit an engagement, assembles them, and reports the facts still missing.

The 25 starter clauses

They use variables such as {{client}}, {{contractor}}, {{project}}, {{fee}}, {{currency}}, {{payment_days}}, {{deposit_percent}}, {{late_fee_percent}}, {{liability_cap}}, {{notice_days}}, {{revision_rounds}}, {{acceptance_days}}, {{kill_fee_percent}}, {{rush_fee_percent}} and {{jurisdiction}}. Call variables_list with the clauses you picked to see exactly which ones your document needs.

What you can say

Free vs Pro

Get Pro: https://mcp.zovo.one/buy/clauses, $19 one-time, or $39 for the whole collection.

Pairs with

• mcp-docx, the document engine this server assembles through. Install both and the same conversation that picks clauses can also write the covering letter and read the client's own .docx back.
• mcp-invoice, the payment terms you agreed in the contract are the terms you bill on.
• mcp-recurring, once a retainer clause is signed, the schedule that raises its invoices.

Privacy

Every clause and every assembled document stays on your machine, in ${XDG_DATA_HOME:-~/.local/share}/mcp-servers/clauses/. The server makes no network calls at all. Your licence key is verified offline.

Built by theluckystrike. Support: support@zovo.one

One business profile for the whole suite

Your identity is stored once, at ${XDG_DATA_HOME:-~/.local/share}/mcp-servers/profile/business.json, and every server in the suite reads it: the invoice issuer, the docx letterhead, the recurring issuer, expense-tracker's default VAT rate, time-tracker's and timezone's home zone, and the resume and contract letterheads. Set it once with business_set (invoice or docx) - you never repeat it anywhere else. An email address is only ever taken from that profile or from an explicit argument; when none is stored, documents show [add: email] and the tool says so rather than letting anyone improvise an address.

Use these docs as an MCP server

Any MCP client (Claude, Cursor, Windsurf, VS Code) can read this repository's documentation directly via GitMCP - no install:

• Docs MCP URL: https://gitmcp.io/theluckystrike/mcp-clauses