About EU E-Invoice API
Validate, parse and generate EU e-invoices: XRechnung, ZUGFeRD, Peppol BIS, KSeF, FatturaPA
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y @einvoiceapi/mcpEINVOICE_API_BASE_URLAPI base URL (the gateway shown in the developer portal)EINVOICE_API_KEYSecretYour API key from the developer portal (free plan available)Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
3Saved tool list · updated 3d ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| xml | string | No | The invoice XML as text (CII or UBL). |
| path | string | No | Local path of the invoice file (XML, or PDF with embedded XML). |
| base64 | string | No | The invoice file (XML or PDF), base64-encoded. |
| preview | boolean | No | Validate against the upcoming rule sets (published but not yet mandatory) instead of the rules in force, to check early whether invoices will still pass. Paid plans only. |
| rulesets | array | No | Pin rule-set versions instead of the defaults, e.g. ["[email protected]"]. See the API's GET /v1/formats. |
Details
The maintainer has not added details yet. Check the README in the repository.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.