Remote MCP server · REST API
Add receipt filing to your AI assistant.
Your assistant sends a receipt and gets back structured JSON and a renamed file.
Create an API key
Add it to your assistant
Checked against claude mcp add --help · not run live
Run this once, in any directory.
claude mcp add --transport http --scope user quickerfile https://www.quickerfile.com/api/mcp \
--header "Authorization: Bearer qf_live_..."claude mcp list should then show quickerfile.Why `--scope user`
--scope user writes it to your user config rather than the current project, so it is there for you in every project on this machine.
The command form is checked against claude mcp add --help, and the entry it writes has been inspected. Not yet run against the live endpoint.
File a receipt
Attach a receipt, or link to one, and ask:
File this receipt with Quickerfile and give me the vendor, date, tax, total and the saved filename.What comes back
| vendor | name, address, phone, tax or VAT registration number, website |
|---|---|
| transaction | date, time, receipt number, register, cashier |
| items | one row per line: name, quantity, unit price, total, SKU |
| payment | subtotal, tax, tax rate, total, ISO currency code, method, card type, last four digits, tip |
| classification | category and the model's own confidence in it |
| file | the same document renamed YYYY-MM-DD_Vendor_Amount.pdf, with the vendor, date, amount and keywords written into its Title, Subject and Keywords fields |
What it costs
Assistant, REST API and dashboard draw on the same monthly allowance.
| Plan | Price | Receipts a month |
|---|---|---|
| Free | $0 | 5 |
| Starter | $10/month | 250 |
| Pro | $20/month | 750 |
| Business | $50/month | 2,500 |
Free works against the API and the MCP endpoint too. Full pricing
Limits
| Formats | PDF, JPEG, PNG, WEBP, HEIC, HEIF |
|---|---|
| Size | 10 MB per file — about 7.4 MB as base64, larger as a url or as multipart |
| Per call | One receipt; there is no batch endpoint |
| Retention | Receipt records are scheduled to expire after 24 hours |
| Rate limits | 60 a minute per key on the MCP endpoint, 100 a day per account |
Why these limits
A request body is capped at 10 MB, and base64 is a third larger than the file it carries, so a base64 receipt tops out at about 7.4 MB. Anything bigger goes in as a url, which the server downloads itself, or as multipart form data on the REST API. Over the limit you get payload_too_large rather than a parse error, decided from the Content-Length header.
A JPEG or PNG comes back as a single-page PDF wrapping the image, so the metadata has somewhere to live. WEBP, HEIC and HEIF are returned as they arrived, renamed, with metadata_embedded: false.
A url is fetched by the server, on the MCP tool and in the REST JSON body alike, and the two are mutually exclusive with the base64 field. One that resolves to anything other than a public internet address is refused, and every redirect is checked again.
Download links point to public, unguessable URLs and may remain reachable until cleanup succeeds; treat them as secrets. The 100-request rolling daily limit applies only on deployments with rate limiting configured.
The MCP endpoint adds a 60-request-per-minute limit per API key, on top of that daily account limit and under the same condition. A 429 from one key does not mean the account is out of room.
Building against it directly
POST /api/v1/receipts file one — multipart, base64 or url
GET /api/v1/receipts/{id} read it back
GET /api/v1/usage the allowance