Home · Setup · Claude.ai and Claude Desktop connectors
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.
The agreements live in the hosted store behind the token, so the three free active agreements and the SA-YYYY-NNNN numbers follow the key rather than the machine. There is no network call inside the server on any route, so the one-step status machine and the checklist behave the same here as on a laptop, and agreement_render's Markdown or HTML comes back inline in the answer: no file is ever written on the hosted route, and the template-not-legal-advice line travels with the document.
| 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.
https://mcp.zovo.one/mcp/connect mints an anonymous token and prints a URL per server, including this one, shaped like https://mcp.zovo.one/mcp/service-agreement/t/<token>. That URL works with no headers: the token is in the path, not in an Authorization field this form does not have.
Idle anonymous tokens are swept after 30 days. Since this route has no filesystem, a file MCP Service Agreement generates comes back as a download link that expires after one hour. A Pro key can replace the token in the same URL and removes the free-tier limits.
On an individual Pro or Max plan you add the connector yourself from Customize, Connectors. On Team and Enterprise it is the other way round: only an Owner or Primary Owner can add a custom connector, at Organization settings, Connectors, and members then connect to what the Owner added rather than pasting their own URL.
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, and binds to the token after checkout.
No. Add custom connector offers an Advanced settings section with an OAuth Client ID and Client Secret, but the connect-by-URL route does not use it. Leave both blank: the token in the URL path is what authenticates.
That is documented, not a bug: on Team and Enterprise, only an Owner or Primary Owner can add a custom connector, at Organization settings, Connectors, Add, Custom, Web. After that, members connect to the URL the Owner added from Customize, Connectors.
Yes. The token segment of the URL from /mcp/connect can be replaced with a Pro key, which removes the free-tier limits on MCP Service Agreement for that connector.
The connector runs server-side with no filesystem of its own, so any file MCP Service Agreement produces is handed back as a download link that expires after one hour, rather than a path on disk.
MCP Service Agreement in detail · How connect-by-URL works · Every server for Claude.ai and Claude Desktop connectors · All clients · Claude.ai and Claude Desktop connectors docs · Buy Pro