FattureInCloud MCP
It lets an MCP client read and manage Fatture in Cloud issued and received documents, company configuration data, and document attachments.
Discover accessible companies and use
company_iddefaults.Look up VAT types, payment methods/accounts, and received-document expense categories.
List/get issued documents (invoices, quotes, proformas, receipts, credit notes, etc.) with filters, sorting, pagination, and basic/detailed fieldsets.
Create, partially update, and irreversibly delete issued documents.
List/get received documents (expenses, passive credit notes, etc.) with the same filtering/pagination options.
Create, partially update, and irreversibly delete received documents.
Upload local files as attachments and bind them to documents via
attachment_token.Delete a document’s attachment, with a caveat that the FIC API may return 500 on this operation.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@FattureInCloud MCP list my issued invoices from the last month"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
FattureInCloud MCP
MCP (Model Context Protocol) server for the Fatture in Cloud API v2. Lets Claude (Code / Desktop / any MCP client) read and manage (CRUD) issued documents (invoices, credit notes, quotes...) and received documents (expenses, passive credit notes...).
Two transports over the same tools: stdio as a local child process, and Streamable HTTP for a shared deployment that keeps no credentials of its own.
Tools
Tool | Description |
| Companies accessible with the token (source of |
| Config lookups: VAT types, payment methods/accounts, expense categories |
| Paginated list of issued documents, one type per call (default |
| Full detail of a single issued document |
| Paginated list of received documents (default |
| Full detail of a single received document |
| The "documenti da registrare" queue: SDI e-invoices (and emailed/uploaded documents) waiting to be registered |
| Full detail of a single pending document |
| Create an invoice, credit note, quote... |
| Update an issued document (partial: only the fields passed) |
| Delete an issued document (irreversible) |
| Create an expense or other received document |
| Update a received document (partial) |
| Delete a received document (irreversible) |
| Upload a file from an https |
| Remove a document's attachment (FIC API currently 500s here, see docs) |
See docs/api.md for parameters, payload shapes and API quirks. List tools support:
q— Fatture in Cloud filter language, e.g.date >= '2026-01-01' and date <= '2026-06-30',entity.name like '%acme%',amount_gross > 1000sort— e.g.-date(descending)page/per_page(min 5, max 100) — responses includecurrent_page,last_page,totalfieldset—basic(compact, default for lists) ordetailed(includes line items)
Related MCP server: Pacioli
Setup
npm install
npm run buildAuthentication
Two values, wherever they come from:
FIC_ACCESS_TOKEN(required) — a manual access token: generate it from the Fatture in Cloud developer area selecting the read scopes for issued and received documents. Manual tokens never expire (revocable from the same page).FIC_COMPANY_ID(optional) — default company ID; if unset, tools require an explicitcompany_idargument (discover it withlist_companies).
Over stdio they are environment variables of the server process. Over HTTP they are the X-FIC-Token and X-FIC-Company headers of each request, so the deployed instance stores neither.
Configuration templates for Claude Code, Claude Desktop and opencode, local stdio and remote HTTP, are in examples/.
Claude Code
A project-scoped .mcp.json (gitignored) holds the credentials. From any other directory:
claude mcp add --scope user fattureincloud -e FIC_ACCESS_TOKEN=<token> -e FIC_COMPANY_ID=<id> -- node <repo>\dist\index.jsClaude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"fattureincloud": {
"command": "node",
"args": ["<repo>\\dist\\index.js"],
"env": {
"FIC_ACCESS_TOKEN": "<token>",
"FIC_COMPANY_ID": "<id>"
}
}
}
}Remote (Streamable HTTP)
dist/http.js serves the same tools over HTTP and takes the credentials from the X-FIC-Token and X-FIC-Company request headers instead of the environment, so the host running it stores no secret. ./scripts/deploy.ps1 (or ./scripts/deploy.sh) installs it as a systemd service on a remote machine — see docs/deploy.md.
Extending
The API surface is small on purpose. To add endpoints (clients, suppliers, products, receipts, taxes, cashbook...), follow the pattern in src/server.ts: one registerTool per action calling ficGet from src/fic.ts. The full OpenAPI spec lives at fattureincloud/openapi-fattureincloud.
Available Tools
14 toolscreate_issued_documentCreate issued documentA
Create an issued document (invoice, credit note, quote...). Requires entity and items_list; look up VAT type and payment method/account IDs with get_company_info first. Returns the created document.
Inputs: data (required), company_id.
create_received_documentCreate received document (expense)A
Create a received document (expense, passive credit note...). Requires description, entity, date, amounts (amount_net/amount_vat/amount_gross) and a payments_list covering the total. Returns the created document.
Inputs: data (required), company_id.
delete_document_attachmentDelete document attachmentADestructiveIdempotent
Remove the attachment from an issued or received document (the document itself is untouched). Irreversible. Note: the FIC API has been observed returning 500 on this endpoint; deleting the document or replacing the attachment via update (new attachment_token) are alternatives.
Inputs: target (required), document_id (required), company_id.
delete_issued_documentDelete issued documentADestructiveIdempotent
Permanently delete an issued document by ID. Irreversible.
Inputs: document_id (required), company_id.
delete_received_documentDelete received document (expense)ADestructiveIdempotent
Permanently delete a received document by ID. Irreversible.
Inputs: document_id (required), company_id.
get_company_infoGet company configuration listsARead-only
Look up company configuration needed to build documents: VAT types (IDs for items_list), payment methods, payment accounts, expense categories.
Inputs: resource (required), company_id.
get_issued_documentGet issued documentARead-only
Get a single issued document by ID with full details (entity, line items, payments, amounts).
Inputs: document_id (required), fieldset, company_id.
get_received_documentGet received document (expense)ARead-only
Get a single received document (expense, passive credit note...) by ID with full details.
Inputs: document_id (required), fieldset, company_id.
list_companiesList companiesARead-only
List the Fatture in Cloud companies accessible with the configured token. Returns id, name and type for each company; the id is the company_id used by the other tools.
Inputs: no named parameters.
list_issued_documentsList issued documentsARead-only
List issued documents (invoices, credit notes, quotes, proformas, receipts...) for a company. One document type per call; defaults to invoices. Paginated: check current_page/last_page/total.
Inputs: q, page, sort, type, +3 more.
list_received_documentsList received documents (expenses)ARead-only
List received documents for a company: expenses (spese), passive credit notes, passive delivery notes, self invoices. Defaults to expenses. Paginated: check current_page/last_page/total.
Inputs: q, page, sort, type, +3 more.
update_issued_documentUpdate issued documentADestructiveIdempotent
Update an existing issued document. Only the fields provided in data are changed. Fetch the document first with get_issued_document to see its current state.
Inputs: data (required), document_id (required), company_id.
update_received_documentUpdate received document (expense)ADestructiveIdempotent
Update an existing received document. Only the fields provided in data are changed. Fetch the document first with get_received_document to see its current state.
Inputs: data (required), document_id (required), company_id.
upload_attachmentUpload document attachmentA
Upload a local file (PDF, image, XML, zip...) as an attachment for an issued or received document. Returns an attachment_token: pass it as data.attachment_token in a create/update tool to bind it to a document. Unbound tokens expire after a while, so upload right before creating/updating.
Inputs: target (required), file_path (required), filename, company_id.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 14 tools
Each tool targets a distinct resource (issued document, received document, company, company info, attachment) and action (get, create, list, update, delete, upload, remove). The parallel issued/received sets are clearly separated by document type, and the attachment tools are distinct. No two tools could be confused for the same purpose.
The core document tools follow a consistent verb_noun pattern: get_issued_document, create_received_document, list_issued_documents, etc. Minor deviations exist: 'get_company_info' and 'delete_document_attachment' use slightly different structures (info suffix, document_attachment compound). Overall, the pattern is predictable and readable.
14 tools is well-scoped for a document management server. It covers two document types with full CRUD plus list, company management, configuration lookup, and attachment handling. Each tool has a clear role, and the count is not excessive or overly sparse.
The toolset provides complete CRUD and listing for both issued and received documents, plus company info and attachment upload/delete. A notable gap is the lack of a download attachment (or document PDF) function, which would be useful for a full document workflow, but the core lifecycle is covered.
Related MCP Connectors
Fatture in Cloud MCP server for ChatGPT, Claude and any AI agent: create invoice, send to SDI, add client, record expense and list unpaid invoices in your own Fatture in Cloud account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Fatture in Cloud yourself; Cotlet does not store your password and you need no Fatture in Cloud API key. About the official Fatture in Cloud 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. Setup and FAQ: https://cotlet.dev/integrations/fatture-in-cloud-api-mcp-server
MCP server for Quaderno — tax-rate calculation, invoices, contacts, products, receipts & expenses.
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
MCP server for Codat — companies, connections, invoices, bills and financial statements.
Related MCP Servers
- AlicenseBqualityBmaintenanceA Model Context Protocol (MCP) server for the Holded Invoice API. This server allows AI assistants like Claude to interact with Holded's invoicing, contacts, products, and more.119171 npm20MIT
- AlicenseAqualityDmaintenanceMCP server that connects Claude Code to the Holded API for natural language financial, accounting, and invoicing queries, with built-in Spanish PGC context.132Apache 2.0
- FlicenseNot gradedqualityDmaintenanceAn MCP server for the FreshBooks API that lets Claude read and manage invoices, clients, expenses, projects, services, payments, and time entries.-
- AlicenseAqualityDmaintenanceMCP server for interacting with Aruba Fatturazione Elettronica API, enabling users to manage electronic invoices with Claude, including sending invoices to SDI, searching, downloading, and retrieving invoice details and notifications.67MIT