FattureInCloud MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIC_COMPANY_ID | No | Default company ID. If unset, tools require an explicit company_id argument. | |
| FIC_ACCESS_TOKEN | Yes | A manual access token for Fatture in Cloud API v2. Required. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_companiesA | 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. |
| get_company_infoA | Look up company configuration needed to build documents: VAT types (IDs for items_list), payment methods, payment accounts, expense categories. |
| list_issued_documentsA | 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. |
| get_issued_documentA | Get a single issued document by ID with full details (entity, line items, payments, amounts). |
| list_received_documentsA | 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. |
| get_received_documentA | Get a single received document (expense, passive credit note...) by ID with full details. |
| create_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. |
| update_issued_documentA | 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. |
| delete_issued_documentA | Permanently delete an issued document by ID. Irreversible. |
| create_received_documentA | 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. |
| update_received_documentA | 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. |
| delete_received_documentA | Permanently delete a received document by ID. Irreversible. |
| upload_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. |
| delete_document_attachmentA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.