Uruguay Invoices (DGI e-Factura CFE, merchant-signed SOAP relay)

Official6 toolsLive

by junter1989k-ai · JavaScript

Uruguay DGI e-Factura (CFE): AI agents submit signed sobres to DGI e-invoicing, stateless forwarder.

Topics

ai-agentclaudedgie-facturainvoicemcpmcp-serveruruguayvatwishpool

Captured live from the server via tools/list.

submit_sobre

Submit a Sobre (envelope of one or more signed CFEs — e-Factura / e-Ticket and their notas) to Uruguay DGI e-Factura via the EFACRECEPCIONSOBRE webservice operation. You pass an ALREADY WS-Security-signed SOAP envelope (base64); this server forwards it to DGI and translates the reply. Result: accepted=true with estado AS (Sobre Recibido — DGI accepted the envelope) or accepted=false with estado BS (Sobre Rechazado — see motivos_rechazo). On acceptance DGI returns consulta_token + consulta_fechahora — use them later with query_envio_status to fetch the 2nd message (per-CFE response). How signing works: DGI requires message-level WS-Security — you sign the CFE XML, build + sign the Sobre, and X.509-sign the SOAP envelope with your Uruguayan CA certificate (e.g. from Correo Uruguayo), all merchant-side. This server stores nothing and never sees your private key; it forwards the finished envelope. Endpoint headers: x-dgi-mode = test (default, ePrueba sandbox — no fiscal effect) | homologacion | produccion; or x-dgi-endpoint to point at an explicit DGI webservice URL. Owner-policy headers x-agentpay-max-amount / x-agentpay-approval-above / x-agentpay-allowed-tools are honored.

Parameters1

signed_soap_envelope

string

required

The FULL WS-Security-signed SOAP 1.1 envelope, base64-encoded. You build it (Body = the DGI operation wrapping <Datain><xmlData>your signed Sobre/Reporte</xmlData></Datain>), sign it with your X.509 certificate merchant-side, then base64-encode the whole envelope. This server forwards the bytes untouched — it never signs. Tip: call build_cfe_envelope first to get the exact Body to sign.

Raw schema

{
  "type": "object",
  "properties": {
    "signed_soap_envelope": {
      "type": "string",
      "description": "The FULL WS-Security-signed SOAP 1.1 envelope, base64-encoded. You build it (Body = the DGI operation wrapping <Datain><xmlData>your signed Sobre/Reporte</xmlData></Datain>), sign it with your X.509 certificate merchant-side, then base64-encode the whole envelope. This server forwards the bytes untouched — it never signs. Tip: call build_cfe_envelope first to get the exact Body to sign."
    }
  },
  "required": [
    "signed_soap_envelope"
  ]
}

submit_reporte_diario

Submit a Reporte Diario (daily report of the CFEs issued that day, including any anulados) to Uruguay DGI via the EFACRECEPCIONREPORTE webservice operation. Same shape as submit_sobre: pass an ALREADY WS-Security-signed SOAP envelope (base64) whose Body wraps your signed Reporte Diario XML; this server forwards it. Result carries the DGI acknowledgement (estado + any motivos_rechazo). The daily report is mandatory for emisores electrónicos. How signing works: DGI requires message-level WS-Security — you sign the CFE XML, build + sign the Sobre, and X.509-sign the SOAP envelope with your Uruguayan CA certificate (e.g. from Correo Uruguayo), all merchant-side. This server stores nothing and never sees your private key; it forwards the finished envelope. Endpoint headers: x-dgi-mode = test (default, ePrueba sandbox — no fiscal effect) | homologacion | produccion; or x-dgi-endpoint to point at an explicit DGI webservice URL. Owner-policy headers x-agentpay-max-amount / x-agentpay-approval-above / x-agentpay-allowed-tools are honored.

Parameters1

signed_soap_envelope

string

required

Raw schema

