The invoicing rules of 31 countries, inside your AI assistant.
VAT rates, e-invoicing mandates, formats and required fields for the EU-27 plus the UK, Norway, Switzerland and Iceland. One install, and your assistant answers from the rules instead of from memory.
Product details
- Type
- Open source · MIT
- Status
- Beta · since 2026
- Works in
- Claude · Cursor · VS Code
- Stack
- Node · TypeScript
- Links
- GitHub npm euinvoice.dev
- Install
-
npx euinvoice-mcp
Why it exists
European invoicing is fragmented. Every country has its own VAT rates, its own e-invoicing mandates, its own formats and its own required fields. Germany wants XRechnung, Italy routes everything through SDI, Poland through KSeF, and what a language model remembers is always a few changes behind.
I build connectors between AI assistants and business software, and invoicing is exactly the kind of place where an assistant has to know rather than guess. This server is the structured knowledge behind such a connector. Open source, so you can check the rules and the edge cases yourself.
How it works
One question, the right answer.
No trawling through tax websites. You describe the situation, the assistant pulls the rules from the server and answers with rate, format and required fields.
I sell software from the Netherlands to a company in Germany. What VAT do I charge, and what does the invoice need to look like?
Reverse charge. You charge 0% and state the reverse charge on the invoice; your customer in Germany accounts for the VAT.
- VAT: reverse charge, article 196 VAT Directive
- On the invoice: both VAT numbers and the words "reverse charge"
- Format: XRechnung 3.0 or ZUGFeRD/Factur-X; Peppol BIS 3.0 also works
- Note: German businesses must be able to receive e-invoices since 1 January 2025
Want the required fields for this invoice as well?
Yes, and compare it with Belgium.
Belgium mandates B2B e-invoicing through Peppol from 1 January 2026. Germany has had to receive since 2025 and must send from 2027. The fields for your German invoice are below.
What it does
Rates
VAT rates and OSS
Standard, reduced, super-reduced and parking rates per country, or every standard rate side by side. Plus the thresholds and rules of the One-Stop Shop for cross-border B2C.
- get_vat_rates
- list_vat_rates
- get_oss_rules
Mandates
E-invoicing and reverse charge
Which mandates apply per country for B2G, B2B and B2C, through which system and from when. And when to apply reverse charge, and what to put on the invoice.
- get_einvoicing_requirements
- get_b2b_mandate_status
- get_reverse_charge_rules
Formats
Formats and required fields
UBL, CII, Factur-X, XRechnung, FatturaPA and Peppol BIS: what they are and where they apply. The required fields per country and transaction type, EN 16931 with its national extensions, and two countries side by side.
- get_invoice_format
- validate_invoice_fields
- get_en16931_info
- compare_countries
When it becomes mandatory
Every country its own date, its own system.
This is the kind of answer the server gives: per country the system, the format and the date from which B2B e-invoicing is mandatory. Six of the 31 countries, as a taster.
Install
One block in your configuration, and done.
No account, no cloud. The server starts through npx whenever your assistant needs it, and runs on your own machine.
-
Pick your assistant
Claude Desktop, Cursor or VS Code. Any client that speaks MCP works.
-
Paste the block on the right
Into your assistant's configuration file. For Cursor and VS Code without the outer mcpServers layer.
-
Restart and ask
That is all. Start with "What are the VAT rates in Germany?"
claude_desktop_config.json
{
"mcpServers": {
"euinvoice": {
"command": "npx",
"args": ["-y", "euinvoice-mcp"]
}
}
}
MCP settings of Cursor or VS Code
{
"euinvoice": {
"command": "npx",
"args": ["-y", "euinvoice-mcp"]
}
}
What you can ask
Plain sentences, precise answers.
You do not need to know any tool names. These are questions you can ask exactly like this.
-
“What are the VAT rates in Germany?”
-
“What e-invoicing format do I need for B2G invoices in Italy?”
-
“Compare the invoicing requirements of France and Germany.”
-
“When does the B2B e-invoicing mandate start in Poland?”
-
“What fields are required on an invoice to a customer in Spain?”
-
“Explain the reverse charge mechanism for intra-EU B2B services.”
What is comingInvoice generation and XML validation are on the roadmap. Version 0.2 builds UBL 2.1 and CII from structured input, 0.3 validates existing files against EN 16931. Until then this is a reference server, not a generator.
See the roadmap
What is MCPAn open standard that lets AI assistants use tools. Think of it as a plug: you install one server and every assistant that speaks MCP can work with it. I build the same technique for organisations on their own systems.
See the ConnectorBuilt here, run here.
What I build here for myself, I also build for organisations that want to take AI beyond the pilot.