🇺🇾 Uruguay Invoice MCP live

AI agents can now submit a Uruguay DGI e-Factura (Comprobante Fiscal Electrónico, CFE) through the DGI facturación electrónica webservice. This remote MCP server forwards your already-signed SOAP envelope to the government DGI gateway — submit_sobre for an envelope of signed CFEs, submit_reporte_diario for the mandatory daily report, and query_envio_status for submission status. It only forwards the submission: the CFE signature, the Sobre signature and the WS-Security SOAP signature all stay merchant-side.

Connect

{
  "mcpServers": {
    "uruguay-invoice": {
      "type": "http",
      "url": "https://inv-uy.wishpool.app/mcp",
      "headers": {
        "x-dgi-mode": "test"
      }
    }
  }
}

Omit x-dgi-mode (or set test) to stay in the DGI ePrueba testing environment (no fiscal effect); homologacion / produccion for those environments, or x-dgi-endpoint to point at an explicit DGI webservice URL from your onboarding. Your Uruguayan CA certificate and private key never leave your side — this server never sees them.

How it works

• You sign, we forward: DGI requires message-level WS-Security. You sign the CFE, build + sign the Sobre, and X.509-sign the SOAP envelope with your Uruguayan CA certificate (e.g. Correo Uruguayo); you pass the finished envelope as base64. This server relays it to DGI and translates the response — it never signs and never stores anything.
• Get the exact bytes to sign: build_cfe_envelope (local, no network) wraps your signed inner XML into the exact DGI Datain/xmlData SOAP Body so you sign the right structure.
• Three DGI operations: submit_sobre → EFACRECEPCIONSOBRE, submit_reporte_diario → EFACRECEPCIONREPORTE, query_envio_status → EFACCONSULTARESTADOENVIO.
• Status enums: results carry estado (AS = Sobre Recibido / accepted, BS = Sobre Rechazado / rejected), any motivos_rechazo, the consulta_token + consulta_fechahora for the 2nd message, and numbered next_steps.
• IVA helper: calc_iva computes the CFE MontosTotales (Tasa Básica 22% / Tasa Mínima 10% / Exento) from line items.

Do I need to be a DGI "Proveedor Habilitado"?

No. The Registro de Proveedor Habilitado is DGI's optional simplified-onboarding scheme for commercial software vendors — it requires being declared a software provider by at least five electronic issuers and holding the software-vendor activity codes (46510 / 62010 / 62020 / 63110). A merchant issuing their own CFEs onboards through the ordinary ingreso al régimen as an emisor electrónico using their own software; no vendor registration is required. This server is purely a transport layer for documents you have already signed.

Why it is safe

• Stateless: no database — the signed SOAP envelope you submit is forwarded in memory and discarded.
• Signing stays with you: the CFE signature, the Sobre signature and the WS-Security SOAP signature are all computed merchant-side with your private key; a compromise here cannot forge or replay your comprobantes.
• Owner policy guardrails: x-agentpay-allowed-tools (tool allow-list) — set by the human owner in client config; the agent cannot relax it.

Weak-model friendly

Estado values (AS/BS) spelled out in every tool description; the WS-Security requirement and the "you sign, we forward" boundary stated up front; DGI SOAP Faults passed through verbatim; every error teaches the fix (base64 not raw XML, missing WS-Security signature, endpoint mode). Verified live: the DGI ePrueba WSDL returns 200 and an unsigned message is rejected with No signature in message!.

Sister servers

Invoices: Saudi ZATCA inv-sa · Chile DTE inv-cl · Mexico CFDI 4.0 inv-mx · Peru CPE inv-pe · Brazil NF-e inv-br · India GST inv-in. Local payments in 81 countries, one family, same stateless pattern: mcp.wishpool.app (Taiwan e-invoice 電子發票 included).