
Rate Card
io.github.theluckystrikePublished by GitHub account theluckystrikev0.22.6Updated Oct 24, 2026
Hourly rates by role and date, priced into invoice and quote lines without retyping.
Overview
A local catalogue server that stores SKU prices and role hourly rates by date and prices invoice and quote line items from them.
- What you can do
- Set, reprice, look up, list and delete catalogue SKUs with dated prices in minor units per currency and tier, refusing unknown codes and dates before any price existed. Set and read hourly rates on role rate cards, optionally bound to a SKU. Price a list of SKU and role lines into ready-made invoice and quote payloads in one call, with the correct unit scale for each. Export the price list as plain text or, on Pro, as an A4 PDF, and run a catalogue report on rows in force, replaced rows and missing prices. Check or activate a Pro license.
- When to use it
- Useful when an assistant prepares invoices or quotes and prices must come from a maintained, date-aware rate card rather than being retyped or guessed. Suited to small businesses with a fixed price list and labour rates that change over time.
- Requirements
- Runs as a local process on the user's machine (desktop only). The README says the npm package is not yet published, so the .mcpb bundle or a clone and build is the working install path. Data is stored locally under the user's data directory. An optional MCP_LICENSE_KEY enables Pro features; no network access is needed.
Installation
In SourceWeft
- Open Rate Card in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
mcp-catalogue
In the official MCP Registry (io.github.theluckystrike/catalogue).
One price list and one rate card, kept where the invoice and the quote can both read them.
Give a product a code, a name, a unit and a price in minor units, with the day that price
comes into force. Give a role an hourly rate the same way. Then hand the catalogue a list
of what a customer had, and it hands back the line items already priced: the quantity, the
description, the unit price and the VAT rate, in the exact argument shape invoice_create
takes and in the exact argument shape quote_create takes.
Nothing is invented and nothing is stored twice. A SKU holds its price ROWS, each with a valid-from date; the price on a date is worked out on the call, so raising a price in July does not rewrite what June's job was quoted at. An unknown code comes back as a refusal naming the code, never as a guessed price.
npm publish for @theluckystrike/mcp-catalogue is pending, so npx -y @theluckystrike/mcp-catalogue returns 404 today. Until then, the .mcpb one-click bundle or a clone+build is the working path.
Install
Claude Desktop
~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or
%APPDATA%\Claude\claude_desktop_config.json (Windows):
Claude Code
Cursor
~/.cursor/mcp.json (global) or .cursor/mcp.json (project), same entry as Claude Desktop.
Tools
Free vs Pro
Get Pro: https://mcp.zovo.one/buy/catalogue ($19 one-time for this server, $39 for all of them, lifetime). Keys are verified offline; nothing is sent anywhere.
Where the price comes from
A price row is (currency, tier, valid_from, amount). The price on a date is the latest
valid_from at or before that date, for that currency and that tier. Setting a row on a
key that already exists REPLACES it, so two rows can never share one key and "the price
that day" is never a coin toss. A date before every row has no price and is refused; a
price that did not exist yet is not a price.
Nothing here converts a currency. A EUR price shown under a PLN heading would be an
invented number, so a SKU with no price in the currency you asked for is listed as having
none, and catalogue_report counts them.
The measured insight
The two servers this catalogue feeds take the same price in different scales, and the
gap is exactly 100x. invoice_create's item carries unit_price in MAJOR units
("Price per unit in major units, e.g. 90 for 90 EUR", servers/invoice/src/index.ts);
quote_create's item carries unit_price_minor in MINOR units ("9000 = 90.00 EUR, 90 =
JPY 90. Never a decimal", servers/quotes/src/index.ts). Both fields are called the unit
price, both take a plain number, and neither tool can tell that the number it was handed
was scaled for the other one: 45000 passed as unit_price is a valid invoice line for
EUR 45,000.00.
Measured on the worked resolution in test/unit.test.mjs: the correct payload nets
EUR 2,613.63, and the same items with the quote server's field fed into the invoice
server's engine net EUR 261,363.00, which the suite asserts is exactly 100x. In a
3-decimal currency such as KWD it is 1000x. So the catalogue stores minor units, which is
the only lossless form, and builds BOTH payloads itself in one call, printing the scale
against each. That is the whole reason lines_resolve returns two payloads instead of one
"price" the caller reshapes.
The second half of that: every stored price is a whole number of minor units, so
invoice_create's own computeTotals rounds the major-unit form straight back to the
integer it came from. rounding_drift_minor on a resolution is zero by construction and
the suite asserts it, which is the machine-checkable form of "the invoice will show the
figure the price list showed".
Privacy
All data stays local: ${XDG_DATA_HOME:-~/.local/share}/mcp-servers/catalogue/. No
network call is made by any tool. The only file outside that directory this server touches
is the shared business profile, read-only, for the default currency, the default VAT rate
and the name at the top of the price list. It creates no invoice and no quote.
Built by theluckystrike.
Use these docs as an MCP server
Any MCP client (Claude, Cursor, Windsurf, VS Code) can read this repository's documentation directly via GitMCP - no install:
- Docs MCP URL: https://gitmcp.io/theluckystrike/mcp-catalogue
Source: servers/catalogue/README.md at commit 6535b33
Tools
0Version history
3- v0.22.6LatestOct 14, 2026
- v0.22.3Sep 23, 2026
- v0.21.0Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts