Home · Setup · Claude Code

MCP Clause Library in Claude Code

Reusable contract clauses, searched and assembled into Word. It ships 25 generic freelance clauses across 11 categories, each holding {{variables}}, lets you add and rank-search your own, lists which variables a selection still needs, and assembles the picked clauses into a numbered .docx or markdown document that opens with a not-legal-advice line.

Keep the library in one data directory and the assembled drafts out of your repositories. The one command worth running first is variables_list, because it names every fact the document needs before the document exists.

What you get in Claude Code

You say	Tool
What clauses do I have about late payment?	`clause_search`
What do I still need to fill in for those five clauses?	`variables_list`
Draft a service agreement for Beta Corp: scope, payment, IP, termination. 4,500 EUR, 14 day terms.	`contract_assemble`

A variable you do not supply is never guessed and never blanked: it is printed as a visible bracketed prompt such as [late fee percent], so the unfinished part of the draft is the part you can see. Nothing here has been reviewed by a lawyer in any jurisdiction.

Install it in Claude Code

The file is .mcp.json, and the key inside it is mcpServers.

Scope	Path
local (default)	`~/.claude.json, this project only`
project	`.mcp.json at the repository root`
user	`~/.claude.json, every project`

claude mcp add clauses -- npx -y @theluckystrike/mcp-clauses
claude mcp list    # health-check it before the first prompt

# or --scope project, committed to .mcp.json for the team

No restart. The entry is picked up in the next session, and `/mcp` reconnects one on demand.

The npm publish of @theluckystrike/mcp-clauses is pending; until then use the .mcpb bundle or a clone and build from the latest release.

No install: the hosted endpoint

There is no hosted endpoint for this one yet. MCP Clause Library runs locally over stdio with the config above, which is also the only form in which it reads and writes files on your own disk. Three of the servers in this collection are served at https://mcp.zovo.one/mcp/<name> over MCP streamable HTTP: time-tracker, price-tracker and invoice.

Claude Code notes worth knowing first

The `--` is load-bearing: it separates Claude Code's own options, such as --transport, --env and --scope, from the command that runs the server. And the default scope is local, private to you and to the directory you ran it in, so adding it in the wrong folder leaves the tools absent with no error at all.

Free: the 25 starters plus 10 of your own, ranked search, up to 8 clauses per document, markdown import and export. Pro is $19 once, verified offline.

Questions

Which scope should I use for MCP Clause Library?

Local, the default, writes ~/.claude.json and is private to you and that directory. --scope project writes .mcp.json at the repository root, shared through version control. --scope user loads it everywhere.

Why did my first prompt ignore the server?

Measured, not documented: of three fresh projects, one first prompt made zero tool calls although initialize answered in 1.05 seconds. Run claude mcp list once first: it prints Connected, and the next run used the tool.

Can I use MCP Clause Library without installing anything?

Not yet. MCP Clause Library runs locally over stdio, which is also how it reads and writes files on your disk. The hosted endpoints at https://mcp.zovo.one/mcp currently cover time-tracker, price-tracker and invoice.

MCP Clause Library in detail · The same server in Claude Desktop and Cursor · Every server in Claude Code · Guides · Claude Code docs