Uae Einvoice MCP

What uae-einvoice-mcp does

uae-einvoice-mcp provides a local toolkit for reviewing UAE e-invoicing data against PINT AE-oriented requirements. Its checks cover business identifier formats, invoice structure, mandatory data fields, XML generation, XML Schematron validation, transaction scope, and mandate guidance.

The server is suited to ERP and finance workflows that need an initial review before sending documents through an Accredited Service Provider (ASP). It can identify missing or invalid invoice data and explain whether a transaction is mandatory, excluded, or voluntary under the supported scope categories.

How it works

The package is implemented with the MCP TypeScript SDK v2 and communicates over stdio. An MCP client starts the local process, then sends structured tool calls containing invoice, transaction, or identifier data. Results include validation findings, gaps, errors, warnings, scores, or generated XML depending on the tool.

validate_pint_ae_xml applies the official OpenPeppol PINT AE 1.0.4 Schematron rules, including shared and UAE-specific rules. Its first invocation downloads and compiles those rules. The XML generator creates UBL 2.1 Invoice or CreditNote documents and supports an optional strict mode that can refuse invalid input.

Setup and configuration

Node.js 20 or newer is required. Install and build the package, then start the server:

npm install
npm run build
npm start

For direct TypeScript development, use npm run dev. npm run selfcheck runs the package self-check without an MCP client. The repository also provides an Inspector command through npm run inspector.

A published-package MCP configuration can start the server with npx:

{
  "mcpServers": {
    "uae-einvoice": {
      "command": "npx",
      "args": ["-y", "uae-einvoice-mcp"]
    }
  }
}

A local checkout can instead launch dist/index.js with Node.js. The package requires no API keys for its local operation.

Tools and capabilities

• lookup_business_trn checks 15-digit TRN and 10-digit TIN formats, verifies the UAE 1… prefix and Peppol AE:TIN check digit, and returns the 0235:<TIN> endpoint identifier.
• check_invoice_compliance reviews parties, line items, totals mathematics, and tax breakdowns, returning errors, warnings, and a score.
• check_pint_ae_fields evaluates all 51 mandatory fields as present, missing, invalid, or not applicable, then reports gaps.
• generate_pint_ae_xml creates a UBL 2.1 PINT AE Invoice or CreditNote, with optional strict validation behavior.
• validate_pint_ae_xml checks XML against PINT AE 1.0.4 Schematron rules.
• get_einvoicing_requirements returns mandate phases, excluded transactions, recent Ministry of Finance amendments, the technical baseline, and suggested next actions.
• check_einvoicing_scope classifies transaction scope for B2B, B2G, and B2C cases, including Tax Groups, sovereign transactions, air transactions, and exempt finance.

Limitations and notes

The server is informational tooling, not legal or tax advice. Its checks do not replace Accredited Service Provider XSD validation, digital signatures, or live FTA register checks. XML generated by the server should therefore be treated as part of a preparation workflow rather than a complete transmission process. Schematron validation also downloads and compiles the PINT AE 1.0.4 rules on its first call.