io.github.theluckystrike/service-contract

Official9 toolsLive

by theluckystrike · JavaScript

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

io.github.theluckystrike/service-contract (MCP Server)

This MCP server provides the content needed to write a freelance service contract. Its description centers on generating a contract that covers scope, deliverables, rate, termination, liability, and signatures. The server is identified by the slug io-github-theluckystrike-service-contract.

🛠️ Key Features

Generates freelance service contract text
Includes sections for scope and deliverables
Covers rate, termination, liability, and signatures

🚀 Use Cases

Drafting freelance service agreements
Defining project scope and deliverables in a contract
Documenting commercial terms (rate) and legal terms (liability, termination)

⚡ Developer Benefits

Structured contract elements aligned with the included fields

⚠️ Limitations

No additional capabilities beyond the described contract-writing scope are provided in the available source data

Topics

claudecursorinvoicemcpmcp-servermodel-context-protocolspreadsheetaccountingai-toolsbookkeepingclaude-desktopfreelanceinvoicinglocal-firstmcp-serverspdfself-hostedtime-trackingvatproductivity

Captured live from the server via tools/list.

agreement_create

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.

Parameters17

freelancer	string	required	Who does the work, e.g. Anna Nowak, or Nowak Design
client	string	required	Who the work is for, e.g. Brightleaf Studio
scope	string	required	The services the freelancer provides, e.g. Design and build of a five-page marketing site, with two weeks of post-launch fixes
deliverables	array	required	What the client receives at the end, e.g. ["Five-page site deployed to the client's host", "Handover document"]
rate_cents	integer	required	The rate in whole cents. 8500 is 85.00
rate_unit	string	required	What the rate buys: an hour, a day, or the whole project
currency	string	required	ISO code the rate and cap are in
payment_terms	string	required	When and how it is paid, e.g. Net 14 from invoice date, or 50% on signing and 50% on delivery
start_date	string	optional	The date work begins, YYYY-MM-DD. May be in the future; it is a plan, not a log
end_date	string	optional	The date the engagement ends, YYYY-MM-DD. Leave unset for an open-ended engagement
termination_notice_days	integer	optional	Days of written notice either party must give to end the agreement, e.g. 14
liability_cap_cents	integer	optional	The most the freelancer can be liable for, in whole cents. Leave unset and liability is uncapped, which the checklist flags
jurisdiction	string	optional	The governing law and courts, e.g. England and Wales, or the State of New York
clauses	array	optional	Ids of library clauses to include, from clause_library: ip_assignment, confidentiality, late_payment, kill_fee, revision_rounds. The clause library is a Pro feature
freelancer_address	string	optional
client_address	string	optional
note	string	optional

Raw schema

