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.
agreement_get, agreement_list, agreement_checklist and agreement_render are reads and safe to auto-approve. Keep agreement_create behind a click, because it spends one of the three free active slots, and remember expired is final: a finished engagement is expired, never edited, and the record is kept.
| You say | Tool |
|---|---|
| Write an agreement between Anna Nowak and Brightleaf Studio: design and build of a five-page marketing site, 85.00 EUR an hour, Net 14, 14 days notice, liability capped at 8,500 EUR, England and Wales. | agreement_create |
| Run the checklist on it before I send it. | agreement_checklist |
| Mark it sent today. | agreement_update_status |
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.
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: service-agreement.mcpb
from the latest release opens as an extension, with no JSON and no terminal.
Cline reads its own config, so here it is:
The config block:
{
"mcpServers": {
"service-agreement": {
"command": "node",
"args": ["/absolute/path/to/mcp-servers/servers/service-agreement/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/service-agreementThat 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"]
}
}
}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 latest release, a clone and build, or the hosted URL.
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.
Write the transport in. Omitting type falls back to the legacy sse transport, which will not talk to this endpoint:
{
"mcpServers": {
"service-agreement": {
"type": "streamableHttp",
"url": "https://mcp.zovo.one/mcp/service-agreement",
"headers": { "Authorization": "Bearer <token>" }
}
}
}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: 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.
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.
Set the transport explicitly. Omitting type falls back to the legacy sse transport, so streamable HTTP needs "type": "streamableHttp" written in. It is the one default here that sends you debugging a server that works.
Approve the read-only ones and leave the writing ones behind a click: each entry carries an autoApprove array and a disabled flag.
MCP Service Agreement in detail · The same server in Windsurf and Claude.ai and Claude Desktop connectors · Every server in Cline · Guides · Cline docs · Buy Pro