Buyer problem: you are about to start client work and you need the engagement on paper. The template you copy off the internet is old, half-finished, and full of fields you do not fill in because the last person did not either. You are not a lawyer, so you send it anyway and hope. This server writes the agreement from what you tell it, checks it for missing fields and one-sided gaps, and renders it ready for signing.
You describe the engagement in plain language: the parties, the scope of services, the deliverables,
the rate in whole cents with its unit, the payment terms, start and end dates, a termination notice
period, a liability cap and the governing jurisdiction. agreement_create stores it and
returns it rendered as clean Markdown with a signature block, numbered SA-YYYY-NNNN.
Two tools do the before-you-send work. agreement_checklist lists the missing fields and
flags one-sided gaps neutrally, so it does not call your terms bad, it points at the blank and the
asymmetry. agreement_update_status moves the agreement exactly one step at a time:
draft, sent, signed, expired, stamping a date and note into its history, and a skipped step is refused,
so a draft cannot leap to signed by accident.
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.
One click, no JSON. Download service-agreement.mcpb from the
latest release and open it in Claude Desktop. It runs 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 line:
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/service-agreement
claude mcp add --scope user service-agreement -- node /absolute/path/to/mcp-servers/servers/service-agreement/dist/index.jsClaude 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": {
"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 service-agreement -- npx -y @theluckystrike/mcp-service-agreementWhichever path you take, there is no account, no API key and no login step. It writes to
~/.local/share/mcp-servers/service-agreement/.
These are the sentences you type:
Write an agreement. "Write an agreement between Anna Nowak and Brightleaf Studio: design and build of a five-page site, 85.00 EUR an hour, Net 14, 14 days notice, capped at 8,500 EUR, England and Wales." One call, one rendered agreement with a signature block.
Check it before sending. "Run the checklist on it before I send it." Missing fields and one-sided gaps, listed.
Advance its status. "Mark it sent today." The status moves one step to sent with a date stamp.
Copying a template means filling in whatever the template happens to ask for and missing the rest. This server asks for the specific set of fields a service agreement needs and refuses to let one leak past unchecked: the checklist is the part a Word document does not give you, and the one-step status machine means there is always a record of where each agreement is. It will not replace a lawyer, and it says so on every render, but it replaces the copy-and-hope template.
There is no direct MCP competitor: an npm registry probe for service-agreement, service-contract, freelance contract, agreement and contract template found no other server that holds and renders a service agreement.
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 ($19 once, lifetime) opens unlimited active agreements, the full clause texts with the agreement's variables filled in, and print-ready HTML rendering. The full comparison is in free versus Pro. Product page: MCP Service Agreement. There are 41 of these MCP servers in total; one lifetime key covering all of them, this one included, is $39.
Claude.ai, the Claude Desktop connector dialog and several IDE pickers take a remote URL and nothing
else. mcp/connect mints a token and prints a ready-to-paste URL for every
hosted server, including this one at https://mcp.zovo.one/mcp/service-agreement.
MCP Service Agreement writes a scope, deliverables, rate, payment terms, termination notice, liability cap and governing jurisdiction into a rendered agreement numbered SA-YYYY-NNNN, and checks it for missing fields and one-sided gaps before you send it. Three active agreements are free; Pro is $19 once for unlimited.
No. Every render carries a one-line note that it is a template, not legal advice. It produces the document and the checklist; a lawyer reviews the important ones.
Yes. agreement_checklist lists the missing fields and flags one-sided gaps neutrally. It is a before-you-send pass, not a grading.
Yes. https://mcp.zovo.one/mcp/service-agreement answers over streamable HTTP. mcp/connect mints a free anonymous token and prints the ready URL.
All MCP servers and prices · All guides · Buy the bundle $39