Home · Setup · Claude Desktop

MCP Service Agreement in Claude Desktop

Service agreements for freelancers: scope, deliverables, rate, termination and liability, rendered for signing. You give it the parties, the scope of services, the deliverables, the rate and payment terms, start and end dates, a termination notice period, a liability cap and the governing jurisdiction, and it stores the agreement and returns it rendered as clean Markdown with a signature block, numbered SA-YYYY-NNNN. agreement_checklist is the before-you-send-it pass: every missing field listed, and terms whose absence cuts one way flagged neutrally, as written, for both parties - no termination clause, an uncapped liability. agreement_update_status moves the agreement exactly one step at a time, draft to sent to signed to expired, stamping date and note into its history, and a skipped or backwards step is refused naming the one step that is next. The built-in clause library covers IP assignment, mutual confidentiality, late payment interest, kill fee and revision rounds, filled with the agreement's own variables. Every render carries a one-line note that it is a template, not legal advice.

The agreement is written in the same window the negotiation happened in: agreement_create returns the rendered Markdown to paste back to the client, and agreement_checklist is run on it before sending, in the same conversation, with the directory of past engagements one question away.

What you get in Claude Desktop

The contract suite drives the nine tools over real stdio: the fourth active agreement is refused and nothing is written, expiring one frees the slot, the clause texts and HTML rendering refuse free-tier calls with the tagged upgrade link, and a draft cannot jump straight to signed. The only files written are agreements.json and counter.json.

Install it in Claude Desktop

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

One click, no JSON. Download service-agreement.mcpb from the latest release and open it. Claude Desktop installs it as an extension and runs it on the Node runtime it ships with, so neither your PATH nor your node version comes into it, and there is no file to edit. Everything below is the manual route, for when you want the entry in the config file itself.

The config block, which needs both strings absolute:

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

If node came from nvm, asdf or homebrew, use the absolute path that which node prints rather than the bare word, because a stdio server started by this app inherits a limited PATH:

"command": "/Users/you/.nvm/versions/node/v22.14.0/bin/node"

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/service-agreement

That writes servers/service-agreement/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": {
    "service-agreement": {
      "command": "npx",
      "args": ["-y", "@theluckystrike/mcp-service-agreement"]
    }
  }
}

Save, then completely quit Claude Desktop and start it again. A window reload is not enough.

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

No install: the hosted endpoint

The same server runs at https://mcp.zovo.one/mcp/service-agreement 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.

{
  "mcpServers": {
    "service-agreement": {
      "url": "https://mcp.zovo.one/mcp/service-agreement",
      "headers": { "Authorization": "Bearer <token>" }
    }
  }
}

Claude Desktop notes worth knowing first

Two documented facts decide whether the entry works: every path in claude_desktop_config.json must be absolute, and a stdio server started here inherits only a limited, platform-dependent subset of environment variables. If node came from nvm or homebrew, paste what `which node` prints instead of the bare word. The .mcpb route avoids both: Claude Desktop ships a built-in Node.js environment.

Free: Three active agreements, with reading, listing, the before-you-send checklist and Markdown rendering free and unlimited on every tier. An agreement stops counting the moment it expires, so expiring a finished engagement frees its slot. Pro is $19 once, verified offline.

Questions

Where is claude_desktop_config.json?

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json. Windows: %APPDATA%\Claude\claude_desktop_config.json. There is no published Linux path. Settings, Developer, Edit Config opens the right copy and creates it if it does not exist.

I added it and MCP Service Agreement does not appear.

In order: did you fully quit and restart, not just close the window? Is every path absolute? And is the command resolvable, given the limited environment a stdio server inherits here? If node came from nvm, paste what which node prints.

Can I install it without editing JSON?

Yes. An .mcpb bundle, the format renamed from .dxt, opens with Claude and shows an installation dialog. One you built yourself goes in through Settings, Extensions, Advanced settings, Install Extension.

Related

MCP Service Agreement in detail · The same server in Claude.ai and Claude Desktop connectors and Claude Code · Every server in Claude Desktop · Guides · Claude Desktop docs · Buy Pro