MCP Einvoicing Ae

mcp-einvoicing-ae 🇦🇪

English | العربية

---

Introduction

mcp-einvoicing-ae is an MCP (Model Context Protocol) server that exposes tools for United Arab Emirates electronic invoicing. It is part of the mcp-einvoicing-* family of country-specific servers, all built on mcp-einvoicing-core, which provides the shared validation engine, EN 16931 abstractions, and Peppol network utilities.

Generated PINT AE invoices are structurally conformant: cbc:UUID, cbc:ProfileExecutionID, per-line cac:ItemPriceExtension, and trade_license_number are all emitted, and round-trip back through parse_invoice_ae. The 5.00% standard VAT rate is enforced by a model validator, and a Peppol participant-lookup tool is exposed. validate_invoice_ae checks core's shared CEN EN16931 base Schematron only, not the PINT AE jurisdiction overlay; validate_tdd_ae currently reports "unavailable" — see Supported standards and Available tools below.

The UAE Peppol Authority's PINT AE (billing) specialization is at Status: Final, version 1.0.4 (2026-06-02); the Peppol AE Tax Data Document (TDD) is at Status: Final, version 1.0.4 (2026-07-23). Full citations: specs/README.md.

Supported standards

• PINT AE (billing) — UBL 2.1, CustomizationID: urn:peppol:pint:billing-1@ae-1, ProfileID: urn:peppol:bis:billing. Version 1.0.4 (2026-06-02).
• PINT AE (self-billing) — CustomizationID: urn:peppol:pint:selfbilling-1@ae-1, ProfileID: urn:peppol:bis:selfbilling.
• Peppol AE TDD (Tax Data Document) — the 5th-corner reporting document sent to the FTA; its own XML namespace (urn:peppol:schema:taxdata:1.0), not a UBL invoice. Version 1.0.4 (2026-07-23).

The UAE programme is a decentralized Peppol 5-corner model routed through Accredited Service Providers, adding a tax-authority reporting leg (the TDD above) beyond the 4-corner exchange used elsewhere in this family. The invoice-tree pathway is confirmed EN16931Invoice (PINT AE is a UBL 2.1 CIUS of EN 16931-1:2017) — no JSON binding was found in the supplied specifications.

AEInvoice serializes via mcp_einvoicing_ae.wire_formats.AEUBLSerializer, which layers the AE-specific elements (cbc:ProfileExecutionID, PartyLegalEntity/CompanyID with schemeAgencyID="TL" for trade_license_number) on top of core's EN16931UBLSerializer — the latter now emits cbc:UUID (from document_uuid) and per-line cac:ItemPriceExtension natively (mcp-einvoicing-core v1.25.0), since profile/business_process already hold the real Peppol URNs. AEParty.vat_id carries the 15-digit TRN, format-validated via TaxIdentifier.validate_ae_trn() (core v1.22.0); the Peppol participant ID (TIN) is auto-derived as its first 10 digits. AETaxDataDocument models the TDD's mandatory fields but is not a UBL invoice and is not built on AEInvoice. parse_invoice_ae re-extracts the AE-specific elements from the raw XML and re-validates the result as AEInvoice, so parsing re-applies the same TRN and tax-rate checks a fresh construction gets — see Available tools for what's covered and what isn't. The TDD transport channel (same AS4 channel as the invoice, or a separate one) remains an open documentation question, not a code gap. Full detail: specs/README.md.

Validation scope, as of v0.2.0: validate_invoice_ae checks the CEN EN16931 base Schematron only (structural + arithmetic/totals rules, shared with mcp-einvoicing-be/mcp-ksef-pl) — not the PINT AE jurisdiction overlay (ibr-*-ae rules). BR-CO-09 (VAT identifier must carry an ISO 3166-1 alpha-2 prefix) is expected to fire on every genuine AE invoice, since UAE TRNs carry no country prefix; this is disclosed in every result, not a defect in your data. validate_tdd_ae currently has no validation available at all. v0.1.0 bundled five self-compiled files derived from OpenPeppol's PINT AE and TDD Schematron/XSD sources with no confirmed redistribution rights — removed in v0.2.0. See CHANGELOG.md.

Installation

Requirements

• Python ≥ 3.11
• mcp-einvoicing-core (installed automatically as a dependency)

Using uvx (recommended)

uvx mcp-einvoicing-ae

Using uv

uv add mcp-einvoicing-ae

From source

git clone https://github.com/cmendezs/mcp-einvoicing-ae.git

cd mcp-einvoicing-ae uv sync --all-extras

Configuration

Environment variables

Country-specific variables (transport endpoints, credentials, environment switches) are added once the specification documents them. See .env.example. This server needs no credentials to run today.

Claude Desktop integration

To use this server with Claude, add this configuration to your claude_desktop_config.json file:

{

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

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-ae": { "command": "uvx", "args": ["mcp-einvoicing-ae"] } } }

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-ae": { "command": "uvx", "args": ["mcp-einvoicing-ae"], "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

Peppol participant lookup (core's register_peppol_tools plugin, TIN-based id adapter — scheme 0235, first 10 digits of the TRN):

generate_invoice_ae/validate_invoice_ae/parse_invoice_ae require mcp-einvoicing-ae[xslt2] (bundles saxonche) for the base Schematron validator to load; without it, validate_invoice_ae returns an explicit "unavailable" result rather than a silent pass.

The tool reference in docs/TOOLS.md is generated from the running server:

uv run python scripts/gen_tool_reference.py

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 required for PINT AE / Peppol AE TDD, but any accredited access point speaks the same AS4 profile, so switching providers is a configuration change, not a code change.

Contributing

See CONTRIBUTING.md for development setup, the test and lint commands, and the pull request checklist. Security issues follow the private disclosure process in SECURITY.md.

Other e-invoicing MCP servers

License

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