Invoicehub

dev.invoicehubPublished by invoicehub.devOfficial publisherv1.3.0Updated Oct 25, 2026

Validate, generate & convert EU e-invoices (UBL, CII, XRechnung, Factur-X) — EN 16931 pre-validated.

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that lets an assistant validate, generate and convert EU e-invoices against the EN 16931 standard.

What you can do
Validate an EU e-invoice XML string against the official EN 16931 Schematron, auto-detecting UBL 2.1 or UN/CEFACT CII and applying XRechnung 3.0 rules when declared. Generate an EN 16931-conformant UBL 2.1 invoice from seller, buyer and line fields, self-validated before return. Convert an e-invoice between formats through the shared EN 16931 model, validating the result before returning it. List the e-invoice formats supported today and those on the roadmap.
When to use it
Useful when an assistant must check whether an EU e-invoice is compliant, draft a standards-conformant invoice from structured data, or move a document between UBL, CII, XRechnung and Factur-X style formats without shipping an unchecked result.
Requirements
A remote streamable HTTP endpoint at the provider's API host; no package, environment variables or headers are declared. The manifest declares no authentication, so no credentials appear to be needed.
Before you install
Invoice content, including seller and buyer details and VAT identifiers, is sent to a third-party service for validation and conversion. Generated and converted documents are returned as new output, so review them before issuing or filing them.

Installation

In SourceWeft

  1. Open Invoicehub in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.invoicehub%2Finvoicehub/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "invoicehub": {
      "type": "http",
      "url": "https://api.invoicehub.dev/mcp"
    }
  }
}

README

This repository has no README.

Tools

4

validate_invoice

Validate an EU e-invoice

Validate an EU e-invoice XML string against the official EN 16931 Schematron. Accepts either syntax — UBL 2.1 (Invoice or CreditNote) or UN/CEFACT CII — and auto-detects which. A document declaring the XRechnung 3.0 CustomizationID is additionally checked against KoSIT's XRechnung delta ruleset. Returns whether it is valid and any failing BR-* / BR-DE-* business rules.

Parametersxmlrequired

generate_invoice

Generate an EU e-invoice

Generate an EN 16931-conformant UBL 2.1 invoice from structured fields. The result is self-validated before being returned. Provide seller, buyer, and at least one line; for standard-rated (category "S") lines include a vatRate and the seller vatId.

ParametersbuyerrequiredlinesrequiredsellerrequireddueDatepaymentcurrencyrequiredissueDaterequiredinvoiceNumberrequired

convert_invoice

Convert an e-invoice between formats

Convert an e-invoice between formats via the shared EN 16931 canonical model: parse the source document, re-serialize as the target, and validate the result before returning it — never a document that has not been checked. Format ids: "UBL_2.1" (OASIS UBL, the universal Peppol/EN16931 baseline), "UN_CEFACT_CII" (UN/CEFACT Cross Industry Invoice, required syntax for Chorus Pro/France and many ERP back-ends), "XRechnung_UBL" / "XRechnung_CII" (Germany's mandatory B2G format, XRechnung 3.0 — required for invoicing German public-sector buyers), "Factur-X" (France/Germany hybrid PDF+XML — a human-readable PDF/A-3 with the structured invoice embedded, common for French B2B). Binary formats (Factur-X) are base64 in both directions. Requires an API key on the Pro plan or above for any target beyond plain UBL_2.1 — call list_supported_formats to see current availability.

Parameterstorequiredfromrequireddocumentrequired

list_supported_formats

List supported invoice formats

List the e-invoice formats InvoiceHub validates today and what is on the roadmap.

Takes no parameters.

Version history

1
  1. v1.3.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Invoicehub integrations