Home · Setup · Cline

MCP Clause Library in Cline

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.

Put clause_search, clause_list, clause_get and variables_list in autoApprove and keep clause_delete out of it: a deleted starter clause is not re-seeded on the next call.

What you get in Cline

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 Cline

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

Scope	Path
Cline CLI	`~/.cline/mcp.json`
The editor extension	`opened from the Cline panel, not by path; the documentation deliberately calls it the MCP settings JSON used by the extension`

If you also run Claude Desktop, the shortest path there is one click: clauses.mcpb from the bundle catalog opens as an extension, with no JSON and no terminal. Cline reads its own config, so here it is:

The config block:

{
  "mcpServers": {
    "clauses": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-servers/servers/clauses/dist/index.js"],
      "disabled": false,
      "autoApprove": []
    }
  }
}

The node command above wants a built file. From a clone, once:

git clone https://github.com/theluckystrike/mcp-servers.git
cd mcp-servers && npm install
npm run build -w packages/mcp-license -w servers/clauses

That writes servers/clauses/dist/index.js, and its absolute path is the one argument the config needs.

The npm packages are not published yet, so the form below returns a 404 today. It is here because it is what the entry becomes the day the publish lands, with nothing else changed:

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

No full-app restart. The MCP settings actions include restarting an unresponsive server if its tools do not appear.

Nothing is published to npm yet, so the working install paths are the ones above: the .mcpb bundle from the bundle catalog, a clone and build, or the hosted URL.

No install: the hosted endpoint

The same server runs at https://mcp.zovo.one/mcp/clauses over MCP streamable HTTP, no install. Mint a free token with curl https://mcp.zovo.one/mcp/token, or use a Pro key. It has no filesystem, so a file comes back as a one-hour download link.

Write the transport in. Omitting type falls back to the legacy sse transport, which will not talk to this endpoint:

{
  "mcpServers": {
    "clauses": {
      "type": "streamableHttp",
      "url": "https://mcp.zovo.one/mcp/clauses",
      "headers": { "Authorization": "Bearer <token>" }
    }
  }
}

Cline notes worth knowing first

Cline is the one client here with an unsafe transport default. `type` selects it, and omitting `type` falls back to the legacy sse transport, so a streamable HTTP endpoint needs it written in or you will debug a server that is fine. Local entries carry "disabled" and an "autoApprove" array.

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

Where does the config live?

The CLI reads ~/.cline/mcp.json. For the extension, do not hunt for a path: MCP Servers icon, Configure tab, Configure MCP Servers. cline mcp opens a wizard, and cline config mcp --json is the non-interactive form.

The hosted endpoint will not connect.

Set the transport explicitly. Omitting type falls back to the legacy sse transport, so streamable HTTP needs "type": "streamableHttp" written in.

Should I auto-approve MCP Clause Library's tools?

Approve the read-only ones and leave the writing ones behind a click: each entry carries an autoApprove array and a disabled flag.

MCP Clause Library in detail · The same server in Windsurf and Claude.ai and Claude Desktop connectors · Every server in Cline · Guides · Cline docs · Buy Pro

Related guides & tools

Assemble a contract from your own clause library, in chat · MCP Service Agreement: stop copying a rotting contract template off the internet