Service Contract

io.github.theluckystrikePublished by GitHub account theluckystrikev0.22.5Updated Oct 24, 2026

Write a freelance service contract: scope, deliverables, rate, termination, liability, signatures.

VerifiedSTDIODesktop onlyProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

A local MCP server that drafts freelance service contracts and renders them as Markdown or print-ready HTML with signature blocks.

What you can do
Create agreements from parties, scope, deliverables, rate, payment terms, dates, termination notice, liability cap and jurisdiction, stored and returned as Markdown with an SA number. Read, list and filter agreements by status or client, with status history. Advance an agreement one step through draft, sent, signed and expired. Look up five built-in clauses (IP assignment, confidentiality, late payment interest, kill fee, revision rounds). Render for signing as Markdown or self-contained HTML with print CSS. Run a before-you-send checklist that flags missing fields and one-sided gaps.
When to use it
Useful for freelancers starting client work who want a structured, reusable contract draft and a pre-send gap check without copying a template from the web. Suits drafting and organizing agreements locally; it is not a substitute for legal review.
Requirements
Runs as a local process on the user's machine (desktop only). The npm package is not yet published, so a clone-and-build is currently the working install path. No account, API key or network call; data is stored locally. An optional Pro license key can be supplied via the MCP_LICENSE_KEY environment variable and is verified offline.
Before you install
Free tier is limited to three active agreements; Pro (a one-time purchase) unlocks unlimited agreements, full clause texts and print-ready HTML. Agreements are templates, not legal advice, and the checklist only flags gaps neutrally. Status changes are written to local storage. License keys are entered as MCP_LICENSE_KEY.

Installation

In SourceWeft

  1. Open Service Contract in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

mcp-service-agreement

[theluckystrike/mcp-service-agreement MCP server]

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:

json
{  "mcpServers": {    "service-agreement": {      "command": "npx",      "args": ["-y", "@theluckystrike/mcp-service-agreement"]    }  }}

Claude Code

sh
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

toolwhat it does
agreement_createWrite 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_getRead one agreement in full by SA number or client name, with its status history
agreement_listList agreements newest first; filter by status and client
agreement_update_statusMove the agreement exactly one step -- draft, sent, signed, expired -- stamping date and note into its history
clause_libraryThe 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_renderRender for signing: Markdown, or self-contained HTML with print CSS (Pro). Includes the signature block and the template-not-legal-advice line
agreement_checklistThe before-you-send-it checklist: missing fields and one-sided gaps flagged neutrally
license_status / license_activateFree or Pro, and the key

Free vs Pro

FreePro
Active agreements3Unlimited
Core template (parties, services, deliverables, payment, term, termination, liability, jurisdiction, signatures)YesYes
Markdown renderingYesYes
Before-you-send checklistYesYes
Clause libraryTitles and summariesFull texts, variables filled
HTML rendering, print-readyNoYes

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:

Source: servers/service-agreement/README.md at commit 55b3f42

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.22.5LatestOct 14, 2026
  2. v0.22.0Sep 23, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts