Home · Setup · Cursor

MCP Bill of Sale in Cursor

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.

sale_list, sale_get, sale_summary and sale_render are free, unlimited and never gated, so leave them enabled permanently: the document is never the metered thing. sale_finalize is the irreversible one, because from there sale_update refuses the document and the number is burned.

What you get in Cursor

You sayTool
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.

Install it in Cursor

The file is .cursor/mcp.json, and the key inside it is mcpServers.

ScopePath
This project only<project>/.cursor/mcp.json
Every project~/.cursor/mcp.json

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. Cursor reads its own config, so here it is:

The config block:

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

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"]
    }
  }
}

The Customize page shows the server and its tools once it has started.

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.

Cursor notes worth knowing first

The current field table marks `type` as required, with `stdio` for a locally launched server, so write it out rather than relying on command and args alone. The other documented restriction is that `envFile` is stdio-only: a remote HTTP or SSE server does not read it, and its headers belong in the config.

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

Project config or global config?

<project>/.cursor/mcp.json applies to that project and can be committed, which suits a server tied to one client. ~/.cursor/mcp.json applies everywhere. Both are managed from the Customize page.

Why does my stdio entry not start?

The current field table marks type as required, with stdio for a locally launched server, so include it. Pointing at a remote endpoint, envFile is documented as stdio-only and is not read.

Is there a one-click install link?

Servers in Cursor's marketplace get an Add to Cursor button. The deeplink reference currently documents prompt, command and rule links only, so for MCP Bill of Sale pasting the config block above is the supported route.

Related

MCP Bill of Sale in detail · The same server in Claude Code and VS Code · Every server in Cursor · Guides · Cursor docs · Buy Pro