Service Agreement MCP server: install, tools and pricing

Service agreements for freelancers: scope, deliverables, rate, termination and liability caps.

Category: Documents and files · Tools: 7 · Version: 0.22.6 · Licence: MIT

Install it

  • Hosted, nothing to install: open https://mcp.zovo.one/mcp/connect - it mints a free token and prints a ready URL, https://mcp.zovo.one/mcp/service-agreement/t/<token>. Paste that into your client. The bare https://mcp.zovo.one/mcp/service-agreement hands out the tool list but answers tool calls with HTTP 401, which is why the tokenised URL is the one to use.
  • Claude Desktop, one click: download the .mcpb bundle
  • From source: git clone https://github.com/theluckystrike/mcp-servers then build servers/service-agreement.
  • npm: the package @theluckystrike/mcp-service-agreement is staged and publishes shortly; the .mcpb bundle is the supported install until then.

Tools it exposes

Tool What it does
agreement_create see tool reference
agreement_get see tool reference
agreement_list see tool reference
agreement_update_status see tool reference
clause_library see tool reference
agreement_render see tool reference
agreement_checklist see tool reference

Pricing

Free to run locally, forever. The Pro licence is $19, one time, lifetime — it changes only the hosted endpoint’s saved-report cap, never the tools. All 58 servers together are $39 as a bundle instead of $1102 bought one at a time.

Buy the Service Agreement Pro licence — $19

Questions people actually ask

Is the Service Agreement MCP server free?

Yes. Running Service Agreement locally is free and unlimited, and the code is MIT licensed. There is a one-time $19 Pro licence for the hosted endpoint, which removes the saved-report cap. No subscription and no account are required.

Does Service Agreement need an API key?

No. The server works offline against local files. If you use the hosted endpoint, the connection is authenticated with a scoped token instead of a per-tool API key.

Where does the data go?

Local installs keep everything on your machine. The hosted endpoint stores records in an isolated per-tenant namespace, and only for servers you actually call.

Which clients can use it?

Any MCP client: Claude Desktop (via the .mcpb bundle), Claude Code, Cursor, Windsurf, VS Code with an MCP extension, or your own agent over the Streamable HTTP transport.

  • Invoice MCP server — Make real, sendable PDF invoices from a sentence. Clients, numbering that never repeats, VAT lines, discounts
  • Quotes MCP server — Send a client a real quote in seconds: line items with VAT, a validity date, a plain-text version to paste int
  • Recurring MCP server — Bill the same clients every month without remembering to. Define a recurring invoice once, then generate the r
  • Credit Note MCP server — Credit notes against an invoice or standalone: drafts, finalization, rendering, totals.

All 58 back-office MCP servers · how the collection is organised