eleata e-invoice MCP server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@eleata e-invoice MCP server Validate this Peppol invoice XML"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
eleata e-invoice MCP server
Validate EU electronic invoices and explain validation error codes directly from your AI coding agent (Claude, Cursor, Copilot, …). It wraps the hosted eleata validation API plus a bundled offline error-code reference.
Never ship a broken invoice. When you ask your agent "is this FatturaPA / XRechnung / Peppol file valid?", it runs the official Schematron rules and gets back the rule id and the fix — before a rejection (an SdI scarto, a Chorus Pro refusal, a KSeF error) ever happens.
Tools
Tool | What it does | API key |
| Validate one invoice (Peppol BIS 3.0, EN 16931 UBL/CII, XRechnung 3.0.x, Factur-X/ZUGFeRD, UBL, CII). Returns valid/invalid + each rule id, explanation and fix. | required |
| List the formats eleata validates today + roadmap. | none |
| Explain one error code (e.g. | none |
Related MCP server: Fintom8 E-Invoice MCP Server
Setup
Get a free API key (200 validations/month, no card) at https://eleata.io/signup/.
Add the server to your agent's MCP config.
Claude Desktop / Claude Code (claude_desktop_config.json or .mcp.json)
{
"mcpServers": {
"eleata-einvoice": {
"command": "npx",
"args": ["-y", "eleata-einvoice-mcp"],
"env": { "EINVOICE_API_KEY": "your_free_key_here" }
}
}
}Cursor (~/.cursor/mcp.json)
Same block as above.
Example prompts
"Validate this XRechnung file and tell me what to fix" (paste the XML)
"What does FatturaPA error 00400 mean and how do I fix it?"
"Which e-invoice formats can you validate today?"
Privacy
validate_einvoice sends the invoice you pass to the hosted eleata API for validation. list_formats
and explain_error_code are local/offline (the error-code reference is bundled). See
https://eleata.io/privacy/.
Links
Web validator, CLI and GitHub Action: https://eleata.io
Error-code reference: https://eleata.io/error/
CLI (
npx @eleata/validate-einvoice): same API, for CI/CD
MIT licensed. Schematron engines: Mustang / phive. Schematron rules from CEN, OpenPeppol, KoSIT.
Available Tools
3 toolsexplain_error_codeA
Explain a single e-invoice validation error code (e.g. a FatturaPA SdI control like 00400, or an XRechnung rule like BR-DE-21) in plain English, with the suggested fix and an example. Works offline; no API key required.
Inputs: rule_id (required).
list_formatsA
List the EU e-invoice formats eleata can validate today, plus what is on the roadmap (e.g. FatturaPA, KSeF). No API key required.
Inputs: no named parameters.
validate_einvoiceA
Validate an EU electronic invoice against the official Schematron rules (Peppol BIS 3.0, EN 16931 UBL/CII, XRechnung 3.0.x, Factur-X/ZUGFeRD, UBL, CII). Returns whether it is valid and, for each violation, the rule id, a plain-English explanation and a suggested fix. Use this before a developer ships or transmits an invoice so a rejection (an SdI scarto, a Chorus Pro refusal, a KSeF error) is caught early. Requires EINVOICE_API_KEY (a free key from https://eleata.io/signup/).
Inputs: content (required), format, is_pdf.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: error code explanation, format listing, and invoice validation. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern: explain_error_code, list_formats, validate_einvoice.
3 tools is well-scoped for a focused e-invoice validation server, covering the core needs without excess.
The tool surface covers the full workflow: understanding formats, validating invoices, and interpreting errors. No obvious gaps for the domain.
Maintenance
Related MCP Connectors
Validate, generate & convert EU e-invoices (UBL, CII, XRechnung, Factur-X) — EN 16931 pre-validated.
EN 16931/XRechnung e-invoice validate+create, Peppol routing, EU VAT/EORI, sanctions, KYB. Free tier
Validate, generate, convert and extract EN 16931 e-invoices for businesses.
Validate XRechnung, Peppol BIS 3 and EN 16931 invoices with KoSIT; explain rules; check auto-repair
Related MCP Servers
AlicenseNot gradedqualityBmaintenanceInvoiceXML brings e-invoice compliance to your AI agent. Create, validate, convert, render, and extract structured invoices across UBL (Peppol BIS Billing 3.0, used worldwide), CII, Factur-X, ZUGFeRD, and XRechnung, all checked against the EN 16931 standard and official Schematron rules. Ask your assistant to generate a compliant invoice, validate one for errors, or convert between formats, with n5MIT- AlicenseNot gradedqualityDmaintenanceEnables autonomous agents to validate, audit, and correct e-invoices against European standards (EN16931) and Peppol regulations.1MIT
- AlicenseAqualityBmaintenanceValidates electronic invoices (XRechnung, ZUGFeRD, Factur-X, Peppol BIS, etc.) against authority-pinned rules and explains failures.229 npmMIT
- AlicenseNot gradedqualityDmaintenanceEU e-invoice validation, as a developer API. Check whether an electronic invoice conforms to EN 16931 — the European standard behind France, Germany, Belgium, Poland and the 2030 ViDA mandate — with a single REST call. Structured JSON errors mapped to the official BR-* business rules. No enterprise sales call required.MIT