Home · Setup · VS Code

MCP Service Agreement in VS Code

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.

In agent mode the checklist is the gate to run before anything goes out: it lists the missing fields and flags the one-sided gaps neutrally, as written, for both parties - and the render carries the template-not-legal-advice line on its face, which an agent summarizing the document must not drop.

What you get in VS Code

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 VS Code

The file is .vscode/mcp.json, and the key inside it is servers.

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. VS Code reads its own config, so here it is:

// .vscode/mcp.json  (the key is "servers")
{
  "servers": {
    "service-agreement": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-servers/servers/service-agreement/dist/index.js"]
    }
  }
}

Or from a terminal:

code --add-mcp '{"name":"service-agreement","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:

code --add-mcp '{"name":"service-agreement","command":"npx","args":["-y","@theluckystrike/mcp-service-agreement"]}'

VS Code asks you to confirm you trust the server and its capabilities before it starts. Nothing runs until you answer.

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.

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

VS Code notes worth knowing first

The top-level key is "servers", not "mcpServers". A config pasted from a Claude Desktop or Cursor README parses cleanly, contributes no servers, and gives you no error to read, which makes it the most expensive one-word mistake here. Alongside it an "inputs" array holds secrets. The newer Agent Host reads a workspace .mcp.json instead.

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

Why does my mcp.json do nothing?

The key is servers, not mcpServers. A config copied from a Claude Desktop README parses cleanly and contributes nothing. Rename it. On the newer Agent Host, use a workspace .mcp.json instead.

Do I have to edit the file at all?

No. code --add-mcp takes the server object on the command line, and MCP: Add Server in the palette asks whether the target is Workspace or Global.

Where do the MCP Service Agreement tools show up?

In Chat, behind the tools picker, once the server has started. Adding or changing one raises a prompt asking you to confirm you trust it; if the picker is empty, that prompt is usually still waiting.

Related

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