Factur-X e-invoicing
Generate, validate and read Factur-X / EN 16931 e-invoices (France, EU): PDF/A-3, CII, UBL 2.1.
What it can do
What data it sees
Do you need an account
An API key from the service settings is required
Generate, validate and read Factur-X / EN 16931 e-invoices (France, EU): PDF/A-3, CII, UBL 2.1.
How to connect
How to connect Factur-X e-invoicing to Claude
The server address to paste into Claude settings:
https://facturx.orvel.dev/mcp
- Open Claude (claude.ai or the desktop app).
- Go to Settings → Connectors.
- Click Add custom connector.
- Paste the server address copied below into Remote MCP server URL and click Add.
- In a chat, click + → Connectors and switch the new connector on.
Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.
Authorization
After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.
How to connect Factur-X e-invoicing to ChatGPT
The server address to paste into ChatGPT settings:
https://facturx.orvel.dev/mcp
- Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
- Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
- Open Settings → Connectors and click Create.
- Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
- Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
- In a new chat open + → Apps/Connectors and enable the connector.
OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.
Authorization
On first use ChatGPT opens the service's sign-in window. Sign in and approve access.
How to connect Factur-X e-invoicing to Cursor
The server address to paste into Cursor settings:
https://facturx.orvel.dev/mcp
Fastest: click Open in Cursor below and confirm the prompt.
Manually:
- In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
- Paste the JSON copied below into
~/.cursor/mcp.json(per project:.cursor/mcp.jsonin the repo root). - Save the file. The server appears in the MCP list; authorize it there if asked.
Authorization
If the service needs sign-in, an authorize button appears next to the server in the MCP list.
Server tool list (4)
Raw names from tools/list. Only developers need these.
| generate_invoice | Create a new, compliant e-invoice (Factur-X PDF/A-3, CII XML or UBL XML) from structured invoice data. Use when you have the invoice content (parties, lines, dates) and need the document. Do not use when you already have a visual PDF and a Factur-X XML to combine: call embed_xml. To check a document you did not create here, call validate_invoice; to read one, call extract_invoice. The result is validated (XSD + schematron for `check`) before it is returned; on failure the tool returns an error listing the failing rule ids (e.g. BR-CO-10, BR-FR-01) so you can fix the input and retry. Nothing is stored. Returns a text summary (number, totals, warnings) plus the document as an embedded resource: base64 PDF for facturx-pdf, XML text for cii-xml / ubl-xml. |
| embed_xml | Combine a visual PDF you already have with a Factur-X (CII) XML into one PDF/A-3 Factur-X invoice. Use when the PDF is produced by your own system and you only need the compliant hybrid file. Do not use to create an invoice from data: call generate_invoice, which renders the PDF too. The XML is validated first and rejected with rule ids if it fails. Nothing is stored. Returns a text summary plus the PDF/A-3 as a base64 embedded resource. |
| validate_invoice | Check whether an existing e-invoice (Factur-X PDF, CII or UBL XML) is compliant, and report why not. Use on any document you did not produce with generate_invoice (supplier invoices, files from another system) or to re-check after a fix. Do not use to read the invoice content: call extract_invoice. Runs XSD then the EN 16931 schematron (plus French rules for fr-ctc). Read-only, nothing stored. Returns {valid, profile, findings[]} where each finding has the rule id (e.g. BR-CO-10), severity and message; a non-compliant document is a normal result, not an error. |
| extract_invoice | Read an e-invoice and return its business data as JSON: number, dates, seller, buyer, totals, VAT breakdown, lines. Use to get the content of a received invoice (Factur-X PDF, CII or UBL XML) for bookkeeping, matching or summaries. Does not judge compliance: call validate_invoice for that. Read-only, nothing stored. Returns {profile, fields{...}} and, with include_xml, the XML text. |