Quaderno MCP server

Issues a credit note against an existing invoice, by `invoice_id`, and records the refund. It credits the whole invoice unless `credited_amount` is given. It consumes a document number and cannot be deleted, only voided.

credits.create

Emails the credit note to the address on file for its contact. A GET that mutates, so it is a write and is never replayed. Answers `delivered: true`.

credits.deliver

One credit note by id, with its lines, payments and the document it credits.

credits.get

Credit notes, newest first, as a bare array. A voided invoice leaves one of these beside it.

credits.list

Changes the administrative fields of a credit note: `notes`, `payment_details` and `tag_list`. Amounts, lines and the customer are immutable once it is issued.

credits.update

Voids a credit note. `void_reason` is required, exactly as for an invoice.

credits.void

Adds a customer. `first_name` is required, and holds the company name for a `company`. Give an `email` if documents will be delivered to this contact.

contacts.create

Removes a customer. Quaderno refuses with 422 while the contact still has documents attached, so invoices must be voided first. Answers 204 with no body.

contacts.delete

One customer by id. An unknown id answers **401**, not 404, with “Unauthorized access or contact does not exist”; the plugin reports it as `not_found_or_denied`.

contacts.get

Customers, newest first, answered as a bare array. Search with `q` and page with `created_before`; `next_created_before` carries the next cursor.

contacts.list

Changes a customer. Fields left out are left unchanged by the API, not cleared.

contacts.update

Adds a product. `name`, `code` and `unit_cost` are required, and `kind` is `one_off` or `subscription`, not the value the spec’s example suggests.

products.create

Removes a product. Existing documents keep the line they were issued with, so past invoices are unaffected.

products.delete

One product by id, with its price, tax class and the currency it is sold in.

products.get

Your product catalogue, newest first, from the `/items` route. A bare array; page with `created_before`.

products.list

Changes a product. Existing documents keep the line they were issued with, so past invoices are unaffected.

products.update

Issues a receipt for a sale that is already paid, so `payment_method` is required. Like an invoice, it consumes a document number and cannot be deleted or updated, only voided.

receipts.create

Emails the receipt to the address on file for its contact. A GET that mutates, so it is a write and is never replayed. Answers `delivered: true`.

receipts.deliver

One receipt by id, with its lines, payments and the invoice it settles.

receipts.get

Receipts, newest first, as a bare array. Filter by a `date` range or `contact`, and page with `created_before`.

receipts.list

Voids a receipt. `void_reason` is required, as for an invoice.

receipts.void

One tax jurisdiction by id, naming the country and any region whose tax rules apply.

jurisdictions.get

Every tax jurisdiction Quaderno knows, about 290 rows, as a bare array. Verified live: this route ignores `limit` and always returns the full list.

jurisdictions.list

One tax code by its identifier, such as `standard`.

taxCodes.get

The tax codes available on the account, as a bare array. This route honours `limit`, unlike `jurisdictions.list`.

taxCodes.list

Which account this key belongs to: `identity.href` is that account’s base URL, so this is how a caller finds the subdomain to pass as `account`. Also returns the default API version.

authorization

Checks that the key and account name are valid. The docs say it does not consume an API call. Answers `{"status":"OK"}`.

ping

Checks a VAT or tax number against the country’s registry. `valid` is true or false, or null when the registry could not be reached, which does not mean the number is invalid.

taxIds.validate

The tax rate Quaderno would charge for a customer country and tax code, with the resulting total. `tax_code` and `amount` are required from API version 20210316, which this plugin targets.

taxRates.calculate

Records a sale or a refund in one call: it creates the document and its payment together, which is what distinguishes it from `invoices.create`. The body is not an invoice body: the buyer is `customer`, each line carries its total as `amount`, and `payment.method` is required. A real financial record.

transactions.create

The webhook subscriptions on the account, with the events each one receives. Read only here: this plugin registers no inbound handler. The signing secret (`auth_key`) is left out of the result.

webhooks.list