{
  "type": "object",
  "properties": {
    "freelancer": {
      "type": "string",
      "maxLength": 200,
      "description": "Who does the work, e.g. Anna Nowak, or Nowak Design"
    },
    "client": {
      "type": "string",
      "maxLength": 200,
      "description": "Who the work is for, e.g. Brightleaf Studio"
    },
    "scope": {
      "type": "string",
      "maxLength": 4000,
      "description": "The services the freelancer provides, e.g. Design and build of a five-page marketing site, with two weeks of post-launch fixes"
    },
    "deliverables": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 400
      },
      "minItems": 1,
      "maxItems": 50,
      "description": "What the client receives at the end, e.g. [\"Five-page site deployed to the client's host\", \"Handover document\"]"
    },
    "rate_cents": {
      "type": "integer",
      "minimum": 0,
      "maximum": 100000000000000,
      "description": "The rate in whole cents. 8500 is 85.00"
    },
    "rate_unit": {
      "type": "string",
      "enum": [
        "hour",
        "day",
        "project"
      ],
      "description": "What the rate buys: an hour, a day, or the whole project"
    },
    "currency": {
      "type": "string",
      "pattern": "^[A-Za-z]{3}$",
      "description": "ISO code the rate and cap are in"
    },
    "payment_terms": {
      "type": "string",
      "maxLength": 500,
      "description": "When and how it is paid, e.g. Net 14 from invoice date, or 50% on signing and 50% on delivery"
    },
    "start_date": {
      "type": "string",
      "maxLength": 10,
      "description": "The date work begins, YYYY-MM-DD. May be in the future; it is a plan, not a log"
    },
    "end_date": {
      "type": "string",
      "maxLength": 10,
      "description": "The date the engagement ends, YYYY-MM-DD. Leave unset for an open-ended engagement"
    },
    "termination_notice_days": {
      "type": "integer",
      "minimum": 0,
      "maximum": 365,
      "description": "Days of written notice either party must give to end the agreement, e.g. 14"
    },
    "liability_cap_cents": {
      "type": "integer",
      "minimum": 0,
      "maximum": 100000000000000,
      "description": "The most the freelancer can be liable for, in whole cents. Leave unset and liability is uncapped, which the checklist flags"
    },
    "jurisdiction": {
      "type": "string",
      "maxLength": 300,
      "description": "The governing law and courts, e.g. England and Wales, or the State of New York"
    },
    "clauses": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 40
      },
      "maxItems": 20,
      "description": "Ids of library clauses to include, from clause_library: ip_assignment, confidentiality, late_payment, kill_fee, revision_rounds. The clause library is a Pro feature"
    },
    "freelancer_address": {
      "type": "string",
      "maxLength": 400
    },
    "client_address": {
      "type": "string",
      "maxLength": 400
    },
    "note": {
      "type": "string",
      "maxLength": 4000
    }
  },
  "required": [
    "freelancer",
    "client",
    "scope",
    "deliverables",
    "rate_cents",
    "rate_unit",
    "currency",
    "payment_terms"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

agreement_get

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.

Parameters1

agreement

string

required

The agreement id, e.g. SA-2026-0003, or the client name when only one agreement has it

Raw schema

{
  "type": "object",
  "properties": {
    "agreement": {
      "type": "string",
      "maxLength": 200,
      "description": "The agreement id, e.g. SA-2026-0003, or the client name when only one agreement has it"
    }
  },
  "required": [
    "agreement"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

agreement_list

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.

Parameters2

status	string	optional	Only agreements at this status: draft, sent, signed, expired
client	string	optional	Only agreements whose client contains this text, case-insensitive

Raw schema

{
  "type": "object",
  "properties": {
    "status": {
      "type": "string",
      "maxLength": 20,
      "description": "Only agreements at this status: draft, sent, signed, expired"
    },
    "client": {
      "type": "string",
      "maxLength": 200,
      "description": "Only agreements whose client contains this text, case-insensitive"
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

agreement_update_status

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.

Parameters4

agreement	string	required	The agreement id, e.g. SA-2026-0003, or the client name when only one agreement has it
status	string	required	The next step for this agreement: draft, sent, signed, expired
date	string	optional	The date to stamp the step with, YYYY-MM-DD. Default today
note	string	optional

Raw schema

{
  "type": "object",
  "properties": {
    "agreement": {
      "type": "string",
      "maxLength": 200,
      "description": "The agreement id, e.g. SA-2026-0003, or the client name when only one agreement has it"
    },
    "status": {
      "type": "string",
      "maxLength": 20,
      "description": "The next step for this agreement: draft, sent, signed, expired"
    },
    "date": {
      "type": "string",
      "maxLength": 10,
      "description": "The date to stamp the step with, YYYY-MM-DD. Default today"
    },
    "note": {
      "type": "string",
      "maxLength": 4000
    }
  },
  "required": [
    "agreement",
    "status"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

clause_library

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.

Parameters1

agreement

string

optional

Fill each clause body with this agreement's variables. Pro feature

Raw schema

{
  "type": "object",
  "properties": {
    "agreement": {
      "type": "string",
      "maxLength": 200,
      "description": "Fill each clause body with this agreement's variables. Pro feature"
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

agreement_render

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.

Parameters2

agreement	string	required	The agreement id, e.g. SA-2026-0003, or the client name when only one agreement has it
format	string	optional	markdown (default) or html. The HTML carries its own styling and references nothing external. HTML is a Pro feature

Raw schema

{
  "type": "object",
  "properties": {
    "agreement": {
      "type": "string",
      "maxLength": 200,
      "description": "The agreement id, e.g. SA-2026-0003, or the client name when only one agreement has it"
    },
    "format": {
      "type": "string",
      "enum": [
        "markdown",
        "html"
      ],
      "description": "markdown (default) or html. The HTML carries its own styling and references nothing external. HTML is a Pro feature"
    }
  },
  "required": [
    "agreement"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

agreement_checklist

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.

Parameters1

agreement

string

required

The agreement id, e.g. SA-2026-0003, or the client name when only one agreement has it

Raw schema

{
  "type": "object",
  "properties": {
    "agreement": {
      "type": "string",
      "maxLength": 200,
      "description": "The agreement id, e.g. SA-2026-0003, or the client name when only one agreement has it"
    }
  },
  "required": [
    "agreement"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

license_status

Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}

license_activate

Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.

Parameters1

key

string

required

License key from checkout, MCPL1.<payload>.<signature>

Raw schema

{
  "type": "object",
  "properties": {
    "key": {
      "type": "string",
      "description": "License key from checkout, MCPL1.<payload>.<signature>"
    }
  },
  "required": [
    "key"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

servers/service-agreement/README.md5 KBView on GitHub

mcp-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:

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

Install

Tools (9)

agreement_createagreement_getagreement_listagreement_update_statusclause_libraryagreement_renderagreement_checklistlicense_status

Remote endpoint

Streamable HTTP

Hosted server - connect over the network, no local install.

url

https://mcp.zovo.one/mcp/service-contract

Configuration

Environment variables

MCP_LICENSE_KEYsecret

Optional Pro license key (MCPL1....). Verified offline.

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "service-contract": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.zovo.one/mcp/service-contract"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.

io.github.theluckystrike/service-contract (MCP Server)

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

agreement_create

agreement_get

agreement_list

agreement_update_status

clause_library

agreement_render

agreement_checklist

license_status

license_activate

mcp-service-agreement

Install

Claude Desktop

Claude Code

Cursor

Tools

Free vs Pro

Not legal advice

Privacy

Use these docs as an MCP server

Install

Remote endpoint

Configuration

Related servers