[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Fatture in Cloud MCP tools

> The Fatture in Cloud MCP tools on the Cotlet server: every operation with its input schema, a tools/call example and an example result.

Source: https://cotlet.dev/docs/mcp/fatture-in-cloud

Docs sections: [Get started](https://cotlet.dev/docs.md) · [REST API](https://cotlet.dev/docs/api.md) · [MCP](https://cotlet.dev/docs/mcp.md) · [SDKs & CLI](https://cotlet.dev/docs/sdks.md) · [Integrations](https://cotlet.dev/docs/integrations.md)

Fatture in Cloud has 13 operations on the Cotlet MCP server, in fatture_in_cloud_read and fatture_in_cloud_write. Your agent picks one in `operation`; the tool carries each operation's input schema. Open an operation for its schema and an example call.

- MCP server: `https://cotlet.dev/mcp/v1`
- MCP tools: `fatture_in_cloud_read`, `fatture_in_cloud_write`
- Connects with: Your own Fatture in Cloud user with access to the company; for a sub-user, the company admin must grant the matching permissions
- Integration page: https://cotlet.dev/integrations/fatture-in-cloud-api-mcp-server

## Read

Return data and change nothing in the account.

| Operation | Description |
|---|---|
| [`list_invoices`](https://cotlet.dev/docs/mcp/fatture-in-cloud/list_invoices.md) | List issued invoices, filtered by date, client or payment status. |
| [`get_invoice`](https://cotlet.dev/docs/mcp/fatture-in-cloud/get_invoice.md) | Get one invoice with its lines, totals and payments. |
| [`list_clients`](https://cotlet.dev/docs/mcp/fatture-in-cloud/list_clients.md) | Find clients by name, VAT number or tax code. |
| [`list_expenses`](https://cotlet.dev/docs/mcp/fatture-in-cloud/list_expenses.md) | List received documents (expenses and supplier invoices), filtered by date. |
| [`get_einvoice_status`](https://cotlet.dev/docs/mcp/fatture-in-cloud/get_einvoice_status.md) | Read the SDI status of an invoice. |
| [`get_einvoice_rejection_reason`](https://cotlet.dev/docs/mcp/fatture-in-cloud/get_einvoice_rejection_reason.md) | Get the reason SDI rejected an e-invoice. |
| [`verify_einvoice`](https://cotlet.dev/docs/mcp/fatture-in-cloud/verify_einvoice.md) | Check an invoice's e-invoice XML for errors before sending it to SDI. |
| [`get_invoice_pdf`](https://cotlet.dev/docs/mcp/fatture-in-cloud/get_invoice_pdf.md) | Get a download link for the invoice PDF. |

## Write

Change the account. Calls marked Confirm wait for the user to approve them.

| Operation | Description |
|---|---|
| [`create_client`](https://cotlet.dev/docs/mcp/fatture-in-cloud/create_client.md) | Add a client with name, VAT number or tax code and address. |
| [`create_invoice`](https://cotlet.dev/docs/mcp/fatture-in-cloud/create_invoice.md) (Confirm) | Create an invoice for a client, with lines, VAT and a due date. |
| [`send_einvoice`](https://cotlet.dev/docs/mcp/fatture-in-cloud/send_einvoice.md) (Confirm) | Send an invoice to the Sistema di Interscambio as an electronic invoice. |
| [`record_invoice_payment`](https://cotlet.dev/docs/mcp/fatture-in-cloud/record_invoice_payment.md) (Confirm) | Mark an invoice payment as paid, with the date and payment account. |
| [`record_expense`](https://cotlet.dev/docs/mcp/fatture-in-cloud/record_expense.md) | Record an expense with supplier, date and net and VAT amounts. |

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.