Factur-X e-invoicing MCP Server

by leborgneantoine Your server? Claim it

answering

Factur-X e-invoicing is answering right now. Last checked 8 min ago. It exposes 4 tools.

Generate, validate and read Factur-X / EN 16931 e-invoices (France, EU): PDF/A-3, CII, UBL 2.1.

Uptime history 9 days of history

9 days agonow

100.0%

Uptime 24h

184 of 184 checks

Tools

read from the server

357 ms

Response time

average over 24h

authentication required

Access

streamable-http

What changed 8

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 3 September 2026. No other catalogue keeps this.

3 Sep 4 tool descriptions were rewritten embed_xml, extract_invoice, generate_invoice and 1 more

3 Sep 4 tools changed the parameters they ask for embed_xml, extract_invoice, generate_invoice and 1 more

Nothing serious here today

Today is the operative word: we check Factur-X e-invoicing every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add facturx --transport http https://facturx-api.fly.dev/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "facturx": {
      "url": "https://facturx-api.fly.dev/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.facturx]
url = "https://facturx-api.fly.dev/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "facturx": {
      "url": "https://facturx-api.fly.dev/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "facturx": {
      "url": "https://facturx-api.fly.dev/mcp"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

embed

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.

extract

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.

generate

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.

validate

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.

Endpoints

URL	Transport	State	Latency	Checked
https://facturx-api.fly.dev/mcp	streamable-http	needs key	565 ms	9 min ago
https://facturx.orvel.dev/mcp	streamable-http	answering	183 ms	8 min ago

Alternatives to Factur-X e-invoicing

same job, measured the same way

Invoicehub

by invoicehub

Validate, generate & convert EU e-invoices (UBL, CII, XRechnung, Factur-X) — EN 16931 pre-validated.

4 tools answering

Facturx Toolkit

by cedrickouma

Validate, extract, repair and generate French Factur-X / EN16931 invoices via AgentForge API

31 installs/wk answering

Einvoicewiz

by einvoicewiz

Generate & validate EN 16931 e-invoices (Factur-X, ZUGFeRD, XRechnung); verification certificates

7 tools answering

Fakturai — German E-Invoice (ZUGFeRD / Factur-X / E-Rechnung)

by fakturai

KoSIT-verified German e-invoices: generate & validate ZUGFeRD, Factur-X, XRechnung, EN 16931.

3 tools answering

Tallystick

by tally-stick

Read, validate and write e-invoices on your own machine. XRechnung, ZUGFeRD, Factur-X, UBL, CII.

100 installs/wk local only

Eleata e-Invoice Validator

by hernaninverso

Validate EU e-invoices (Peppol, XRechnung, Factur-X, UBL, CII) and explain error codes.

32 installs/wk local only

Gofact

by kolapsis

Creates compliant French e-invoices locally: Factur-X PDF/A-3 with EN 16931 CII XML, legal numbering

local only

Attestwire

by attestwire

EN 16931: validate invoice data or a UBL/CII file, emit UBL or CII XML. XRechnung, Peppol. Not PDF.

46 installs/wk 9 tools answering

Factur-X e-invoicing — questions

Answers built from our own checks of this server.

What can Factur-X e-invoicing do?

It exposes 4 tools, read directly from the server on our last check. Among them: embed_xml, extract_invoice, generate_invoice, validate_invoice. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Factur-X e-invoicing working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 184 of 184 checks got a reply (100.0%), average response time 357 ms. The bar chart above shows every period we have measured.

How do I connect Factur-X e-invoicing?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.

Does Factur-X e-invoicing need an API key?

Yes. Every time we knock, Factur-X e-invoicing answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is Factur-X e-invoicing?

It answers our handshake in 357 ms on average, which is faster than 46% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.