Home · Guides

NDA and confidentiality agreements from a clause library

A non-disclosure agreement is mostly standard clauses with your names and a term dropped in. An MCP Clause Library keeps those clauses so you assemble one by describing the deal: "an NDA for Acme, mutual, twelve months, covering our pricing and roadmap".

A one-sided NDA or a mutual one

State the direction and the server picks the clauses: a one-way NDA keeps the language to the disclosing side, a mutual one mirrors the obligations, and both take the names, a term and the scope of the confidential information from your sentence. Because the source is a library, a revised term or a narrowed scope is a re-worded clause rather than a whole new document, which is what makes the round trip useful when a counterpart sends back edits.

From clauses to a document in the same chat

NDAs get signed as documents, not as chat transcripts. When the clause set is agreed, the contract engine hands the structured terms to MCP Service Agreement, which renders the final agreement so you can send, print or e-sign it without moving to a separate editor. The clause set and the rendered document both live in the same conversation.

One click, with no JSON. Download clauses.mcpb and service-agreement.mcpb from the latest release and open them in Claude Desktop. They run on the Node runtime Claude Desktop ships with, so your own PATH and node version never come into it.

Or a URL, with nothing installed. /mcp/connect mints a free anonymous token and prints the ready lines:

claude mcp add --transport http clauses           https://mcp.zovo.one/mcp/clauses/t/<token>
claude mcp add --transport http service-agreement https://mcp.zovo.one/mcp/service-agreement/t/<token>

Or from a clone, for a client with no bundle installer. Build once, then point the client at the built file:

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

claude mcp add --scope user clauses           -- node /absolute/path/to/mcp-servers/servers/clauses/dist/index.js
claude mcp add --scope user service-agreement -- node /absolute/path/to/mcp-servers/servers/service-agreement/dist/index.js

Claude Desktop, Cursor, Windsurf and Cline take the same two strings as JSON, in claude_desktop_config.json or the client's own MCP config file:

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

The npm packages are not published yet, so the npx form below returns a 404 today. It is kept because it is what that config becomes the day the publish lands, with nothing else changed; installing these servers when npx does not work yet has the whole picture.

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

Questions

Does this write legal advice?

No. It assembles the standard clauses you pick from a library. For any deal with real money or exposure, review the result with a lawyer before signing, the same as you would any template.

Can I mix a one-way NDA with a mutual agreement?

Each agreement is assembled from a chosen direction; describe the deal and the server picks the matching clause set. Revising a term re-words that clause rather than rebuilding the whole document.

Do I need a docs editor installed?

No. The service-agreement server renders the final document directly, so the NDA is ready to send or e-sign from the same chat.

All MCP servers and prices · All guides · Buy the bundle $39