Contract Clause Library Assemble

com.bestremotetoolsPublished by bestremotetools.comv0.21.0Updated Oct 24, 2026

Assemble a contract from a searchable clause library, with variables filled in or flagged as missing

VerifiedSTDIODesktop onlyProductivity & WorkflowFiles & Storage

Overview

AI-generated overview

A local MCP server that stores reusable contract clauses and assembles them into Word or markdown drafts with variables filled in or flagged as missing.

What you can do
Save, read, update and delete reusable clauses with variables, categories, tags and jurisdiction, and list them in assembly order or by category. Search clauses with ranked matching on titles, tags, categories and bodies, with an optional jurisdiction filter. Import clauses in bulk from markdown or JSON and export the whole library to markdown or JSON. Assemble a document from clause ids or whole categories, numbering clauses, filling variables, bracketing missing facts and writing .docx or .md. List every variable a chosen set of clauses needs before assembling, and check or activate a Pro license.
When to use it
Useful when you draft the same kinds of agreements repeatedly and want an assistant to pull your own standard paragraphs, fill in deal facts and produce a first draft document instead of pasting last year's contract. Also handy for keeping a searchable, exportable library of reusable clauses on your own machine.
Requirements
Runs as a local process on the user's machine (desktop only). Install via the .mcpb bundle or build from source with Node.js and npm; the npx package is described as pending publication. An optional Pro license key is supplied through the MCP_LICENSE_KEY environment variable or by calling license_activate. No account or network access is needed.
Before you install
Assembled documents are generic templates, not legal advice, and the starter clauses have not been reviewed by a lawyer; treat output as a first draft for a qualified lawyer. Tools write files to disk and can delete clauses; existing output files are only replaced when overwrite is set. Clause data and documents stay in a local data directory, and a business profile shared with other servers in the suite may hold identity details such as an email address. Pro features are paid.

Installation

In SourceWeft

  1. Open Contract Clause Library Assemble in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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 (io.github.theluckystrike/contract-clause-library-proposal-template-docx).

[clauses demo]

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):

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

Claude Code:

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

(.cursor/mcp.json):

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:

sh
git clone https://github.com/theluckystrike/mcp-servers.git && cd mcp-serversnpm installnpm 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

ToolWhat it does
clause_addSave a reusable clause: title, body with {{variables}}, category, tags, optional jurisdiction and language
clause_getReturn one clause in full, by id or by title (a partial title matches)
clause_updateChange the text, category, tags, variables or jurisdiction. In Pro the previous text is kept as a version
clause_deleteRemove a clause. A deleted starter is not re-seeded on the next call
clause_listList every clause, in assembly order, optionally narrowed to one category
clause_searchRanked search over titles, tags, categories and bodies. A title match outranks a body mention; a term matches on a real word boundary ("fee" never matches inside "coffee"), with plain substring containment kept only as a lower-ranked fallback. The jurisdiction filter is free (citing a clause from the wrong jurisdiction is the error this prevents); the tag filter is Pro and is skipped, never refusing the search
clause_importBulk-load from a markdown file (## Title, category: / tags: lines, blank line, body) or from JSON (Pro). Only short, field-shaped lines right after the title are read as metadata, so body prose that happens to open with a word like "note:" is kept as body, not swallowed
clause_exportWrite the whole library to markdown (free) or JSON (Pro). An existing destination is never replaced unless you pass overwrite: true
contract_assembleBuild a document from clause ids or whole categories: orders the clauses, numbers them, fills the variables, brackets what is missing, prepends the not-legal-advice line, writes .docx or .md. An existing out_path is never replaced unless you pass overwrite: true
variables_listEvery {{variable}} a selection of clauses needs, and which clause needs it, before you assemble
license_statusShow free or Pro mode
license_activateActivate a Pro key (verified offline)

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

CategoryClauses
scopeScope of Work, Revisions, Acceptance of Deliverables, Change Requests
paymentPayment Terms, Late Payment, Kill Fee, Rush Fee
expensesExpenses
ipIntellectual Property Assignment, Portfolio and Credit
confidentialityConfidentiality
dataData Protection
termTermination
liabilityLimitation of Liability
warrantyWarranty Disclaimer
disputesDispute Resolution
generalGoverning Law, Force Majeure, Independent Contractor, Non-Solicitation, Notices, Entire Agreement, Severability, Assignment

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

You sayTool
"What clauses do I have about late payment?"clause_search
"Save this as a clause called Retainer, category payment."clause_add
"Draft a service agreement for Beta Corp: scope, payment, late fees, IP, termination. Fee 4,500 EUR, 14-day terms."contract_assemble
"What do I still need to fill in for those five clauses?"variables_list
"Import my old clauses from clauses.md."clause_import
"Export the whole library so I can keep a copy."clause_export

Free vs Pro

FreePro
25 starter clausesyesyes
Your own clauses10unlimited
Ranked search, category filteryesyes
Filter by jurisdiction or tagnoyes
Clauses per assembled document8unlimited
Markdown import and exportyesyes
JSON import and exportnoyes
Clause version history on clause_updatenoyes

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: [email protected]

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:

Source: servers/clauses/README.md at commit 1bd9d69

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.21.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts