mcpField
M
mcp-einvoicing-de

mcp-einvoicing-de

Local
github.com/cmendezsFinance2Updated 7w ago

About mcp-einvoicing-de

mcp-einvoicing-de is a Python MCP server for German e-invoicing, designed for organizations handling ZUGFeRD and XRechnung documents. It creates, validates, parses, and converts invoices, with optional Peppol tools and local validation by default.

Key features

  1. 01Create ZUGFeRD and XRechnung invoices
  2. 02Validate against EN 16931 and KoSIT rules
  3. 03Parse invoice XML and PDF/A-3
  4. 04Convert invoice profiles and syntax
  5. 05Export invoices for DATEV
  6. 06Peppol lookup and sending tools

Use cases

  1. 01Generate compliant German e-invoices
  2. 02Validate invoices locally against rules
  3. 03Extract structured data from invoice files
  4. 04Check Peppol registration or send invoices

MCP support

Exposes invoice creation, validation, parsing, conversion, tax, DATEV, and Peppol tools to MCP clients. Local validation is the default; KoSIT cloud validation can be enabled optionally.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"cmendezs-mcp-einvoicing-de": {
"command": "uvx",
"args": [
"mcp-einvoicing-de"
],
"env": {
"EINVOICING_DE_LOG_LEVEL": "<EINVOICING_DE_LOG_LEVEL>",
"EINVOICING_DE_KOSIT_ENABLE": "<EINVOICING_DE_KOSIT_ENABLE>",
"EINVOICING_DE_KOSIT_VALIDATOR_URL": "<EINVOICING_DE_KOSIT_VALIDATOR_URL>"
}
}
}
}
Run commanduvx mcp-einvoicing-de
Environment variables to set
EINVOICING_DE_LOG_LEVELLogging level: DEBUG, INFO (default), WARNING, or ERROR
EINVOICING_DE_KOSIT_ENABLESet to 1 to opt in to remote KoSIT cloud validation by default across all invoice_validate calls (egresses the full invoice payload). Local Schematron only by default; callers can still opt in per-call with cloud_validate=True.
EINVOICING_DE_KOSIT_VALIDATOR_URLURL of a self-hosted KoSIT validation tool REST endpoint (e.g. http://localhost:8080/api/v1/validate), used only when cloud validation is enabled (cloud_validate=True or EINVOICING_DE_KOSIT_ENABLE=1). Defaults to an [Unverified] validator.kosit.de endpoint if unset.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
pypimcp-einvoicing-de0.11.4

Tools

50

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
syntaxstringNoXML syntax: 'CII' (default) or 'UBL' (XRechnung only).
invoiceobjectYesInvoice data matching the ZUGFeRDInvoice schema. Set invoice.profile to XRECHNUNG to produce an XRechnung invoice.
pretty_printbooleanNoPretty-print the XML output.
output_formatstringNo'xml' (default) or 'pdf' (ZUGFeRD hybrid PDF/A-3).
transitional_period_opt_inbooleanNoAcknowledge the Wachstumschancengesetz transitional period (2025-2026) and explicitly permit non-XML output for a German VAT-registered buyer. Set to True only when the buyer has agreed in writing to receive PDF or another non-structured format. From 2027 the transitional grace ends for large businesses; from 2028 all B2B invoices to German VAT-registered buyers must be in a structured EN 16931 format. Source: §14 Abs. 2 UStG, Wachstumschancengesetz of 27 March 2024 (BGBl. I Nr. 108).

Details

From the project README

mcp-einvoicing-de 🇩🇪

English | Deutsch

License PyPI version Python mcp-einvoicing-de MCP server

MCP server (Model Context Protocol) in Python for German electronic invoicing in ZUGFeRD 2.x and XRechnung 3.x formats (EN 16931, FeRD, KoSIT). Enables AI agents (Claude, IDEs) to create, validate, parse, and convert e-invoices that are fully compliant with the German B2B e-invoicing mandate (effective from 2025, phased enforcement through 2027 to 2028) and the European standard EN 16931.


Introduction

This package is built on mcp-einvoicing-core, a shared base library for European e-invoicing MCP servers. It provides shared models, validation abstractions, XML utilities, and the exception hierarchy.

mcp-einvoicing-core is automatically installed as a transitive dependency, no additional step required.

For developers: pip install -e ".[dev]" installs the base package automatically from PyPI.

Installation

Via PyPI (recommended)
pip install mcp-einvoicing-de

Without prior installation, using uvx:

uvx mcp-einvoicing-de
From source
git clone https://github.com/cmendezs/mcp-einvoicing-de.git
cd mcp-einvoicing-de

python -m venv .venv
source .venv/bin/activate   # Windows: .venv\Scripts\activate

pip install -e ".[dev]"
Optional extras
ExtraPurposeInstall
[xslt2]Saxon-HE backend for XSLT 2.0 Schematron stylesheets (FeRD Factur-X 1.09.2 and KoSIT XRechnung 3.0.2). Required for local Schematron validation; lxml supports XSLT 1.0 only.pip install mcp-einvoicing-de[xslt2]
[pdf]Additional PDF utilities for embedded XML extraction (pikepdf is also a base dependency for PDF/A-3 generation).pip install mcp-einvoicing-de[pdf]
[pymupdf]Alternative PDF engine (uses PyMuPDF).pip install mcp-einvoicing-de[pymupdf]
[dev]Development tools (pytest, ruff, pre-commit).pip install mcp-einvoicing-de[dev]

Configuration

The server does not require external credentials. Available environment variables:

VariableDescriptionDefault
EINVOICING_DE_LOG_LEVELLog level (DEBUG, INFO, WARNING, ERROR)INFO
EINVOICING_DE_KOSIT_VALIDATOR_URLURL of a self-hosted KoSIT validation tool REST endpoint. Only used if cloud validation is enabled — see EINVOICING_DE_KOSIT_ENABLE
EINVOICING_DE_KOSIT_ENABLESet to 1 to enable KoSIT cloud validation (validator.kosit.de or a self-hosted endpoint). Local Schematron-only validation is the default
EINVOICING_PEPPOL_CODELIST_DIRLocal directory containing your own copy of the OpenPeppol eDEC Code Lists, required by the Peppol codelist tools (not bundled with this package; see mcp-einvoicing-core README)
EINVOICING_EN16931_CODELIST_DIRLocal directory containing your own copy of the CEF "Digital Building Blocks" EN 16931 semantic code lists, required by the EN 16931 codelist tools (not bundled; see mcp-einvoicing-core README)

The EUSR/TSR reporting and MLS tools additionally require the [xslt2] extra for Schematron validation.

Claude Desktop integration

Add the following entry to claude_desktop_config.json. No environment variables are required:

{
  "mcpServers": {
    "einvoicing-de": {
      "command": "uvx",
      "args": ["mcp-einvoicing-de"]
    }
  }
}

Cursor integration

Cursor supports MCP servers via stdio. Add the configuration in:

  • Global (all projects): ~/.cursor/mcp.json
  • Project (this repository only): .cursor/mcp.json
{
  "mcpServers": {
    "einvoicing-de": {
      "command": "uvx",
      "args": ["mcp-einvoicing-de"]
    }
  }
}

Reload the Cursor window (Ctrl+Shift+P then Reload Window) to apply the changes.

Kiro integration

Kiro supports MCP servers via its dedicated configuration file. Two levels are available:

  • Global (all projects): ~/.kiro/settings/mcp.json
  • Workspace (this repository only): .kiro/settings/mcp.json
{
  "mcpServers": {
    "einvoicing-de": {
      "command": "uvx",
      "args": ["mcp-einvoicing-de"],
      "disabled": false,
      "autoApprove": []
    }
  }
}

The file is automatically reloaded on save. You can also open the config via the command palette (Cmd+Shift+P / Ctrl+Shift+P) then MCP.

Available tools

ToolDescription
invoice_createGenerate ZUGFeRD or XRechnung XML (CII or UBL). Enforces the §14 Abs. 2 UStG B2B mandate: non-XML output is rejected for DE-prefixed VAT buyers unless transitional_period_opt_in=True is set. output_format='pdf' produces a PDF/A-3 level B hybrid invoice with sRGB ICC profile, OutputIntent, embedded fonts, and deterministic /ID.
invoice_validateValidate an invoice against EN 16931 and KoSIT rules (BR-DE-*). Local Schematron validation runs by default (no data leaves your machine); set cloud_validate=True or EINVOICING_DE_KOSIT_ENABLE=1 to opt into KoSIT cloud validation (validator.kosit.de or a self-hosted endpoint) with exponential backoff retry (1s/2s/4s). XSLT 2.0 local validation requires the [xslt2] extra.
invoice_parseExtract structured data from ZUGFeRD or XRechnung XML, or from a PDF/A-3 hybrid invoice with embedded factur-x.xml / zugferd-invoice.xml.
invoice_convertConvert between ZUGFeRD profiles, swap ZUGFeRD/XRechnung CII headers, or perform cross-syntax CII/UBL conversion via core convert_wire_format.
datev_exportExport a ZUGFeRD invoice as a DATEV EXTF 700 Buchungsstapel CSV file for import into DATEV accounting software. Defaults to SKR 03 accounts (8400 revenue / 10000 receivable).
tax_rulesQuery German VAT rules (rates, §13b UStG reverse charge codes, §19 UStG Kleinunternehmer thresholds at JStG 2024 values of €25,000 preceding year / €100,000 current year, exemptions).
Peppol network tools

Peppol participant lookup, service-endpoint lookup, a DNS-only diagnostic, AS4 send, Peppol Directory search, and the OpenPeppol eDEC codelist tools are provided by the shared core Peppol tool plugin (mcp_einvoicing_core.peppol.tools.register_peppol_tools), mounted in server.py with a German-specific identifier adapter: a bare USt-IdNr (e.g. 123456789 or DE123456789) is normalized to the 9930:<value> Peppol scheme (DE:VAT); an already scheme-qualified identifier (e.g. 9930:DE123456789, or 0204:<leitweg-id> for Leitweg-ID-routed B2G invoices) passes through unchanged. To send via AS4, first produce XRechnung UBL with invoice_convert (or invoice_create with target_syntax='UBL'), then pass the result to peppol_send.

peppol_send signs outbound messages with a real wsse:Security signature as of mcp-einvoicing-core v1.20.0 (previously computed and discarded — see CHANGELOG.md v0.10.0).

ToolDescription
peppol_lookup_participantCheck whether a business is registered on the Peppol network; returns registration status and supported document types
peppol_get_service_endpointFetch the AS4 endpoint for a participant's document type
resolve_peppol_dnsDNS-only (SML) diagnostic, independent of SMP reachability
peppol_sendTransmit a UBL/CII invoice via AS4
peppol_directory_searchSearch the public Peppol Directory by participant, name, country, or document type
list_participant_id_schemes, list_document_type_ids, list_process_ids, list_spis_use_case_idsOpenPeppol eDEC codelist lookups (require EINVOICING_PEPPOL_CODELIST_DIR)
check_document_type_id_in_codelist, check_process_id_in_codelist, check_participant_id_scheme_in_codelist, get_peppol_codelist_versionOpenPeppol eDEC codelist checks and version reporting

See the mcp-einvoicing-core README for full parameter documentation on these tools.

Peppol reporting and status tools

Added in v0.10.0 via three opt-in core plugins, mounted unconditionally in server.py. Each raises a clear error at call time (not at registration) if its extra or data directory is missing.

ToolPluginDescription
validate_eusr_reportregister_peppol_reporting_toolsValidate an End User Statistics Report (XSD, then Schematron). Requires the [xslt2] extra.
validate_tsr_reportregister_peppol_reporting_toolsValidate a Transaction Statistics Report (XSD, then Schematron). Requires the [xslt2] extra.
validate_mls_messageregister_peppol_mls_toolsValidate a Message Level Status document (UBL ApplicationResponse-2 subset). Requires the [xslt2] extra.
build_mls_messageregister_peppol_mls_toolsBuild a document-level MLS response. Requires the [xslt2] extra.
13 list_*/check_* pairs, get_en16931_codelist_versionregister_en16931_codelist_toolsEN 16931 semantic code list lookups/checks (units, VAT categories, etc.). Require EINVOICING_EN16931_CODELIST_DIR.

See the mcp-einvoicing-core README for full parameter documentation on these tools.

Usage examples

Example 1: Validate an invoice

1. invoice_validate(
     xml_base64="...",   # Base64-encoded ZUGFeRD XML
     strict=True
   )
   → {
       "is_valid": true,
       "profile": "EN_16931",
       "syntax": "CII",
       "error_count": 0,
       "warning_count": 2,
       "errors": [],
       "warnings": [...],
       "validator_used": "local_schematron"
     }

Example 2: Query German tax rules

2. tax_rules(query="reverse_charge", context="Bauleistungen")
   → {
       "results": [
         {
           "paragraph": "§13b Abs. 2 Nr. 5 UStG",
           "description_en": "Construction services (building contractor rule)",
           "vatex_code": "VATEX-EU-AE",
           "invoice_note": "Steuerschuldnerschaft des Leistungsempfängers (§13b UStG)"
         }
       ],
       "legal_disclaimer": "..."
     }

Example 3: Check Peppol registration

3. peppol_lookup_participant(
     identifier="123456789",   # bare USt-IdNr, normalized to 9930:DE123456789
     environment="production"
   )
   → {
       "is_registered": true,
       "participant_id": "9930:DE123456789",
       "supported_document_types": ["urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0"],
       "smp_hostname": "b-...iso6523-actorid-upis.edelivery.tech.ec.europa.eu"
     }

Example 4: Parse invoice data

4. invoice_parse(xml_base64="...", include_raw_xml=False)
   → {
       "profile": "XRECHNUNG",
       "syntax": "CII",
       "invoice_number": "RE-2025-001",
       "invoice_date": "2025-01-15",
       "seller_name": "Muster GmbH",
       "buyer_name": "Käufer AG",
       "tax_inclusive_amount": "119.00",
       "currency_code": "EUR"
     }

Architecture

mcp-einvoicing-de (this package, standalone MCP server)
├── ZUGFeRDInvoice / XRechnungInvoice  ← Pydantic models (all profiles)
├── SchematronValidator                ← EN 16931 + KoSIT BR-DE-* rules
├── KoSITValidator                     ← Remote validation tool (optional)
└── Tools: create / validate / parse / convert / datev_export / tax_rules
    (+ core Peppol tool plugin, mounted separately: lookup / send / DNS / codelists)

        ↑ extends
mcp-einvoicing-core (shared base, installed as dependency)
├── BaseDocumentGenerator / Validator / Parser
├── BaseInvoice, BaseParty … (Pydantic)
├── xml_utils, exceptions
└── EInvoicingMCPServer

Vendor neutrality

This server implements the standard itself: it builds, validates, and signs the document locally. It is not a client for a commercial invoicing platform, and your signing keys and credentials never leave your own infrastructure.

A Peppol access point is optional: transmission via peppol_send is one available channel, and any accredited access point speaks the same AS4 profile, so switching providers is a configuration change, not a code change. This package does not implement direct submission to a German B2G state portal (ZRE/OZG-RE).

Supported standards

StandardVersionProfiles / Syntax
ZUGFeRD2.5.2MINIMUM, BASIC WL, BASIC, EN 16931, EXTENDED
XRechnung3.0.2CII (Cross Industry Invoice), UBL (Universal Business Language)
KoSIT xrechnung-schematron ruleset2.6.0Validation rules for XRechnung 3.0.2 (separate version axis from the spec itself)
EN 169312017European core data model for electronic invoicing
Peppol BIS3.0Billing 3.0 (EN 16931-compliant)

Note: ZUGFeRD 2.x and XRechnung 3.x share the same CII XML syntax at the EN 16931 profile level. Conversion between both formats is therefore possible without data loss. The EXTENDED profile is specific to ZUGFeRD and has no XRechnung equivalent.

ResourceLink
FeRD ZUGFeRD specificationferd-net.de
KoSIT XRechnungxeinkauf.de
KoSIT validation toolgithub.com/itplr-kosit/validationtool
EN 16931-1:2017CEN
Peppol BIS Billing 3.0docs.peppol.eu

Tests

# Install development dependencies
pip install -e ".[dev]"

# Run the full test suite
pytest tests/ -v

# With coverage report
pytest --cov=mcp_einvoicing_de --cov-report=term-missing

# Model tests only
pytest tests/test_models.py -v

Contributing

Contributions are welcome. Please open an issue before submitting a pull request for significant changes.

git clone https://github.com/cmendezs/mcp-einvoicing-de.git
cd mcp-einvoicing-de
pip install -e ".[dev]"
pytest
make audit

Other e-invoicing MCP servers

CountryServer
🌍 Globalmcp-einvoicing-core
🇧🇪 Belgiummcp-einvoicing-be
🇧🇷 Brazilmcp-nfe-br
🇫🇷 Francemcp-facture-electronique-fr
🇩🇪 Germanymcp-einvoicing-de
🇮🇳 Indiamcp-einvoicing-in
🇮🇹 Italymcp-fattura-elettronica-it
🇲🇽 Mexicomcp-cfdi-mx
🇵🇱 Polandmcp-ksef-pl
🇸🇬 Singaporemcp-invoicenow-sg
🇪🇸 Spainmcp-facturacion-electronica-es
🇦🇪 United Arab Emiratesmcp-einvoicing-ae

License

This project is licensed under the Apache 2.0 License. See the LICENSE file for details. For the full version history, see CHANGELOG.md.

Comments

Markdown supported

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.