# fattureincloud-mcp [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://github.com/aringad/fattureincloud-mcp  
**GitHub Stars:** 20  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/fattureincloud-mcp

## Description
Italian e-invoicing with Fatture in Cloud. Create, send to SDI, manage clients.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "fattureincloud-mcp": {
    "command": "uvx",
    "args": ["fattureincloud-mcp"],
    "env": {
      "FIC_ACCESS_TOKEN": "",
      "FIC_COMPANY_ID": ""
    }
  }
}
```

**Requires environment variables:** `FIC_ACCESS_TOKEN`, `FIC_COMPANY_ID` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What fattureincloud-mcp MCP server does

The fattureincloud-mcp MCP server gives an MCP-compatible client access to a connected FattureInCloud company. It supports reading and modifying issued billing documents, managing clients, handling supplier expenses, and checking company-level information.

Issued-document tools cover invoices, credit notes, and proformas. An agent can list documents by year or month, retrieve full details, obtain PDF and web links, create drafts, update drafts, duplicate invoices, delete draft documents, and convert a proforma into a draft electronic invoice. The server also exposes invoice numbering checks and yearly figures for revenue, collections, outstanding amounts, costs, and margin.

For Italian electronic invoicing workflows, `send_to_sdi` submits an invoice or credit note to the Sistema di Interscambio, while `get_invoice_status` checks its e-invoice status. `send_email` can send a courtesy copy when a sender email is configured.

## How it works

The server runs on the user's machine and sends API requests directly to `api-v2.fattureincloud.it`. It does not route billing data through Mediaform or another intermediary. Authentication uses a FattureInCloud manual API token together with the numeric company ID associated with the selected company.

Client lookups and the cost-center registry are cached locally as plaintext JSON. The default cache location is `~/.fattureincloud-mcp/cache/`, with data scoped by company and a 24-hour lifetime. Remove that directory to force a refresh, or set `FIC_CACHE_DISABLED=1` to turn caching off. The cache is not required for the tool interfaces to change.

Cost and revenue centers share one FattureInCloud registry. Existing labels can be assigned to issued documents through `revenue_center` and to supplier expenses through `cost_center`. Unknown labels produce an error that includes the valid labels.

## Setup and configuration

The MCPB installation is intended for Claude Desktop: download the `fattureincloud.mcpb` release file and install it through the desktop application's extension flow. During setup, provide the API token, company ID, and optionally the sender email.

For other MCP clients or Claude Code, install the `fattureincloud-mcp` package from PyPI and configure the server with `python -m fattureincloud_mcp`. Set `FIC_ACCESS_TOKEN` and `FIC_COMPANY_ID`; both are required. `FIC_SENDER_EMAIL` is required only when using courtesy-copy email delivery. `FIC_CACHE_DIR` can override the cache path, and `FIC_CACHE_DISABLED` accepts `1` to disable caching.

Create the manual token in FattureInCloud under Settings → API and Integrations, granting the permissions needed by the tools. The company ID appears in the URL after `/c/` after selecting a company. Restart the MCP client after changing its configuration.

## Limitations and notes

This is an unofficial integration and is not affiliated with or endorsed by TeamSystem S.p.A. Marking payments as paid is intentionally not exposed because the FattureInCloud API requires a payment account that the SDK cannot reliably retrieve; that action must be completed in the FattureInCloud web panel.

Invoice duplication can fail for some client configurations. The documented workaround is to duplicate the invoice manually in the FattureInCloud web panel. The local cache is stored as plaintext JSON, so its files should be protected like other local billing data. Credentials are kept in the user's environment or MCP client configuration and are not sent anywhere except FattureInCloud.

_Full upstream README: https://allmcps.com/mcp/fattureincloud-mcp/readme_