Bill of sale

What bill of sale MCP server does

The bill of sale MCP server stores structured records for sales of vehicles, equipment, and stock. A record can include the seller, buyer, item details, an applicable VIN, serial number, or IMEI, the sale price, date, as-is language, warranty text, and notes. Each sale receives a number in the BOS-YYYY-NNNN format.

The document lifecycle separates review from signing. New records remain drafts and can be changed. Finalizing freezes the record, after which updates are rejected and rendered copies no longer show the DRAFT watermark. The generated document includes signature lines for both parties.

How it works

Create a sale with the facts of the transaction, then render it for review. If details need correction, update the draft before finalizing it. Once finalized, render the signing copy as Markdown, a self-contained HTML file suitable for browser print-to-PDF, or both.

Prices are supplied as integer minor units rather than floating-point values. Dates are checked as calendar dates. VINs and IMEIs are stored even when their format is unusual, but the response flags VINs that are not 17 characters and IMEIs that are not 15 digits.

Records are stored locally in ${XDG_DATA_HOME:-~/.local/share}/mcp-servers/bill-of-sale/, with sales, numbering, and rendered documents kept in separate files and directories. The local implementation makes no network calls, requires no account, and verifies license keys offline. A hosted streamable-HTTP option is also documented and requires a bearer token.

Tools and capabilities

• sale_create creates a sale and prevents an identical repeat unless confirmed.
• sale_update edits draft fields and can clear optional values with an empty string.
• sale_finalize converts a draft into an immutable signing copy.
• sale_list lists records newest first, with optional draft or finalized filtering.
• sale_get retrieves a complete record by its BOS number.
• sale_delete removes drafts; finalized records require explicit confirmation. Deleted numbers are not reused.
• sale_render produces Markdown, self-contained HTML, or both, including signature lines and draft watermarking where applicable.
• sale_summary reports draft and finalized counts and totals separately by currency.
• license_status and license_activate provide license information and activation support.

Setup and configuration

The documented local source workflow is to clone the repository, run npm install && npm run build, and point an MCP client to dist/index.js with Node. A packaged Claude Desktop .mcpb release is also available. The npm package is not currently published, so an npx installation command returns 404.

The hosted option uses https://mcp.zovo.one/mcp/bill-of-sale over streamable HTTP. It accepts a token in the Authorization: Bearer header or in the URL path when the client cannot set headers.

Limitations and notes

Free usage allows up to 10 open drafts and 5 finalized documents; Pro removes those record limits. Reading, listing, summarizing, rendering, and deleting are not metered separately according to the provided plan details.

The generated form is a generic template, not legal advice. Vehicle, boat, and regulated-goods transactions may have additional statutory forms or filing requirements depending on location. Currencies are not combined in summaries.