# toomasgutman-blip/facturolia-mcp [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://github.com/toomasgutman-blip/facturolia-mcp  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/toomasgutman-blip-facturolia-mcp

## Description
Read and validate European e-invoices (Factur-X, ZUGFeRD, XRechnung, UBL, CII) against EN 16931 and flag Factur-X PDF vs embedded XML mismatches.

## Tools
Capabilities this server exposes over MCP:

- **read_invoice** — Full contents: parties, dates, lines, VAT breakdown, totals, IBAN, plus the EN 16931 check
- **check_invoice** — The compliance verdict and anomalies only, for "is this invoice correct?"

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What toomasgutman-blip/facturolia-mcp MCP server does

toomasgutman-blip/facturolia-mcp MCP server lets an MCP-compatible assistant read and check European electronic invoices. It accepts PDF and XML files and supports Factur-X, ZUGFeRD, XRechnung, UBL, and CII formats. The service extracts business and payment information, then reports a consistency result based on EN 16931.

For Factur-X documents, the visible PDF and embedded structured XML represent separate views of the invoice. The resulting analysis can expose differences between them instead of relying only on the rendered page. The server is intended for inspection and checking; it does not create, send, or legally transmit invoices, and it is not a replacement for an accredited platform in France.

## How it works

The server runs as a small Python MCP process and exposes two tools. Both tools receive one argument: `path`, which must be an absolute path to a `.pdf` or `.xml` file.

- `read_invoice` returns the invoice contents, including parties, dates, line items, VAT details, totals, IBAN, and the EN 16931 result.
- `check_invoice` returns only the compliance verdict and detected anomalies, which is useful when the question is whether an invoice is correct.

When either tool is called, the file is uploaded to the Facturolia API for analysis. According to the project documentation, processing happens in memory, the invoice is discarded immediately, and its contents are excluded from technical logs. The API servers are located in the European Union. This remains external processing rather than local analysis.

## Setup and configuration

toomasgutman-blip/facturolia-mcp requires Python 3.10 or newer and has no package dependencies. Download `facturolia_mcp.py`, obtain a Facturolia API key, and register the script in the MCP client configuration. A Claude Desktop entry uses the Python command, the absolute script path, and the `FACTUROLIA_API_KEY` environment variable. Restart the client after adding the configuration.

The available settings are:

- `FACTUROLIA_API_KEY`: required API credential.
- `FACTUROLIA_LANG`: response language, either `en` or `fr`; defaults to `en`.
- `FACTUROLIA_BASE_URL`: API base URL, defaulting to `https://facturolia.fr`. HTTPS is required except for localhost testing, and the key is not sent to an insecure non-local HTTP URL.

French responses use French date and label conventions, while the tool descriptions remain in English. The repository states that its tests use only the Python standard library and can run with `python -m unittest discover -s tests`.

## Tools and capabilities

Use `read_invoice` when the assistant needs a plain-language representation of an invoice. Its output can include supplier and customer information, invoice dates, payment details, line calculations, VAT breakdowns, totals, and the EN 16931 check.

Use `check_invoice` for a narrower validation response. It reports the compliance outcome and anomalies without returning the full invoice contents. Both tools are limited to PDF and XML inputs, with a maximum file size of 10 MB.

## Limitations and notes

toomasgutman-blip/facturolia-mcp is unsuitable for policies that prohibit uploading invoices to an external service. The project recommends using the API within your own network instead, or not using this server, when that restriction applies. It also does not perform invoice issuance or transmission and should not be treated as a complete legal or regulatory compliance solution.

_Full upstream README: https://allmcps.com/mcp/toomasgutman-blip-facturolia-mcp/readme_