{
  "type": "object",
  "properties": {
    "signed_soap_envelope": {
      "type": "string",
      "description": "The FULL WS-Security-signed SOAP 1.1 envelope, base64-encoded. You build it (Body = the DGI operation wrapping <Datain><xmlData>your signed Sobre/Reporte</xmlData></Datain>), sign it with your X.509 certificate merchant-side, then base64-encode the whole envelope. This server forwards the bytes untouched — it never signs. Tip: call build_cfe_envelope first to get the exact Body to sign."
    }
  },
  "required": [
    "signed_soap_envelope"
  ]
}

query_envio_status

Query the status of a previous DGI submission via the EFACCONSULTARESTADOENVIO webservice operation — e.g. to fetch the 2nd message (per-CFE response) using the consulta_token + consulta_fechahora that submit_sobre returned. Pass an ALREADY WS-Security-signed SOAP envelope (base64) whose Body wraps your signed consulta request; this server forwards it and returns the DGI response document. Safe/read-only at DGI. How signing works: DGI requires message-level WS-Security — you sign the CFE XML, build + sign the Sobre, and X.509-sign the SOAP envelope with your Uruguayan CA certificate (e.g. from Correo Uruguayo), all merchant-side. This server stores nothing and never sees your private key; it forwards the finished envelope. Endpoint headers: x-dgi-mode = test (default, ePrueba sandbox — no fiscal effect) | homologacion | produccion; or x-dgi-endpoint to point at an explicit DGI webservice URL. Owner-policy headers x-agentpay-max-amount / x-agentpay-approval-above / x-agentpay-allowed-tools are honored.

Parameters1

signed_soap_envelope

string

required

Raw schema

{
  "type": "object",
  "properties": {
    "signed_soap_envelope": {
      "type": "string",
      "description": "The FULL WS-Security-signed SOAP 1.1 envelope, base64-encoded. You build it (Body = the DGI operation wrapping <Datain><xmlData>your signed Sobre/Reporte</xmlData></Datain>), sign it with your X.509 certificate merchant-side, then base64-encode the whole envelope. This server forwards the bytes untouched — it never signs. Tip: call build_cfe_envelope first to get the exact Body to sign."
    }
  },
  "required": [
    "signed_soap_envelope"
  ]
}

build_cfe_envelope

Helper (pure-local, NO network, NO signing): given your signed inner DGI XML document, returns the exact SOAP 1.1 envelope Body you must WS-Security-sign before submitting. This makes the DGI Datain/xmlData structure explicit so you sign the right bytes. operation = sobre (EFACRECEPCIONSOBRE, default) | reporte (EFACRECEPCIONREPORTE) | consulta (EFACCONSULTARESTADOENVIO). Returns the envelope XML plus its base64 (unsigned — you still must add the WS-Security X.509 signature over the Body, then base64 the SIGNED envelope for submit_sobre/submit_reporte_diario/query_envio_status). Nothing is sent anywhere.

Parameters2

inner_xml	string	required	Your signed inner DGI XML document (the Sobre / Reporte Diario / consulta request). Provided as raw XML (this tool escapes it into <xmlData>). It should already carry its own CFE/Sobre digital signature.
operation	string	optional	Which DGI operation to wrap for. Default sobre.

Raw schema

{
  "type": "object",
  "properties": {
    "inner_xml": {
      "type": "string",
      "description": "Your signed inner DGI XML document (the Sobre / Reporte Diario / consulta request). Provided as raw XML (this tool escapes it into <xmlData>). It should already carry its own CFE/Sobre digital signature."
    },
    "operation": {
      "type": "string",
      "enum": [
        "sobre",
        "reporte",
        "consulta"
      ],
      "description": "Which DGI operation to wrap for. Default sobre."
    }
  },
  "required": [
    "inner_xml"
  ]
}

calc_iva

Compute Uruguay IVA and CFE MontosTotales from line items (pure-local, NO network). Uruguay IVA: Tasa Básica 22%, Tasa Mínima 10%, Exento 0%. Give items with net_price (tax-EXCLUSIVE unit price), optional quantity, and either iva_rate (22 | 10 | 0) or indfact (3 | 2 | 1). Returns the CFE MontosTotales fields: MntNetoIvaTasaBasica / MntNetoIvaTasaMin / MntExento, IVATasaBasica=22 / IVATasaMin=10, MntIVATasaBasica / MntIVATasaMin, and MntTotal — ready to place in the CFE before you sign it. Amounts in UYU (or set moneda).

