Home · Setup · Claude Desktop

MCP Bill of Sale in Claude Desktop

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.

The sale is usually agreed in this window, in the thread with the buyer, so reading the price, the identifiers and the date out of it and into sale_create is one sentence, and the review copy with its DRAFT watermark is the next one. Nothing leaves the machine: there is no network call in the server on any tool.

What you get in Claude Desktop

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.

Install it in Claude Desktop

The file is claude_desktop_config.json, and the key inside it is mcpServers.

One click, no JSON. Download bill-of-sale.mcpb from the latest release and open it. Claude Desktop installs it as an extension and runs it on the Node runtime it ships with, so neither your PATH nor your node version comes into it, and there is no file to edit. Everything below is the manual route, for when you want the entry in the config file itself.

The config block, which needs both strings absolute:

{
  "mcpServers": {
    "bill-of-sale": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-servers/servers/bill-of-sale/dist/index.js"]
    }
  }
}

If node came from nvm, asdf or homebrew, use the absolute path that which node prints rather than the bare word, because a stdio server started by this app inherits a limited PATH:

"command": "/Users/you/.nvm/versions/node/v22.14.0/bin/node"

The 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-sale

That 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:

{
  "mcpServers": {
    "bill-of-sale": {
      "command": "npx",
      "args": ["-y", "@theluckystrike/mcp-bill-of-sale"]
    }
  }
}

Save, then completely quit Claude Desktop and start it again. A window reload is not enough.

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.

No install: the hosted endpoint

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.

Claude Desktop notes worth knowing first

Two documented facts decide whether the entry works: every path in claude_desktop_config.json must be absolute, and a stdio server started here inherits only a limited, platform-dependent subset of environment variables. If node came from nvm or homebrew, paste what `which node` prints instead of the bare word. The .mcpb route avoids both: Claude Desktop ships a built-in Node.js environment.

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.

Questions

Where is claude_desktop_config.json?

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json. Windows: %APPDATA%\Claude\claude_desktop_config.json. There is no published Linux path. Settings, Developer, Edit Config opens the right copy and creates it if it does not exist.

I added it and MCP Bill of Sale does not appear.

In order: did you fully quit and restart, not just close the window? Is every path absolute? And is the command resolvable, given the limited environment a stdio server inherits here? If node came from nvm, paste what which node prints.

Can I install it without editing JSON?

Yes. An .mcpb bundle, the format renamed from .dxt, opens with Claude and shows an installation dialog. One you built yourself goes in through Settings, Extensions, Advanced settings, Install Extension.

Related

MCP Bill of Sale in detail · The same server in Claude.ai and Claude Desktop connectors and Claude Code · Every server in Claude Desktop · Guides · Claude Desktop docs · Buy Pro