mcp-service-agreement is a local MCP server for creating, storing, checking, and rendering freelance service agreements, with a free tier and Pro unlocks.
Create an agreement with parties, scope, deliverables, rate/payment terms, dates, termination notice, liability cap, jurisdiction, and optional library clauses; it stores it and returns Markdown with an SA number.
Read one agreement by SA number or client name, including status history.
List agreements newest first and filter by status or client.
Move an agreement exactly one status step: draft, sent, signed, or expired, with date and note history.
Browse the built-in clause library: IP assignment, confidentiality, late payment interest, kill fee, and revision rounds; Pro fills clause variables.
Render an agreement for signing as Markdown or self-contained print-ready HTML, including signature block and template-not-legal-advice note.
Run a before-you-send checklist for missing fields and neutrally flagged one-sided gaps.
Check license status and activate a Pro key offline.
Free tier supports 3 active agreements; Pro adds unlimited active agreements, full clause texts, and HTML rendering.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-service-agreement Create a service agreement for a logo design for Acme Corp with a $2,000 flat fee."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP server for service agreements for freelancers: scope, deliverables, rate, termination and liability, rendered for signing. Service agreements for freelancers: scope, deliverables, rate, termination and liability, rendered for signing.
Works with Claude Desktop, Claude Code, Cursor and any Model Context Protocol client. Runs on your own machine, or hosted with no install.
Product page: https://mcp.zovo.one/s/service-agreement - what it does, the tools it exposes, and a live token endpoint.
Hosted, nothing to install. Get a token from https://mcp.zovo.one/mcp/connect (the connect page) or https://mcp.zovo.one/mcp/token (the same token as JSON); a free anonymous one is issued on the spot and a Pro key works the same way. Then point an MCP client at https://mcp.zovo.one/mcp/service-agreement over streamable-http and send the token as Authorization: Bearer <token>.
If your client cannot set headers, put the token in the path instead: https://mcp.zovo.one/mcp/service-agreement/t/<token>. Both forms work. The bare URL with no token answers 401 on tools/call, so the token is not optional.
Claude Desktop, one click. Download service-agreement.mcpb from the latest release and double-click it.
From source. The mirror is self-contained: every @theluckystrike/* dependency is vendored, so a fresh clone builds with no extra setup.
git clone https://github.com/theluckystrike/mcp-service-agreement.git
cd mcp-service-agreement
npm install && npm run buildThen point your client at the built entry point:
{
"mcpServers": {
"service-agreement": {
"command": "node",
"args": ["/absolute/path/to/mcp-service-agreement/dist/index.js"]
}
}
}
@theluckystrike/mcp-service-agreementis not published on npm yet, so annpx -y @theluckystrike/mcp-service-agreementcommand will fail. The three paths above are the working ones and each is exercised by CI.
Read-only mirror of mcp-servers/servers/service-agreement. See MIRROR.md.
In the official MCP Registry (io.github.theluckystrike/service-agreement).
An mcp service agreement writer for freelancers who are about to start client work and do not want to copy a rotting template off the internet again. 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 renders clean Markdown, or print-ready HTML, with a signature block for both sides. A before-you-send-it checklist lists missing fields and flags one-sided gaps neutrally, like an agreement with no termination clause. A built-in clause library covers IP assignment, confidentiality, late payment interest, kill fee and revision rounds, filled with your agreement's own details. Every render carries a one-line note that it is a template, not legal advice. Everything stays on this machine; there is no account and no network call.
Built by theluckystrike.
npm publish for @theluckystrike/mcp-service-agreement is pending, so npx -y @theluckystrike/mcp-service-agreement returns 404 today. Until then, a clone+build is the working path.
Related MCP server: AgentContract MCP Server
macOS ~/Library/Application Support/Claude/claude_desktop_config.json, Windows %APPDATA%\Claude\claude_desktop_config.json:
{
"mcpServers": {
"service-agreement": {
"command": "npx",
"args": ["-y", "@theluckystrike/mcp-service-agreement"]
}
}
}claude mcp add service-agreement -- npx -y @theluckystrike/mcp-service-agreement~/.cursor/mcp.json (global) or .cursor/mcp.json (project), same entry as Claude Desktop.
tool | what it does |
| Write an agreement: parties, scope, deliverables, rate and payment terms, dates, termination notice, liability cap, jurisdiction. Stores it and returns the rendered Markdown. Returns |
| Read one agreement in full by SA number or client name, with its status history |
| List agreements newest first; filter by status and client |
| Move the agreement exactly one step -- draft, sent, signed, expired -- stamping date and note into its history |
| The five built-in clauses: IP assignment, mutual confidentiality, late payment interest, kill fee, revision rounds. Pro: full texts with the agreement's variables filled in |
| Render for signing: Markdown, or self-contained HTML with print CSS (Pro). Includes the signature block and the template-not-legal-advice line |
| The before-you-send-it checklist: missing fields and one-sided gaps flagged neutrally |
| Free or Pro, and the key |
Free | Pro | |
Active agreements | 3 | Unlimited |
Core template (parties, services, deliverables, payment, term, termination, liability, jurisdiction, signatures) | Yes | Yes |
Markdown rendering | Yes | Yes |
Before-you-send checklist | Yes | Yes |
Clause library | Titles and summaries | Full texts, variables filled |
HTML rendering, print-ready | No | Yes |
The document is never metered. Three active agreements covers a working freelancer's live engagements, and an agreement stops counting the moment it expires, so writing, reading, checklists and Markdown stay free for good. What Pro adds is the full clause library, print-ready HTML, and unlimited active agreements.
Get Pro: https://mcp.zovo.one/buy/service-agreement, $19 one-time for this server, or $39 for the bundle.
Every rendered agreement ends with one line: "This agreement is a template, not legal advice." The checklist flags gaps neutrally, what the agreement says as written, for both parties, and never tells anyone what the law is or what to do.
All data stays local, in ${XDG_DATA_HOME:-~/.local/share}/mcp-servers/service-agreement/. Two files: agreements.json, counter.json. Nothing is sent anywhere, there is no account, no API key and no network call in this server at all. License keys are verified offline.
Built by theluckystrike. https://github.com/theluckystrike
Any MCP client (Claude, Cursor, Windsurf, VS Code) can read this repository's documentation directly via GitMCP - no install:
Docs MCP URL: https://gitmcp.io/theluckystrike/mcp-service-agreement
The before-you-send-it checklist for one agreement: every missing field is listed, and terms whose absence cuts one way are flagged neutrally -- as written, what the gap means for both parties -- such as no termination clause or an uncapped liability. Reads only.
Inputs: agreement (required).
Write a service agreement between a freelancer and a client before the work starts: 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. Stores the agreement and returns it rendered as clean Markdown with a signature block. Free tier: 3 active agreements; expiring a finished one frees its slot.
Inputs: scope (required), client (required), currency (required), rate_unit (required), +13 more.
Read one service agreement in full by SA number or client name: parties, scope, deliverables, rate and payment terms, dates, termination, liability cap, jurisdiction, the clauses it carries, its status and its status history. Reads only.
Inputs: agreement (required).
List service agreements newest first: parties, status, rate, dates and the clauses each carries. Filter by status and by client. An agreement is active until it is expired; the free tier holds 3 active agreements.
Inputs: client, status.
Render a service agreement ready to send and sign: the parties, the services, the deliverables, the payment terms, the term, termination, liability, jurisdiction, any library clauses it carries, and a signature block for both parties. Markdown, or self-contained HTML with print CSS that needs nothing from the network. HTML is a Pro feature. Writes nothing.
Inputs: agreement (required), format.
Move one agreement exactly one step: draft, sent, signed, expired, stamping the date and an optional note into its history. A skipped or backwards step is refused and nothing is written. Expiring a finished engagement frees a free-tier slot.
Inputs: status (required), agreement (required), date, note.
List the built-in clause library: intellectual property assignment, mutual confidentiality, late payment interest, kill fee and revision rounds. Each clause is a title plus a body text. Pass an agreement and, on Pro, every body comes back with that agreement's variables filled in. The free tier lists titles and summaries; the full texts are a Pro feature.
Inputs: agreement.
Activate a Pro key (MCPL1.xxx.yyy) from checkout: verified offline against a built-in public key, saved to your config file. A wrong, malformed or expired key is refused, unsaved. license_status reads it back.
Inputs: key (required).
Report this server's licence state: product, tier free or pro, licence id, expiry, the key source and the upgrade URL. No arguments, no network. Explains a free-tier refusal; license_activate installs a key.
Inputs: no named parameters.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 9 tools
The agreement tools are split by action (create/get/list/update_status/render/checklist) and the license tools are clearly separate, so an agent can usually pick the right one. The only mild ambiguity is that agreement_create and agreement_render both produce Markdown output, while agreement_checklist could be mistaken for a validation step rather than a read-only check.
Most tools follow an agreement_<verb pattern, and license_status/license_activate keep the same convention. The exceptions are agreement_checklist and clause_library, which use nouns instead of actions, creating a small but noticeable deviation.
Nine tools is well-scoped for a service-agreement server: CRUD-like agreement operations, rendering, checklist validation, a clause library, and license management all earn their place. The count feels intentional rather than bloated or sparse.
The set covers creating, reading, listing, status transitions, rendering, validation, clause lookup, and license activation, so the main lifecycle is represented. A clear gap is the absence of any way to update an agreement's content after creation; agents cannot fix a mistake or revise terms without creating a new agreement.
For individuals and small businesses: draft quotes, quote + agreement docs and contracts to sign.
Freelance business manager — clients, proposals, invoices, time tracking, scope, and follow-ups.
Send agreements for e-signing, use templates, track signatures, send reminders, get signed documents
Branded job estimates and client approvals for independent contractors.