
Mcp Einvoicing Ae
io.github.cmendezs由 GitHub 帳號 cmendezs 發布v0.3.5更新於 Oct 27, 2026
MCP server for United Arab Emirates electronic invoicing
概覽
針對阿聯酋 Peppol PINT AE 電子發票的在地 MCP 伺服器:產生、驗證、解析 UBL 2.1 發票,並查詢 Peppol 參與者。
- 可以做什麼
- 依結構化資料產生 PINT AE UBL 2.1 發票(開立或自開立),強制寫入必要的 AE 元素並檢查 5% 營業稅率
- 依共用的 CEN EN16931 基礎 Schematron 驗證發票(僅結構與金額合計規則)
- 將 PINT AE 發票 XML 解析為結構化資料,並重新套用 TRN 與稅率檢查
- 查詢 Peppol 參與者、取得 AS4 服務端點、執行 DNS/SML 診斷
- 透過 AS4 傳送 UBL/CII 發票,並嘗試 TDD 驗證(目前一律回報不可用)
- 適用情境
- 適合處理阿聯酋電子發票的情境:讓助理草擬 PINT AE 發票、檢查其結構與金額合計、讀取既有發票 XML,或確認某企業是否能在 Peppol 網路上收送單據。
- 執行需求
- 以 stdio 方式在本機執行;需要 Python 3.11 以上版本,透過 uvx 或 uv 安裝(mcp-einvoicing-core 會自動安裝為相依套件)。Schematron 驗證器需要 xslt2 額外元件(內含 saxonche)。可選環境變數 LOG_LEVEL。目前不需要任何憑證;實際進行 PINT AE 交換需要 Peppol 存取點。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Mcp Einvoicing Ae,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
mcp-einvoicing-ae 🇦🇪
[PyPI version] [Python] [License] [mcp-einvoicing-ae MCP server]
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)
Using uv
From source
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:
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
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
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:
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.
來源:README.md,提交 cc3708a
工具
0版本歷史
1- v0.3.5最新Sep 16, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分