Fatture in Cloud MCP by usefulapi

Create a client (Cliente) in a company's registry. Returns the new client with its id.

Create an invoice, quote, proforma, receipt, delivery note, credit note or order. It gets the next number unless you give one. Give client_id (the tool copies the stored client's details, as Fatture in Cloud does not fill them in) or a client object. Each item needs a vat_id (fattureincloud_list_settings kind vat_types). Without payments, invoices, proformas, receipts and credit notes get one unpaid payment of the full total, due on due_date or the document date. This does NOT send anything: e-mail it with fattureincloud_send_document_email or send an e-invoice with fattureincloud_send_einvoice.

Create a product or service in a company's catalogue. Returns the new product with its id.

One client with every field (address, VAT number, defaults, e-invoice code).

One company's details: name, email, type, the user's role and permissions in it, and the Fatture in Cloud plan and its limits.

Why the SDI rejected an e-invoice: the reason, the e-invoice status, the error code and a suggested solution.

One issued document with its customer, items, payments, totals, e-invoice status (ei_status) and PDF link.

What Fatture in Cloud needs to create a document of one type: numerations and next numbers, templates, default values (default VAT, template, payment method), payment methods and accounts, languages and units. Large reference tables are left out unless you ask for them in include: vat_types (also in fattureincloud_list_settings), currencies, countries, e_invoice_codes (SDI document types, regimes, cassa, withholding and payment reason codes) and e_invoice_structure (the XML field limits).

One product with prices, default VAT, category and stock.

One received document with its supplier, items, payments and totals.

One supplier with every field.

The Fatture in Cloud user this server is signed in as: id, name and email.

Cashbook (Prima nota) entries of a company between two dates: money in and out, with the linked documents and payment accounts.

Clients (Clienti) of a company, paged, with an optional filter.

The companies this sign-in can use, with their id (the company_id of the other tools), name, type, plan, VAT number and tax code. Accountants also see controlled_companies.

Issued documents of one type (invoices, quotes, credit notes, ...) of a company, paged. Unpaid invoices: type invoice with q next_due_date is not null. Date range: q date >= '2026-01-01' and date <= '2026-01-31'.

Products and services (Prodotti e servizi) of a company, paged, with an optional filter.

Received documents (expenses, supplier credit notes, delivery notes, self-invoices) of a company, paged.

Reference lists of a company that other tools need: vat_types (the vat_id of document items), payment_methods, payment_accounts (for paid payments and cashbook filters), revenue_centers, cost_centers, product_categories, received_document_categories.

Suppliers (Fornitori) of a company, paged, with an optional filter.

IRREVERSIBLE: e-mail an issued document to the customer from Fatture in Cloud. Use only when the user asks to send it. Recipient, sender, subject and body default to Fatture in Cloud's suggestions for this document. Other files (attachment, delivery note, accompanying invoice) go only when you ask for them.

IRREVERSIBLE: send an issued e-invoice (e_invoice true) to the Italian exchange system SDI. Use only when the user asks to send it. Run fattureincloud_verify_einvoice_xml first; dry_run true checks the send without sending.

Check whether an issued document produces a valid e-invoice XML before it goes to the SDI. Returns success or the validation errors.