Home · Setup · Claude.ai and Claude Desktop connectors
Record a sale of equipment, a vehicle or stock and get a printable bill of sale with signature lines. You tell it who sold, who bought, what the item is, with the VIN, serial number or IMEI where it has one, the price in whole minor units and the date, and it writes the document: parties, item, price, an as-is clause for second-hand sales, any warranty in your own words, and signature lines for both sides. A sale starts as a draft you can revise and delete; sale_finalize freezes it into the signing copy, and from there sale_update refuses it and every render prints without the DRAFT watermark that marks a review copy. sale_render prints Markdown or a single self-contained HTML file that prints to PDF from any browser with no assets beside it. A VIN that is not 17 characters or an IMEI that is not 15 digits is stored as given but flagged in the response. A byte-identical repeat sale is refused before the free cap is consulted and names the id already stored. A finalized document needs confirm_finalized to delete, and the BOS number is never reissued, so a gap in the series is the record of a deletion. The seller defaults to the shared business profile's name, so the seller block is typed once for the whole suite.
This server reads no sibling store at all beyond the shared business profile behind the token, so the hosted route needs nothing but what you type: the sales book lives in the hosted store behind the token, which means the ten free drafts, the five free finalized documents and the BOS-YYYY-NNNN numbers follow the key rather than the machine. There is no network call inside the server on any route, so the identifiers check, the DRAFT watermark and the frozen signing copy behave the same here as on a laptop, and no total is stored on either route because every figure is derived on the call. sale_render's files come back as one-hour download links rather than paths, since a hosted call has nowhere local to write.
| You say | Tool |
|---|---|
| Record a sale: Kowalski Transport buys my 2019 Ford Transit, VIN WF0XXXTTGXKC12345, EUR 18,500, as-is, dated 2026-03-10. | sale_create |
| Print the draft so they can read it before signing. | sale_render |
| They signed. Finalize it and give me the signing copy as HTML. | sale_finalize then sale_render |
Every amount is an integer number of minor units, a price is never a float, and dates are checked as real calendar dates. The smoke suite drives the whole lifecycle over real stdio: create, get, update, render with the DRAFT watermark, finalize, render the signing copy, the refusal of edits after finalize, the summary, the delete, and then the free caps on drafts and finalized documents and the same calls passing in Pro.
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/bill-of-sale/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 Bill of Sale 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: Ten open drafts and five finalized documents, with rendering to Markdown and HTML, listing, reading, the summary and deleting all free and unlimited on every tier. The document itself is never metered: whether you hold a signed record of the sale is the question this server exists to answer, and a free tier that withholds the document is a demo. 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 Bill of Sale for that connector.
The connector runs server-side with no filesystem of its own, so any file MCP Bill of Sale produces is handed back as a download link that expires after one hour, rather than a path on disk.
MCP Bill of Sale 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