Home · Setup · Cursor

MCP Service Agreement in Cursor

Service agreements for freelancers: scope, deliverables, rate, termination and liability, rendered for signing. You 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 returns it rendered as clean Markdown with a signature block, numbered SA-YYYY-NNNN. agreement_checklist is the before-you-send-it pass: every missing field listed, and terms whose absence cuts one way flagged neutrally, as written, for both parties - no termination clause, an uncapped liability. agreement_update_status moves the agreement exactly one step at a time, draft to sent to signed to expired, stamping date and note into its history, and a skipped or backwards step is refused naming the one step that is next. 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.

agreement_get, agreement_list, agreement_checklist and agreement_render of Markdown are free, unlimited and write nothing, so leave them enabled permanently. agreement_update_status is the deliberate one: the agreement moves exactly one step at a time, every step dated, and a skipped step is refused rather than stamped over.

What you get in Cursor

You say	Tool
Write an agreement between Anna Nowak and Brightleaf Studio: design and build of a five-page marketing site, 85.00 EUR an hour, Net 14, 14 days notice, liability capped at 8,500 EUR, England and Wales.	`agreement_create`
Run the checklist on it before I send it.	`agreement_checklist`
Mark it sent today.	`agreement_update_status`

The contract suite drives the nine tools over real stdio: the fourth active agreement is refused and nothing is written, expiring one frees the slot, the clause texts and HTML rendering refuse free-tier calls with the tagged upgrade link, and a draft cannot jump straight to signed. The only files written are agreements.json and counter.json.

Install it in Cursor

The file is .cursor/mcp.json, and the key inside it is mcpServers.

Scope	Path
This project only	`<project>/.cursor/mcp.json`
Every project	`~/.cursor/mcp.json`

If you also run Claude Desktop, the shortest path there is one click: service-agreement.mcpb from the latest release opens as an extension, with no JSON and no terminal. Cursor reads its own config, so here it is:

The config block:

{
  "mcpServers": {
    "service-agreement": {
      "type": "stdio",
      "command": "node",
      "args": ["/absolute/path/to/mcp-servers/servers/service-agreement/dist/index.js"]
    }
  }
}

The node command above wants a built file. From a clone, once:

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

That writes servers/service-agreement/dist/index.js, and its absolute path is the one argument the config needs.

The npm packages are not published yet, so the form below returns a 404 today. It is here because it is what the entry becomes the day the publish lands, with nothing else changed:

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

The Customize page shows the server and its tools once it has started.

Nothing is published to npm yet, so the working install paths are the ones above: the .mcpb bundle from the latest release, a clone and build, or the hosted URL.

No install: the hosted endpoint

The same server runs at https://mcp.zovo.one/mcp/service-agreement over MCP streamable HTTP, no install. Mint a free token with curl https://mcp.zovo.one/mcp/token, or use a Pro key. It has no filesystem, so a file comes back as a one-hour download link.

{
  "mcpServers": {
    "service-agreement": {
      "url": "https://mcp.zovo.one/mcp/service-agreement",
      "headers": { "Authorization": "Bearer <token>" }
    }
  }
}

Cursor notes worth knowing first

The current field table marks `type` as required, with `stdio` for a locally launched server, so write it out rather than relying on command and args alone. The other documented restriction is that `envFile` is stdio-only: a remote HTTP or SSE server does not read it, and its headers belong in the config.

Free: 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 is $19 once, verified offline.

Questions

Project config or global config?

<project>/.cursor/mcp.json applies to that project and can be committed, which suits a server tied to one client. ~/.cursor/mcp.json applies everywhere. Both are managed from the Customize page.

Why does my stdio entry not start?

The current field table marks type as required, with stdio for a locally launched server, so include it. Pointing at a remote endpoint, envFile is documented as stdio-only and is not read.

Is there a one-click install link?

Servers in Cursor's marketplace get an Add to Cursor button. The deeplink reference currently documents prompt, command and rule links only, so for MCP Service Agreement pasting the config block above is the supported route.

MCP Service Agreement in detail · The same server in Claude Code and VS Code · Every server in Cursor · Guides · Cursor docs · Buy Pro