The first MCP server for e-invoicing
Connect Claude, ChatGPT, or any MCP client to InvoiceXML and let your AI agent create, validate, convert, render, and read compliant Factur-X, ZUGFeRD, XRechnung, UBL, CII, and Peppol invoices, natively.
Your AI agent
Claude · ChatGPT · Cursor
InvoiceXML MCP
7 compliance standards
EN 16931 engine
Validated output
Get started
Two ways to run it
Use the managed server for instant setup, or self-host the open-source build on your own infrastructure.
Hosted
mcp.invoicexml.com
- Zero setup, fully managed and kept up to date
- Secure OAuth 2.1 sign-in, no API key to paste
- Always running on EU infrastructure
Add it as a remote connector
{
"mcpServers": {
"invoicexml": {
"url": "https://mcp.invoicexml.com"
}
}
}Self-hosted
Open source · your infrastructure
- Run it anywhere with your own API key
- Full control over networking and data flow
- Auditable, platform-independent code
- Switch between API-key and OAuth 2.1 modes
- No per-call fees beyond your own API usage
Clone and run
git clone https://github.com/InvoiceXML/invoicexml-mcp
cd invoicexml-mcp
export INVOICEXML_API_KEY=sk_live_...
dotnet run --project src/InvoiceXml.Mcp.HostAdd the connector
Point your AI client at mcp.invoicexml.com, or your own host.
Sign in
Authorize with OAuth, or drop in your API key when self-hosting.
Start invoicing
Ask your agent to create, validate, or convert an invoice. That's it.
What it is
E-invoicing your AI can actually use
The Model Context Protocol is the open standard for connecting AI assistants to real tools. InvoiceXML is the first to ship a complete e-invoicing MCP server, so an agent can handle EN 16931 compliance the same way it reads a file or searches the web. No glue code, no brittle screen-scraping, no maintaining a compliance library that breaks every time a standard changes.
Tools
Seven invoicing tools, one connection
Every tool is exposed to your agent with a clear name, description, and structured results.
Create Invoice
Generate a fully compliant e-invoice in any supported format from structured data.
create_invoice
Validate XML Invoice
Check a UBL, CII, or XRechnung document against EN 16931 XSD and Schematron rules.
validate_xml_invoice
Validate PDF Invoice
Validate a Factur-X or ZUGFeRD hybrid PDF and the XML embedded inside it.
validate_pdf_invoice
Render Invoice to PDF
Turn UBL, CII, or XRechnung XML into a clean, human-readable PDF preview.
render_invoice
Extract Invoice Data
Pull structured JSON or the embedded EN 16931 XML out of a hybrid PDF.
extract_invoice
Embed XML into PDF
Combine a PDF and a CII XML into a Factur-X or ZUGFeRD hybrid PDF/A-3.
embed_invoice
Convert Invoice Format
Transform between UBL, CII, XRechnung, Factur-X, and ZUGFeRD on demand.
convert_invoice
Compatibility
Works with every MCP client
MCP is an open standard, so InvoiceXML plugs into the tools your team already uses.
Claude
Desktop, claude.ai & Claude Code
ChatGPT
OpenAI custom connectors
Cursor
AI code editor
Windsurf
Agentic IDE
VS Code
GitHub Copilot agents
Any MCP client
Open protocol, no lock-in
Use cases
What teams build with it
Accounts-payable agent
An agent receives a supplier PDF, extracts the data, validates it against EN 16931, and converts it to the format your ERP expects, with no human in the loop.
Compliance copilot
Ask your assistant "is this invoice XRechnung-compliant?" and get a Schematron-level answer that names the exact business rules that failed.
On-demand conversion
Convert between Factur-X, ZUGFeRD, XRechnung, UBL, and CII inside a chat or an automated pipeline, without wiring up a single library.
Validation gate
Drop a validation step into any agent workflow so invoices are checked before they are sent, booked, or forwarded to a tax authority.
Build it into your product
Give your own AI features native e-invoicing without building and maintaining the compliance layer yourself.
Cross-border invoicing
Generate the right national format for each counterparty, Germany, France, or anywhere on the Peppol network, from one source document.
Formats
Every major e-invoicing standard
One server, the full EN 16931 family, covering the German, French, and EU-wide mandates. Your agent speaks every format your counterparties and tax authorities require.
The EU's core semantic model based on Directive 2014/55/EU that underpins every national format.
Cross-Industry Invoice XML. The UN/CEFACT standard used by ZUGFeRD and Factur-X.
Universal Business Language. Used by Peppol, XRechnung, and many national standards.
Germany's standard for modern B2B e-invoicing. PDF/A-3 with embedded CII XML.
France's equivalent, built on the same CII foundation. Required for B2G and expanding to B2B.
Germany's public sector standard. Pure UBL or CII XML, no PDF wrapper.
Pan-European e-delivery network. UBL-based, used for cross-border invoicing.
Archival PDF format with embedded XML, required for long-term storage compliance.
AI-extracted invoice as a validated JSON model. Every EN 16931 field ready to consume.
Security & privacy
Built for sensitive financial data
OAuth 2.1 + DCR
The hosted server uses OAuth with Dynamic Client Registration. Your client never sees a raw key.
Zero retention
Documents are processed in memory and deleted on response. No training on your data.
EU infrastructure
GDPR-aligned, HTTPS-only, hosted in the European Union.
Open & auditable
The server is open source and platform-independent. Read it, fork it, run it yourself.
FAQ
Frequently asked questions
What is the InvoiceXML MCP server?
It is a Model Context Protocol (MCP) server that exposes the InvoiceXML e-invoicing API to AI assistants. Once connected, an agent can create, validate, convert, render, and extract compliant invoices (Factur-X, ZUGFeRD, XRechnung, UBL, CII, Peppol) as native tools, without you writing integration code.
Which AI assistants does it work with?
Any MCP-compatible client. That includes Claude (Desktop, claude.ai, and Claude Code), ChatGPT custom connectors, Cursor, Windsurf, and VS Code with GitHub Copilot. MCP is an open standard, so there is no vendor lock-in.
Do I need to write any code?
No. With the hosted server at mcp.invoicexml.com you add it as a connector in your AI client and sign in with OAuth. Self-hosting requires only setting your API key and running the server.
What is the difference between hosted and self-hosted?
The hosted server (mcp.invoicexml.com) is fully managed, secured with OAuth 2.1, and requires zero setup. Self-hosting runs the same open-source server on your own infrastructure with your API key, giving you full control over networking and data flow.
Is my invoice data stored?
No. Documents are processed in memory and the result is returned immediately. Nothing is written to disk or retained after the response, and your data is never used to train models. Infrastructure is EU-based.
Which invoice formats are supported?
Factur-X, ZUGFeRD, XRechnung, UBL (including Peppol BIS Billing 3.0), CII, and the EN 16931 semantic model, with PDF/A-3 hybrid output for the embedded formats.
How does authentication work?
The hosted server uses OAuth 2.1 with Dynamic Client Registration, so your AI client signs in securely and never sees a raw API key. Self-hosted deployments authenticate with your InvoiceXML API key.
Ready to automate your invoices?
Start your 30-day free trial. No credit card required.
Get Started For Free