Home · Setup · VS Code

MCP Clause Library in VS 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.

Assemble to markdown first and read it in the editor. The .docx is the version you send; the markdown is the version you can review line by line before anyone signs it.

What you get in VS 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 VS Code

The file is .vscode/mcp.json, and the key inside it is servers.

Scope	Path
This workspace	`<workspace>/.vscode/mcp.json`
Every workspace	`the user profile mcp.json, opened by the MCP: Open User Configuration command`

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. VS Code reads its own config, so here it is:

// .vscode/mcp.json  (the key is "servers")
{
  "servers": {
    "clauses": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-servers/servers/clauses/dist/index.js"]
    }
  }
}

Or from a terminal:

code --add-mcp '{"name":"clauses","command":"node","args":["/absolute/path/to/mcp-servers/servers/clauses/dist/index.js"]}'

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:

code --add-mcp '{"name":"clauses","command":"npx","args":["-y","@theluckystrike/mcp-clauses"]}'

VS Code asks you to confirm you trust the server and its capabilities before it starts. Nothing runs until you answer.

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.

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

VS Code notes worth knowing first

The top-level key is "servers", not "mcpServers". A config pasted from a Claude Desktop or Cursor README parses cleanly, contributes no servers, and gives you no error to read, which makes it the most expensive one-word mistake here. Alongside it an "inputs" array holds secrets. The newer Agent Host reads a workspace .mcp.json instead.

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

Why does my mcp.json do nothing?

The key is servers, not mcpServers. A config copied from a Claude Desktop README parses cleanly and contributes nothing. Rename it. On the newer Agent Host, use a workspace .mcp.json instead.

Do I have to edit the file at all?

No. code --add-mcp takes the server object on the command line, and MCP: Add Server in the palette asks whether the target is Workspace or Global.

Where do the MCP Clause Library tools show up?

In Chat, behind the tools picker, once the server has started. Adding or changing one raises a prompt asking you to confirm you trust it; if the picker is empty, that prompt is usually still waiting.

MCP Clause Library in detail · The same server in Cursor and Windsurf · Every server in VS Code · Guides · VS Code 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