Parameters2

items	array	required	Line items. Each: net_price (tax-exclusive unit price), optional quantity (default 1) and iva_rate (22 Tasa Básica default, 10 Tasa Mínima, 0 Exento) OR indfact (3/2/1).
moneda	string	optional	ISO currency code (Moneda). Default UYU.

Raw schema

{
  "type": "object",
  "properties": {
    "items": {
      "type": "array",
      "minItems": 1,
      "description": "Line items. Each: net_price (tax-exclusive unit price), optional quantity (default 1) and iva_rate (22 Tasa Básica default, 10 Tasa Mínima, 0 Exento) OR indfact (3/2/1).",
      "items": {
        "type": "object",
        "properties": {
          "net_price": {
            "type": "number",
            "description": "Tax-exclusive unit price."
          },
          "quantity": {
            "type": "number",
            "description": "Default 1."
          },
          "iva_rate": {
            "type": "number",
            "description": "IVA rate percent: 22 (Tasa Básica, default), 10 (Tasa Mínima) or 0 (Exento)."
          },
          "indfact": {
            "type": "number",
            "description": "Alternative to iva_rate: CFE IndFact 3 (Básica), 2 (Mínima), 1 (Exento)."
          }
        },
        "required": [
          "net_price"
        ]
      }
    },
    "moneda": {
      "type": "string",
      "description": "ISO currency code (Moneda). Default UYU."
    }
  },
  "required": [
    "items"
  ]
}

get_dgi_info

Reference (pure-local, NO network): the DGI e-Factura webservice endpoints, the three SOAP operations and their SOAPActions, the CFE document-type codes (TipoCFE), and the IVA rates/namespaces — so an agent can orient before signing. The test (ePrueba) endpoint is verified live; produccion must be confirmed against your DGI onboarding. No credentials needed.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "required": []
}

README.md6 KBView on GitHub

Uruguay Invoice MCP

Remote MCP server that lets any AI agent submit Uruguay DGI e-Factura (Comprobante Fiscal Electrónico, CFE) documents to the DGI facturación electrónica webservice. It is a stateless forwarder: the CFE signature, the Sobre signature and the WS-Security SOAP signature all stay merchant-side. Bring your own Uruguayan CA certificate; nothing is stored.

Endpoint: https://inv-uy.wishpool.app/mcp (MCP Streamable HTTP)
Region: gru1 (São Paulo) · License: MIT
Registry: app.wishpool/uruguay-invoice-mcp

The signing boundary (read this first)

DGI requires message-level WS-Security: every submission is a SOAP message whose Body is X.509-signed with the merchant's Uruguayan CA certificate (e.g. from Correo Uruguayo), and each CFE and the Sobre carry their own XML digital signatures. All of that happens on your side, with your private key, which never leaves your side.

This server does not sign and does not store anything. You hand it the finished, WS-Security-signed SOAP envelope (base64); it adds the SOAPAction header, POSTs it to the chosen DGI endpoint, and translates the DGI acknowledgement. This is the same "you sign, we forward" model as the sister Saudi ZATCA and Costa Rica Hacienda servers.

This mirrors how DGI itself behaves: an unsigned POST to the live ePrueba endpoint is rejected with a DGI-signed SOAP Fault — <Detalle>No signature in message!</Detalle>. The signature is mandatory and is yours to produce.

Tools

