About service-contract
An MCP server for freelancers preparing service agreements, with fields for scope, deliverables, payment, term, and liability. It creates Markdown or HTML, includes a pre-send checklist and clause library, and stores data locally; rendered documents state that they are templates, not legal advice.
Key features
- 01Create and manage service agreements
- 02Render Markdown with signature blocks
- 03Check missing fields and one-sided gaps
- 04Provide five common contract clauses
- 05Store agreement data locally
Use cases
- 01Draft terms for a new client engagement
- 02Check for missing fields before sending
- 03Render an agreement for signing
MCP support
This MCP server gives clients tools to create, retrieve, update, render, and check service agreements.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEmcp-service-agreement
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.
Install
Claude Desktop
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 Code
claude mcp add service-agreement -- npx -y @theluckystrike/mcp-service-agreement
Cursor
~/.cursor/mcp.json (global) or .cursor/mcp.json (project), same entry as Claude Desktop.
Tools
| tool | what it does |
|---|---|
agreement_create | Write an agreement: parties, scope, deliverables, rate and payment terms, dates, termination notice, liability cap, jurisdiction. Stores it and returns the rendered Markdown. Returns SA-YYYY-NNNN |
agreement_get | Read one agreement in full by SA number or client name, with its status history |
agreement_list | List agreements newest first; filter by status and client |
agreement_update_status | Move the agreement exactly one step -- draft, sent, signed, expired -- stamping date and note into its history |
clause_library | 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 |
agreement_render | Render for signing: Markdown, or self-contained HTML with print CSS (Pro). Includes the signature block and the template-not-legal-advice line |
agreement_checklist | The before-you-send-it checklist: missing fields and one-sided gaps flagged neutrally |
license_status / license_activate | Free or Pro, and the key |
Free vs Pro
| 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.
Not legal advice
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.
Privacy
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
Use these docs as an MCP server
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
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.