fattureincloud.it

Live

Fatture in Cloud API and MCP server

Fatture in Cloud's API covers invoices, clients and e-invoices, but it takes an app registration or access token and code you write and host. Sign in to Fatture in Cloud once in your own Cloud Browser, and your AI agent does the work there for you. The same tools work over MCP for agents and as a REST API for scripts.

Sign up free View as Markdown

Not affiliated with Fatture in Cloud.

Fatture in Cloud has no API for this. So we run one for you.

Fatture in Cloud's own API, a GitHub MCP server and Cotlet compared
What you need Fatture in Cloud's APIGitHub MCP serverCotlet
Use without an API key or code No Partly Yes, 13 tools
Acts as you, signed in 24/7 No No Yes, Cloud Browser
Fixed for you when Fatture in Cloud changes N/A No Yes, tested every 6h
Runs with your laptop off N/A No Yes, hosted

Checked Oct 14, 2026. Sources: Fatture in Cloud for Developers: Getting started · Fatture in Cloud for Developers: Authentication · Fatture in Cloud for Developers: Scopes · Fatture in Cloud for Developers: Guides (invoice creation, e-invoice management)

Your own Cloud Browser, on 24/7. Sign in once. We keep it connected.

  1. 01Sign in to Fatture in Cloud in your own Cloud Browser

  2. 02Connect it for your agents

  3. 03Cotlet keeps it signed in and working

How do I connect Fatture in Cloud to Claude, ChatGPT or my code?

AI agents connect over MCP, scripts call the REST API. Both reach the same 13 tools with one API key.

For AI agents: MCP

Add Cotlet to your agent once. Fatture in Cloud and every other app you connect show up as its tools.

  • Claude
  • ChatGPT
  • OpenClaw
  • Hermes
  • GrokBot
  • Cursor
  • n8n
  • Any MCP client
  1. 1

    Add Cotlet to your agent

    Claude Code
    claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
    Cursor
    {
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
    Codex
    # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"

    Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

For scripts: REST API

Every tool is an endpoint under /api/v1/fatture-in-cloud with its own method and path, such as POST /api/v1/fatture-in-cloud/clients/{client_id}/invoices, with the same API key. Our open-source repo has ready scripts to start from.

REST API docs

What can the Fatture in Cloud API and MCP server do?

13 tools on your own Fatture in Cloud account. Agents call them as operations of the MCP tools fatture_in_cloud_read and fatture_in_cloud_write; scripts call each one at its own REST endpoint, with the same inputs and answers.

API reference
Fatture in Cloud tools in Cotlet's MCP server and REST API
Tool What it does Access
list_invoices List issued invoices, filtered by date, client or payment status. read
get_invoice Get one invoice with its lines, totals and payments. read
list_clients Find clients by name, VAT number or tax code. read
list_expenses List received documents (expenses and supplier invoices), filtered by date. read
get_einvoice_status Read the SDI status of an invoice. read
get_einvoice_rejection_reason Get the reason SDI rejected an e-invoice. read
verify_einvoice Check an invoice's e-invoice XML for errors before sending it to SDI. read
get_invoice_pdf Get a download link for the invoice PDF. read
create_client Add a client with name, VAT number or tax code and address. write
create_invoice Create an invoice for a client, with lines, VAT and a due date. writeasks first
send_einvoice Send an invoice to the Sistema di Interscambio as an electronic invoice. writeasks first
record_invoice_payment Mark an invoice payment as paid, with the date and payment account. writeasks first
record_expense Record an expense with supplier, date and net and VAT amounts. write

Scroll the table for all 13 tools.

Ask in plain words. Your agent does the rest.

All Fatture in Cloud use cases

Is it safe to connect Fatture in Cloud?

You sign in yourself in your own Cloud Browser, we never save your password, and anything that reaches your readers waits for your OK. The browser profile is encrypted in the EU. Independent scanners grade cotlet.dev A+.

Security overview

How much do the Fatture in Cloud API and MCP server cost?

One price for both: a tool call costs the same over MCP or REST. Free 7-day trial with 2,000 credits, no card needed. Then one-time credit packs, no subscription, valid 12 months. Most calls use 25 credits, and your Cloud Browser uses 50 credits a day while Fatture in Cloud is enabled for agents, so 20 calls a day come to 550 credits.

See full pricing
Cotlet credit packs: price, credits and calls at 25 credits each
Credits Price, one time Calls at 25 credits Per 1,000 credits
5,000 $29 200 $5.80
15,000 $79 600 $5.27
32,000 $149 1,280 $4.66
60,000 $249 2,400 $4.15

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.

Questions

Does Fatture in Cloud have an API?

Yes, Fatture in Cloud has a documented REST API (v2) for issued invoices, clients, received documents, e-invoices to SDI and attachments (checked 14 Oct 2026), but it has no official MCP server. To use it you register an OAuth 2.0 app, or create a manual access token in the web app, choose scopes and pick the companies the token applies to.

How do I get access?

Sign up free, open Fatture in Cloud under Integrations in the console and press Request access. Your free trial starts with your account, no card needed.

Is the MCP server different from the API?

No, only the way in. Cotlet builds each integration as a REST API and puts an MCP server on top, so both have the same 13 tools, the same inputs and answers, one API key and one price. AI agents such as Claude, ChatGPT or Cursor use MCP; scripts, cron jobs and HTTP steps in n8n, Make or Zapier use the REST API.

What is the Cloud Browser?

Your own Chrome that Cotlet runs for you in the EU, around the clock. You open it from the console, sign in to Fatture in Cloud yourself and press Enable for agents. Your agent's calls go through it, from its IP with its cookies, so Fatture in Cloud sees the browser you signed in with. Password saving is off and the profile is stored encrypted with AES-256-GCM.

Can my agent act without asking me?

Not on anything that reaches other people: create_invoice, send_einvoice, record_invoice_payment wait for your OK by default. You can switch that off per tool for scheduled runs.

Can the agent send invoices to SDI on its own?

It can, but by default you confirm each send_einvoice call, because a sent e-invoice is legally binding. It can run verify_einvoice or a dry run first, which sends nothing.

Should I use a Fatture in Cloud MCP server from GitHub instead?

Pick one if you want the code on your own computer and do not mind the upkeep: you install it, sign it in and fix it when Fatture in Cloud changes. Pick Cotlet if you want it hosted and kept working for you.

Can I use it in n8n, Make or Zapier?

Yes. Add https://cotlet.dev/mcp/v1 in n8n's MCP Client node, or call the REST endpoints from an HTTP step in Make or Zapier.

Who runs Cotlet?

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

Is Cotlet affiliated with Fatture in Cloud?

No. Cotlet is independent and not affiliated with Fatture in Cloud.

Give your agent access to Fatture in Cloud.

Free 7-day trial with 2,000 credits, no card needed.

Sign up free