Home · Setup · Claude Code
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.
`claude mcp add bill-of-sale` at user scope is the level that matches both the meter and the data: ten drafts and five finalized documents is a side business's year rather than a repository's, and the store is one directory per machine anyway. sale_render writes the HTML next to wherever you point out_path, so an absolute path into the current project is one flag.
| 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.
The file is .mcp.json, and the key inside it is mcpServers.
| Scope | Path |
|---|---|
| local (default) | ~/.claude.json, this project only |
| project | .mcp.json at the repository root |
| user | ~/.claude.json, every project |
If you also run Claude Desktop, the shortest path there is one click: bill-of-sale.mcpb
from the latest release opens as an extension, with no JSON and no terminal.
Claude Code reads its own config, so here it is:
From the terminal, against a built file:
claude mcp add --scope user bill-of-sale -- node /absolute/path/to/mcp-servers/servers/bill-of-sale/dist/index.js
claude mcp list # health-check it before the first prompt
# or --scope project, committed to .mcp.json for the teamThe node command above wants a built file. From a clone, once:
git clone https://github.com/theluckystrike/mcp-servers.git
cd mcp-servers && npm install
npm run build -w packages/mcp-license -w servers/bill-of-saleThat writes servers/bill-of-sale/dist/index.js, and its absolute path is the one argument
the config needs.
The npm packages are not published yet, so the form below returns a 404 today. It is here because it is what the entry becomes the day the publish lands, with nothing else changed:
claude mcp add bill-of-sale -- npx -y @theluckystrike/mcp-bill-of-saleNo restart. The entry is picked up in the next session, and `/mcp` reconnects one on demand.
Nothing is published to npm yet, so the working install paths are the ones above: the .mcpb bundle from the latest release, a clone and build, or the hosted URL.
There is no hosted endpoint for this one yet. MCP Bill of Sale runs locally over stdio with the config above, which is also the only form in which it reads and writes files on your own disk. Thirty of the servers in this collection are served at https://mcp.zovo.one/mcp/<name> over MCP streamable HTTP; https://mcp.zovo.one/mcp/connect lists them and prints a ready URL for each.
The `--` is load-bearing: it separates Claude Code's own options, such as --transport, --env and --scope, from the command that runs the server. And the default scope is local, private to you and to the directory you ran it in, so adding it in the wrong folder leaves the tools absent with no error at all.
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.
Local, the default, writes ~/.claude.json and is private to you and that directory. --scope project writes .mcp.json at the repository root, shared through version control. --scope user loads it everywhere.
Measured, not documented: of three fresh projects, one first prompt made zero tool calls although initialize answered in 1.05 seconds. Run claude mcp list once first: it prints Connected, and the next run used the tool.
Not this one. The office suite starts every sibling server as its own child process, so it runs locally over stdio. Thirty of those children are hosted individually at https://mcp.zovo.one/mcp/<name> if you want a no-install route; open https://mcp.zovo.one/mcp/connect and it prints a ready URL for each.
MCP Bill of Sale in detail · The same server in Claude Desktop and Cursor · Every server in Claude Code · Guides · Claude Code docs · Buy Pro