Service agreements for freelancers: scope, deliverables, rate, termination and liability caps.
Category: Documents and files · Tools: 7 · Version: 0.22.6 · Licence: MIT
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..mcpb bundlegit clone https://github.com/theluckystrike/mcp-servers then build servers/service-agreement.@theluckystrike/mcp-service-agreement is staged and publishes shortly; the .mcpb bundle is the supported install until then.| 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 |
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
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.
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.
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.
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.
All 58 back-office MCP servers · how the collection is organised