The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the DF E listing page.
Pulls the electronic fiscal documents issued against your Brazilian company (supplier invoices, CT-e freight bills and events) straight from SEFAZ, through the official NFeDistribuicaoDFe web service, using your own A1 digital certificate. Incremental NSU sync with query-budget control so your tax ID never gets blocked. It also renders the DANFE PDF from the XML, which is the printable document, since SEFAZ distributes XML and not PDF. Read-only. Not affiliated with SEFAZ or the Brazilian Federal Revenue Service.
Versão em português · Full docs (PT-BR) · Agent skill
Anthropic unified MCP installation at claude.ai/customize/connectors. The same link works for Claude Web and Claude Desktop (just be logged in):
Manual (if the deeplink does not open): claude.ai/customize/connectors → + → Add custom connector → paste Name DF-e and URL https://api.mcp.ai/p_dfe.
Works with any MCP client that speaks MCP over HTTP. The server URL is always:
Per-client details: INSTALL.md.
| Tool | Description |
|---|---|
dfe_list_accounts | Lista os CNPJs conectados neste install (razão social, CNPJ e UF). |
dfe_sincronizar | Puxa os documentos fiscais NOVOS emitidos contra este CNPJ (nota de fornecedor, evento, CT-e) — NFeDistribuicaoDFe. |
dfe_consultar_nsu | Busca UM documento específico pelo NSU. |
dfe_consultar_chave | Busca um documento pela chave de acesso de 44 dígitos. |
dfe_gerar_danfe | Gera o DANFE (o PDF da nota) a partir do XML. |
dfe_orcamento | Quantas consultas ainda cabem nesta hora para este CNPJ, e se ele está bloqueado. |
Details for each tool: docs/ferramentas.md (PT-BR)
| Area | Coverage |
|---|---|
| Connections | The tax IDs connected to this install, with company name and state |
| Sync | Incremental NSU queue: supplier NF-e, CT-e freight bills and events issued against the company |
| Single document | Lookup by NSU (to recover an item that failed) or by the 44-digit access key |
| DANFE | The invoice PDF rendered from the XML, delivered as a download link |
| Budget | How many queries are left this hour and whether the tax ID is blocked |
Billed per connected account. See docs/precos.md (PT-BR).
Is this an official SEFAZ or Federal Revenue service? No. This is an independent MCP that talks to the public NFeDistribuicaoDFe web service using your own company's digital certificate. It is not affiliated with SEFAZ or the Brazilian Federal Revenue Service and implies no official relationship. The names are used nominatively, to say where the data comes from.
Does it return the invoices my company issued? No, and that is a SEFAZ limit rather than ours: the distribution service hands the recipient what was issued against them, and technical note 2014.002 excludes the issuer. For your own output, the XML lives in your ERP.
Why do some documents arrive without line items?
Because SEFAZ only unlocks the full XML after the recipient acknowledges the invoice. Until then it delivers a summary: access key, issuer and amount. Each document carries completo: true/false so you know which of the two you got. Since the DANFE needs the line items, it is rendered only from the full XML.
Can I use my accountant's certificate? It will not work. SEFAZ matches the certificate holder against the queried tax ID, so you need the A1 e-CNPJ of the company itself. An accounting firm connects one tax ID per client, each with that client's own certificate.
Could this get my tax ID blocked? The risk is real and it comes from the SEFAZ rule: 20 queries per hour per tax ID, and polling past the end of the queue earns a 1-hour block. The MCP stops on its own when the queue ends, and one tool reports the remaining budget without spending a query. What it cannot control is what your other systems query against the same tax ID, because the limit is shared.
Can I fetch an older invoice by its access key? Yes, as long as it reached the national environment within the last 90 days, which is the SEFAZ window for key lookups. Outside it, the incremental NSU queue is the way.
Where does my certificate live? Encrypted at rest, and used only for the TLS handshake with SEFAZ. There is no third party in the path: the certificate hitting SEFAZ is your company's. The captured XMLs are returned to the caller and are not stored by us beyond operational logs.
How is it billed? Per connected tax ID, with unlimited documents. The tax ID is the axis because it is what consumes the SEFAZ query budget; how many invoices your company receives does not change our cost, so charging for that would make no sense. Current pricing at mcp.ai/dfe.
MIT — see LICENSE. The MCP server at api.mcp.ai/p_dfe is proprietary (hosted); this repo (manifests, docs, skills) is MIT.