Tool	DGI operation	What it does
`submit_sobre`	`EFACRECEPCIONSOBRE`	Submit a Sobre (envelope of signed CFEs). Input `signed_soap_envelope` (base64). Returns `estado` (AS accepted / BS rejected), `motivos_rechazo`, `consulta_token` + `consulta_fechahora`.
`submit_reporte_diario`	`EFACRECEPCIONREPORTE`	Submit the mandatory Reporte Diario. Same signed-envelope input.
`query_envio_status`	`EFACCONSULTARESTADOENVIO`	Query a submission status / fetch the 2nd message. Read-only at DGI.
`build_cfe_envelope`	— (local)	Wrap your signed inner XML into the exact SOAP Body to WS-Security-sign. No network, no signing.
`calc_iva`	— (local)	Compute CFE `MontosTotales` (IVA Tasa Básica 22% / Tasa Mínima 10% / Exento). No network.
`get_dgi_info`	— (local)	Reference: endpoints, operations + SOAPActions, `TipoCFE` codes, IVA rates, namespaces.

Typical flow

calc_iva → get the CFE MontosTotales.
Build and sign the CFE, build and sign the Sobre (merchant-side).
build_cfe_envelope → get the exact SOAP Body.
WS-Security-sign that envelope with your certificate, base64-encode it (merchant-side).
submit_sobre → forward. On estado AS, keep the returned consulta_token.
query_envio_status later → fetch the per-CFE 2nd message. Send the daily report with submit_reporte_diario.

Configuration (headers, per-request, nothing stored)

x-dgi-mode: test (default — DGI ePrueba sandbox, no fiscal effect, verified live) · homologacion · produccion.
x-dgi-endpoint: an explicit https:// DGI webservice URL (overrides x-dgi-mode).
x-agentpay-allowed-tools: owner-set tool allow-list (the agent cannot relax it).

Endpoints

Mode	URL	Status
`test`	`https://efactura.dgi.gub.uy:6443/ePrueba/ws_eprueba`	Verified live (200 WSDL + signed fault on unsigned POST, 2026-07-10)
`homologacion`	`https://efactura.dgi.gub.uy:6470/eHomologacion/ws_ehomologacion`	Confirm port/path against your DGI onboarding
`produccion`	`https://efactura.dgi.gub.uy:6463/eFactura/ws_efactura`	Documented prod URL — confirm against your DGI onboarding before going live (this port was not reachable from the build sandbox)

Do I need to be a "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 its own CFEs onboards through the ordinary ingreso al régimen as an emisor electrónico with its own software; no vendor registration is required. This server is only a transport layer for documents you have already signed.

Honest limitations / boundaries

We never sign. If your envelope lacks a WS-Security signature, DGI rejects it (No signature in message!); the server surfaces this and blocks an obviously-unsigned envelope before it even reaches the network.
Amount policy cap is not enforced on submit. The submitted envelope is an opaque signed blob; the grand total lives in each CFE's MontosTotales inside the signed body. Apply x-agentpay-max-amount logic at the calc_iva / build stage (pre-sign). The tool allow-list guardrail does apply to every call.
test is the only endpoint verified live from here. homologacion / produccion URLs are the documented DGI ones but must be confirmed against your onboarding materials (or overridden with x-dgi-endpoint).
calc_iva covers the common Básica/Mínima/Exento breakdown, not every special indicator (exports/assimilated, perceptions, etc.).

Develop / test

bash

npm run dev    # local server on http://localhost:3245
npm test       # e2e: protocol + IVA math + local helpers + validation + policy + LIVE DGI ePrueba assertions

The e2e suite hits the real DGI ePrueba endpoint: it asserts the WSDL is 200 with the three operations and that a fake-signed envelope round-trips to a DGI SOAP Fault (endpoint alive + fault passthrough).

Safety

Stateless forwarder. The signed SOAP envelope travels per-request and is never stored; no credentials, documents, or customer data are persisted. Privacy: https://inv-uy.wishpool.app/privacy

Family

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 — https://mcp.wishpool.app.

Install

Tools (6)

submit_sobresubmit_reporte_diarioquery_envio_statusbuild_cfe_envelopecalc_ivaget_dgi_info

Remote endpoint

Streamable HTTP

Hosted server - connect over the network, no local install.

url

https://inv-uy.wishpool.app/mcp

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "uruguay-invoice-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://inv-uy.wishpool.app/mcp"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.