Categories › Data & Databases › Files, spreadsheets, CSV & PDFs
Validate, generate, convert and extract EN 16931 e-invoices for businesses.
Remote server: your requests and data go to mcp.electronic-invoice.app. Claude Code: claude mcp add --transport http electronic-invoice-api https://mcp.electronic-invoice.app/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
validate_invoice — Validate an existing e-invoice file without changing it. Accepts UBL Invoice/CreditNote XML, UN/CEFACT CII XML, FatturaPA or KSeF FA(3) XML,generate_invoice — Create a new e-invoice file from structured JSON. Builds XRechnung UBL/CII or a ZUGFeRD/Factur-X PDF, validates the result with the same rulconvert_invoice — Convert an existing e-invoice from UBL to CII, CII to UBL, or XML to a ZUGFeRD/Factur-X PDF. Also accepts a ZUGFeRD/Factur-X PDF and convertextract_invoice — Read data from an existing UBL/CII XML or ZUGFeRD/Factur-X PDF. Returns JSON business terms keyed by BT/BG numbers, CSV with one row per linopen_invoice_check — Open an upload field in the chat where the user chooses an invoice PDF or XML file. The file goes straight from the field to this server's vget_service_status — Check whether the Electronic Invoice API is up and which rule set versions it currently runs. Calls GET /v1/health without an API key. Free,get_usage_limits — Return the technical limits of the Electronic Invoice API: rate limits, concurrency limits, request body size limits, and which HTTP status Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.