create_invoiceLABSCO SUMMARY
The European e-invoice formats, without learning their XML.
Factur-X, XRechnung and Peppol are the kind of standards where the specification is long and the acceptance rules are unforgiving. This puts the format work behind an API call, and the same server runs on your infrastructure or InvoiceXML's depending on how you want the credentials held.
What it is
The InvoiceXML API exposed to agents. The same build runs two ways: on your own machine against a single API key, or hosted by InvoiceXML with OAuth and dynamic client registration.
What you get
- The Factur-X and ZUGFeRD hybrid invoice formats
- XRechnung, the German public-sector invoice standard
- UBL and CII, the two underlying XML syntaxes
- Peppol BIS Billing 3.0, the profile used for cross-border exchange
- One deployment shape you choose at startup — self-hosted with a key, or hosted with OAuth
Requirements
Self-hosted, an InvoiceXML API key placed in the environment or in appsettings.json; hosted, an account authorized over OAuth. The host serves the MCP endpoint over HTTP, with a health check beside it.
Setup effort
Add the hosted endpoint, then sign in — paste it into your client, then approve the OAuth sign-in
USE CASES
01
Issuing an invoice a German public buyer will accept
Produce the document in the format the buyer's portal requires rather than sending a PDF that gets bounced back weeks later.
02
Turning invoice data into a hybrid PDF
Factur-X and ZUGFeRD carry structured XML inside a readable PDF, so one file serves both the human approving it and the system booking it.
03
Getting an invoice onto the Peppol network
Work in the BIS Billing 3.0 profile that cross-border exchange expects, instead of mapping your own fields to it by hand.
04
Keeping the credentials on your own infrastructure
Run the same server yourself with one API key in the environment. The SDK inside it never sees credentials — the host attaches them in the HTTP pipeline.
3 tools
Listed in project docs. Your client may show a different list.
validate_xml_invoicevalidate_pdf_invoiceBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation.
Requires
.NET 10 SDK (to run your own copy)
Optional
INVOICEXML_API_KEY in your environment
Where it runs
The documented client connects to a hosted endpoint.
INSTALLATION
Connect your client
Server setup
Setup
TERMINAL
git clone https://github.com/InvoiceXML/invoicexml-mcp
cd invoicexml-mcp
dotnet user-secrets --project src/InvoiceXml.Mcp.Host set "Mcp:ApiKey:Value" "<YOUR_KEY>"
dotnet run --project src/InvoiceXml.Mcp.HostYour own copy then serves its MCP endpoint at http://localhost:5004/ — point your client there instead of the hosted address https://mcp.invoicexml.com.
Hosted endpoint
ENDPOINT URL
https://mcp.invoicexml.comAdd this hosted endpoint to your MCP client, then sign in.
MCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"invoicexml": {
"url": "https://mcp.invoicexml.com"
}
}
}
