mcp-nfe-br
mcp-nfe-br provides MCP tools for Brazilian electronic fiscal document workflows: tax ID validation, XML generation/validation/signing, and gated SEFAZ/ADN submission and consultation.
Validate CPF and CNPJ, including the alphanumeric CNPJ format.
Generate unsigned NF-e/NFC-e (model 55/65), NFS-e DPS, and CT-e (model 57, rodoviário) XML.
Validate NF-e/NFC-e, NFS-e (DPS/NFSe), and CT-e XML against bundled XSDs.
Sign documents with ICP-Brasil A1 certificates (PKCS#12) via XML-DSig.
Build 44-character NF-e/NFC-e access keys.
Submit signed NF-e, NFS-e, and CT-e to SEFAZ/ADN; write operations are gated by BR_READ_ONLY/BR_CTE_READ_ONLY and require two-step confirmation.
Consult SEFAZ/ADN service status and query documents: NF-e status, CT-e status, NFS-e status, and DF-e distribution.
Cancel NFS-e and CT-e, and issue CT-e correction letters (CC-e).
CT-e calls require an explicit endpoint_override; v1 supports modal rodoviário and ICMS CST 00 only.
mcp-nfe-br 🇧🇷
Introduction
mcp-nfe-br is an MCP (Model Context Protocol) server providing tools for issuing and validating Brazilian electronic fiscal documents: NF-e (modelo 55), NFC-e (modelo 65), NFS-e Nacional (ADN), and CT-e (modelo 57). This server is part of the mcp-einvoicing-* / mcp-*-* family, built on mcp-einvoicing-core, which provides the base data model, HTTP/OAuth2 utilities, and shared MCP server infrastructure.
Current status (v0.6.5): NF-e/NFC-e (modelo 55/65, schema 4.00) and NFS-e Nacional (ADN, schema v1.01) generation, ICP-Brasil signing, XSD validation, and gated SEFAZ/ADN submission are implemented. NF-e/NFC-e now also covers the 010e_v.1.02 schema delta (DANFE Simplificado Tipo 2 — tpImp=6, cIndOp, ISUFEmit, and the SEFAZ alert-message response group) and the 010f_v.1.04 delta (NT 2026.007 — emit/IE optional for taxpayers exclusively subject to IBS/CBS, produção 2026-11-03) on top of the PL_010d base. CT-e (modelo 57) generation/signing/validation and SEFAZ event submission (cancelamento, Carta de Correção) were added starting v0.6.0 — v1 scope is intentionally narrow: modal rodoviário only, ICMS CST 00 only, and no bundled/verified CT-e webservice endpoint table (every SEFAZ CT-e call requires an explicit endpoint_override). See the "CT-e (modelo 57)" tools section below for the full field-level reference.
Related MCP server: fiscal-mcp
Installation
Requirements
Python ≥ 3.11
mcp-einvoicing-core(installed automatically as a dependency)
Using uv (recommended)
uv add mcp-nfe-brUsing pip
pip install mcp-nfe-brFrom source
git clone https://github.com/cmendezs/mcp-nfe-br.git
cd mcp-nfe-br
uv sync --all-extrasConfiguration
This server needs no credentials to run. The environment variables below are optional safety/logging toggles:
Environment variables
Variable | Description | Default |
| Master switch. Set to | — |
| Set to | — |
| Log level: |
|
Claude Desktop integration
To use this server with Claude, add this configuration to your claude_desktop_config.json file:
{
"mcpServers": {
"nfe-br": {
"command": "uvx",
"args": ["mcp-nfe-br"]
}
}
}For a local development install:
{
"mcpServers": {
"nfe-br": {
"command": "uv",
"args": ["run", "mcp-nfe-br"],
"cwd": "/path/to/mcp-nfe-br"
}
}
}Cursor integration
Cursor supports MCP servers via stdio. Add the configuration in:
Global (all projects):
~/.cursor/mcp.jsonProject (this repository only):
.cursor/mcp.json
{
"mcpServers": {
"nfe-br": {
"command": "uvx",
"args": ["mcp-nfe-br"]
}
}
}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.jsonWorkspace (this repository only):
.kiro/settings/mcp.json
{
"mcpServers": {
"nfe-br": {
"command": "uvx",
"args": ["mcp-nfe-br"],
"disabled": false,
"autoApprove": []
}
}
}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
br__validate_cpf
Validates a CPF (Cadastro de Pessoas Físicas), the individual taxpayer identification number, using the Receita Federal modulo 11 algorithm.
Parameter | Type | Required | Description |
|
| yes | CPF with or without |
Returns a TaxIdValidationResult with valid=True and the cleaned value (11 digits) on success, or valid=False with an error message in Portuguese.
br__validate_cnpj
Validates a CNPJ (Cadastro Nacional da Pessoa Jurídica), the business taxpayer identification number. Accepts both the traditional numeric format (14 digits) and the alphanumeric format introduced by NT 2026.004 (PL_010d), effective in homologation from 2026-06-01 and in production from 2026-07-01.
Parameter | Type | Required | Description |
|
| yes | CNPJ with or without |
Returns a TaxIdValidationResult with valid=True and the cleaned value (14 characters) on success, or valid=False with an error message in Portuguese.
⚠️ [Unverified]: the check-digit algorithm for the alphanumeric CNPJ format was implemented based on secondary sources, as the primary source ("NT Conjunta DFe 2025.001") is not yet available locally.
br__generate_nfe
Generates an unsigned NF-e/NFC-e 4.00 document (<NFe><infNFe>…</infNFe></NFe>) from a BRInvoice object.
Parameter | Type | Required | Description |
|
| yes |
|
Returns {"xml": ..., "chave_acesso": ..., "warnings": [...]}. The warnings in Portuguese remind that the document is not signed (ICP-Brasil) and was not transmitted to SEFAZ. Both steps are the responsibility of a separate process.
Phase 1 coverage for per-item tax groups:
Tax | Supported codes | Behavior |
ICMS | CST | other codes raise |
PIS/COFINS | CST | group omitted if |
IPI | CST | group omitted if |
[NEED: IBS/CBS/Imposto Seletivo — Grupo UB/W03 (NT 2025.002-RTC) not yet modeled].
br__validate_nfe_xml
Validates an NF-e/NFC-e 4.00 XML document against the official PL_010d XSD, patched with the PL_010e_v.1.02 and PL_010f_v.1.04 deltas (local "unsigned" variant, see note below).
Parameter | Type | Required | Description |
|
| no* | XML as a string |
|
| no* | Base64-encoded XML |
* Exactly one of xml_content/xml_base64 must be provided.
Returns {"valid": bool, "errors": [...], "metadata": {"schema_version": ...}}.
[Inference]: the official XSD (
nfe_v4.00.xsd/leiauteNFe_v4.00.xsd, PL_010d) requires<ds:Signature>as a mandatory child of<NFe>. Since Phase 1 generates unsigned documents, this tool validates against a local derived copy (nfe_v4.00_unsigned.xsd) where<ds:Signature>has been made optional (minOccurs="0"). Validation of signed documents (future phase) should use the official XSD without modifications.
br__build_access_key
Builds an access key (chNFe, 44 characters) with a modulo 11 check digit, from the components cUF, dhEmi, issuer CNPJ, model, series, and document number.
Parameter | Type | Required | Description |
|
| yes | IBGE state code (2 digits) |
|
| yes | Issue date/time (ISO 8601) |
|
| yes | Issuer CNPJ (numeric or alphanumeric PL_010d) |
|
| yes |
|
|
| yes | Document series |
|
| yes | Document number |
|
| no | Issuance type (default |
|
| no | Random numeric code (cNF, 8 digits); auto-generated if omitted |
Returns {"chave_acesso": ..., "cnf": ...}.
CT-e (modelo 57) tools
CT-e (Conhecimento de Transporte Eletrônico) coverage started at v0.6.0. v1 scope is intentionally narrow: modal rodoviário only (other modais raise an error), ICMS CST 00 (tributação normal) only, and no bundled/verified SEFAZ CT-e endpoint table — every SEFAZ call below requires an explicit endpoint_override. Since v0.7.0, br__generate_cte also accepts the Reforma Tributária do Consumo (IBS/CBS) fields introduced by NT 2026.002 — imp/IBSCBS, emit/ISUFEmit, and ide/tpPagAnt+gPagAntecipado — with the NT's self-contained business rules enforced at the model layer; rules that require a live SEFAZ database lookup are not checked.
br__generate_cte
Generates an unsigned CT-e 4.00 document (<CTe><infCte>…</infCte></CTe>) from a BRCTeDocument object.
Parameter | Type | Required | Description |
|
| yes |
|
Returns {"xml": ..., "chave_acesso": ..., "warnings": [...]}.
br__validate_cte_xml
Validates a CT-e 4.00 XML document against the bundled PL_CTe_400 XSD (auto-selects the unsigned or official signed schema based on <ds:Signature> presence).
Parameter | Type | Required | Description |
|
| no* | XML as a string |
|
| no* | Base64-encoded XML |
* Exactly one of xml_content/xml_base64 must be provided.
br__consult_cte_sefaz_status
Checks SEFAZ CT-e webservice availability (CTeStatusServicoV4). Read-only, no confirmation required.
br__consult_cte
Queries a CT-e's status by access key (CTeConsultaV4). Read-only, no confirmation required — it queries one already-known document, not a bulk data pull.
br__submit_cte
Submits a signed CT-e to SEFAZ authorization (CTeRecepcaoSincV4, synchronous). The payload is automatically GZip-compressed and Base64-encoded before transmission, per the CT-e MOC. Gated with a two-step confirmation (ConfirmationGate) and BR_CTE_READ_ONLY.
br__cancel_cte
Requests cancellation of an authorized CT-e (event 110111, CTeRecepcaoEventoV4). cStat=135 indicates the cancellation was homologated. Gated.
br__correct_cte
Issues a Carta de Correção Eletrônica (event 110110, CTeRecepcaoEventoV4). Per Art. 58-B of CONVÊNIO/SINIEF 06/89, a CC-e cannot alter tax values, party registration data, or the issue/departure date. Gated.
Not yet implemented: br__distribute_cte_dfe (CTeDistribuicaoDFe) — the bundled specification confirms the request payload shape but not the webservice's method name, WSDL namespace, or message-wrapper element.
Architecture
mcp-nfe-br/
├── src/
│ └── mcp_nfe_br/
│ ├── __init__.py
│ ├── server.py # MCP entry point and tool registration
│ ├── models/
│ │ ├── __init__.py
│ │ └── invoice.py # BRInvoice, BRInvoiceLine, NFeModelo, TipoOperacao
│ ├── standards/
│ │ ├── __init__.py
│ │ └── nfe_generator.py # NFeGenerator — generates unsigned NF-e/NFC-e 4.00
│ ├── validators/
│ │ ├── __init__.py
│ │ └── nfe_xsd.py # NFeXSDValidator — validates against PL_010d XSD (unsigned variant)
│ ├── schemas/nfe/ # Bundled XSDs (official + "_unsigned" variants)
│ ├── tools/
│ │ ├── __init__.py
│ │ ├── validation.py # br__validate_cpf, br__validate_cnpj
│ │ └── generation.py # br__generate_nfe, br__validate_nfe_xml, br__build_access_key
│ └── utils/
│ ├── __init__.py
│ ├── document_ids.py # validate_cpf, validate_cnpj
│ └── access_key.py # build_access_key, access_key_check_digit
├── tests/
│ ├── conftest.py
│ ├── fixtures/
│ ├── test_tools/
│ │ ├── test_validation.py
│ │ └── test_generation.py
│ ├── test_standards/
│ │ └── test_nfe_generator.py
│ ├── test_validators/
│ │ └── test_nfe_xsd.py
│ └── test_utils/
│ └── test_access_key.py
├── specs/nfe/ # Normative material (XSDs, MOC, Technical Notes, not published)
├── audit/
│ ├── audit_vs_core.py
│ └── report.json
├── .github/workflows/publish.yml
├── pyproject.toml
├── RELEASE.md
└── LICENSERelationship with mcp-einvoicing-core
mcp-einvoicing-core provides:
Base Pydantic models for invoices, parties, line items, and validation results (
InvoiceDocument,InvoiceLineItem,TaxIdValidationResult)Shared MCP server infrastructure (
EInvoicingMCPServer)HTTP/OAuth2 client, token cache, structured logging, exception hierarchy
mcp-nfe-br adds Brazil-specific logic:
BRInvoice(extendsInvoiceDocument, as NF-e/NFC-e has no EN 16931 lineage)Group I fields (NCM, CFOP, ICMS/IPI/PIS/COFINS) in
BRInvoiceLineCPF/CNPJ validation (including the alphanumeric CNPJ from NT 2026.004)
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.
Invoices go directly to SEFAZ (NF-e/NFC-e) and the CT-e SEFAZ endpoint with your own digital certificate; no intermediary is involved.
Contributing
Contributions are welcome. Please open an issue to discuss significant changes before submitting a pull request.
git clone https://github.com/cmendezs/mcp-nfe-br.git
cd mcp-nfe-br
uv sync --all-extras
uv run pytest
uv run ruff check src/mcp_nfe_br tests audit
uv run mypy src/mcp_nfe_brOther e-invoicing MCP servers
Country | Server |
🌍 Global | |
🇧🇪 Belgium | |
🇧🇷 Brazil | |
🇫🇷 France | |
🇩🇪 Germany | |
🇮🇳 India | |
🇮🇹 Italy | |
🇲🇽 Mexico | |
🇵🇱 Poland | |
🇸🇬 Singapore | |
🇪🇸 Spain | |
🇦🇪 United Arab Emirates |
License
This project is licensed under Apache 2.0. See LICENSE for details. For the full version history, see CHANGELOG.md.
Available Tools
22 toolsbr__build_access_keyBr Build Access KeyA
Assemble and check-digit a 44-character NF-e/NFC-e access key (chNFe).
Returns a dict with chave_acesso (44 characters) and cnf (the
8-digit random code used, whether provided or generated).
Inputs: nnf (required), c_uf (required), cnpj (required), serie (required), +4 more. Returns: object
br__cancel_cteBr Cancel CteA
Solicita o cancelamento de um CT-e autorizado (evento 110111, CTeRecepcaoEventoV4).
Constrói, assina (build_cte_event_signer, alvo infEvento) e submete
o evento de cancelamento. cStat=135 indica cancelamento homologado
[Verified locally] — MOC CT-e Visão Geral v4.00 §6.2.2.
Cancelamento é uma operação irreversível em produção e exige
confirmação em duas etapas (ConfirmationGate). Define
BR_CTE_READ_ONLY=1 para desabilitar. endpoint_override é
obrigatório — nenhuma URL de endpoint CT-e está embutida/verificada
nesta versão.
Retorna cStat/xMotivo ou error.
Inputs: cnpj (required), ch_cte (required), n_prot (required), x_just (required), +7 more. Returns: object
br__cancel_nfseBr Cancel NfseA
Solicitar cancelamento de uma NFS-e no ADN.
Cancelamento é uma operação irreversível e exige confirmação em duas
etapas (ConfirmationGate). Defina BR_READ_ONLY=1 para desabilitar.
[Unverified — endpoint e formato de requisição são inferidos.]
Inputs: motivo (required), ch_nfse (required), client_id (required), client_secret (required), +4 more. Returns: object
br__consult_cteBr Consult CteA
Consulta a situação de um CT-e por chave de acesso (CTeConsultaV4).
Read-only — não requer confirmação (consulta um CT-e específico e já
conhecido pela chave de acesso, não um lote de dados fiscais de
terceiros — diferente de br__distribute_dfe no NF-e). Nenhuma URL de
endpoint CT-e está embutida/verificada nesta versão —
endpoint_override é obrigatório.
Retorna cStat/xMotivo/protCTe (quando aplicável) ou error.
Inputs: c_uf (required), ch_cte (required), cert_path (required), endpoint_override (required), +2 more. Returns: object
br__consult_cte_sefaz_statusBr Consult Cte Sefaz StatusA
Consulta a disponibilidade do webservice SEFAZ CT-e (CTeStatusServicoV4).
Read-only — não requer confirmação. Nenhuma URL de endpoint CT-e está
embutida/verificada nesta versão — endpoint_override é obrigatório
(ver mcp_nfe_br.standards.sefaz_cte_client docstring).
Retorna cStat/xMotivo (cStat=107 indica serviço em operação
[Unverified], mesmo código do padrão NF-e).
Inputs: c_uf (required), cert_path (required), endpoint_override (required), tp_amb, +1 more. Returns: object
br__consult_nfse_statusBr Consult Nfse StatusA
Consultar o status de uma NFS-e pelo chave de acesso (chNFSe).
Read-only, não requer confirmação.
[Unverified — endpoint e formato de resposta são inferidos.]
Inputs: ch_nfse (required), client_id (required), client_secret (required), scope, +2 more. Returns: object
br__consult_sefaz_statusBr Consult Sefaz StatusA
Consulta a disponibilidade do webservice SEFAZ (NFeStatusServico4).
Read-only — não requer confirmação. Retorna cStat/xMotivo (cStat=107
indica serviço em operação [Unverified]).
Inputs: c_uf (required), cert_path (required), tp_amb, cert_password, +1 more. Returns: object
br__correct_cteBr Correct CteA
Emite uma Carta de Correção Eletrônica para um CT-e (evento 110110, CTeRecepcaoEventoV4).
Constrói, assina (build_cte_event_signer, alvo infEvento) e submete
o evento de CC-e. cStat=135 indica CC-e homologada [Verified locally] — MOC CT-e Visão Geral v4.00 §6.4. Por força do Art. 58-B do
CONVÊNIO/SINIEF 06/89, a CC-e não pode alterar valores de impostos,
dados cadastrais das partes, ou a data de emissão/saída.
Exige confirmação em duas etapas (ConfirmationGate). Define
BR_CTE_READ_ONLY=1 para desabilitar. endpoint_override é
obrigatório.
Retorna cStat/xMotivo ou error.
Inputs: cnpj (required), ch_cte (required), c_orgao (required), cert_path (required), +6 more. Returns: object
br__distribute_dfeBr Distribute DfeA
Consulta/distribui DF-e via NFeDistribuicaoDFe (NT2014.002_v1.30, [Verified locally]).
Exatamente um de ult_nsu, nsu, ou ch_nfe deve ser informado,
selecionando distNSU, consNSU, ou consChNFe respectivamente.
Esta ferramenta consulta dados fiscais de terceiros vinculados ao
certificado e requer confirmação em duas etapas. Define
BR_READ_ONLY=1 para desabilitar.
Inputs: cert_path (required), c_uf_autor (required), document_id (required), nsu, +7 more. Returns: object
br__generate_cteBr Generate CteA
Generate an unsigned CT-e XML (modelo 57, schema 4.00).
v1 supports modal rodoviário only and ICMS CST 00 (tributação normal)
only — other modais/CSTs raise an error. The returned
<CTe><infCte>…</infCte></CTe> document does not include
<Signature> — sign it with br__sign_cte (roadmap BR-CTE-6 factory,
tool not yet registered) before SEFAZ submission.
Returns a dict with:
xml: the generated CT-e XML stringchave_acesso: the computed 44-character access key (chCTe)warnings: list of non-fatal notices
Inputs: cte (required). Returns: object
br__generate_nfeBr Generate NfeA
Generate an unsigned NF-e/NFC-e XML (modelo 55/65, schema 4.00).
The returned <NFe><infNFe>…</infNFe></NFe> document does not include
<Signature> — sign it with br__sign_nfe before SEFAZ submission.
SEFAZ webservice submission itself is not implemented in this phase.
Returns a dict with:
xml: the generated NF-e/NFC-e XML stringchave_acesso: the computed 44-character access key (chNFe)warnings: list of non-fatal notices
Inputs: invoice (required). Returns: object
br__generate_nfseBr Generate NfseA
Gerar um DPS não assinado para NFS-e Nacional (ADN), schema v1.01.
O DPS (Declaração de Prestação de Serviços) gerado não contém
<ds:Signature> — assine-o com br__sign_nfse antes de submeter
ao ADN via br__submit_nfse.
Returns a dict with:
xml: the generated unsigned DPS XML stringdps_id: the 45-character DPS Id (infDPS Idattribute)warnings: list of non-fatal notices
Inputs: dps (required). Returns: object
br__sign_nfeBr Sign NfeA
Apply an ICP-Brasil enveloped XML-DSig signature to an NF-e/NFC-e XML.
Signs <infNFe> per MOC 7.0 Table 4-2 (RSA-SHA1 / SHA-1, enveloped
transform, ds:Signature appended as the last child of <NFe>) using
mcp_nfe_br.standards.nfe_signer.build_nfe_signer.
Only ICP-Brasil A1 (PKCS#12 file-based) certificates are supported.
A3 (hardware token/HSM) certificates [NEED: not modeled].
Returns a dict with xml (the signed document) or error.
Inputs: cert_path (required), xml_base64, xml_content, cert_password. Returns: object
br__sign_nfseBr Sign NfseA
Aplicar assinatura XML-DSig ICP-Brasil ao DPS da NFS-e Nacional.
Assina o elemento <infDPS> com enveloped ds:Signature adicionada
como último filho de <DPS>, usando
mcp_nfe_br.standards.nfse_signer.build_nfse_signer.
Algoritmo: RSA-SHA1 (padrão XMLDSigSigner).
[Unverified para NFS-e Nacional — confirme no manual ADN antes de usar em produção.]
Somente certificados A1 (PKCS#12 em arquivo) são suportados.
A3 (hardware token/HSM) [NEED: não modelado].
Returns a dict with xml (the signed DPS) or error.
Inputs: cert_path (required), xml_base64, xml_content, cert_password. Returns: object
br__submit_cteBr Submit CteA
Submete um CT-e assinado à autorização SEFAZ (CTeRecepcaoSincV4, síncrono).
O payload é automaticamente compactado em GZip e codificado em Base64
antes do envio, conforme exigido pelo MOC CT-e §3.4.1 [Verified locally].
Submissão para SEFAZ é uma operação irreversível em produção e exige
confirmação em duas etapas (ConfirmationGate). Define
BR_CTE_READ_ONLY=1 para desabilitar esta ferramenta. Nenhuma URL de
endpoint CT-e está embutida/verificada nesta versão —
endpoint_override é obrigatório.
Retorna protCTe (incluindo nProt, o protocolo de autorização) em
caso de sucesso, ou error.
Inputs: c_uf (required), cert_path (required), endpoint_override (required), tp_amb, +4 more. Returns: object
br__submit_nfeBr Submit NfeA
Submete um NF-e/NFC-e assinado à autorização SEFAZ (NFeAutorizacao4, síncrono).
Submissão para SEFAZ é uma operação irreversível em produção e exige
confirmação em duas etapas (ConfirmationGate). Define BR_READ_ONLY=1
para desabilitar esta ferramenta.
Retorna protNFe (incluindo nProt, o protocolo de autorização) em
caso de sucesso, ou error.
Inputs: c_uf (required), id_lote (required), cert_path (required), tp_amb, +5 more. Returns: object
br__submit_nfseBr Submit NfseA
Submeter um DPS assinado ao ADN para geração da NFS-e Nacional.
Submissão ao ADN é uma operação irreversível em produção e exige
confirmação em duas etapas (ConfirmationGate). Defina BR_READ_ONLY=1
para desabilitar esta ferramenta.
[Unverified — endpoint ADN, formato de requisição e resposta são inferidos de fontes secundárias. Verifique no manual ADN antes do uso em produção.]
Retorna campos de status do ADN (cStat, xMotivo) e opcionalmente
o XML da NFS-e gerada (nfse_xml).
Inputs: client_id (required), client_secret (required), scope, tp_amb, +4 more. Returns: object
br__validate_cnpjBr Validate CnpjA
Validate a Brazilian CNPJ (company tax ID).
Accepts both the legacy all-numeric form (14 digits) and the alphanumeric form introduced by NT 2026.004 / PL_010d (12 alphanumeric characters + 2 numeric check digits, production from 2026-07-01).
Inputs: cnpj (required). Returns: Typed result returned by BasePartyValidator.validate_tax_id. valid: True when t…
br__validate_cpfBr Validate CpfB
Validate a Brazilian CPF (individual taxpayer ID).
Inputs: cpf (required). Returns: Typed result returned by BasePartyValidator.validate_tax_id. valid: True when t…
br__validate_cte_xmlBr Validate Cte XmlA
Validate a CT-e XML (modelo 57, schema 4.00) against the bundled PL_CTe_400 XSD.
CTeXSDValidator selects the schema automatically: documents without a
<ds:Signature> are validated against the unsigned derivative; signed
documents are validated against the unmodified official schema, which
requires <ds:Signature>.
Returns a dict with valid, errors, warnings, and schema_version.
Inputs: xml_base64, xml_content. Returns: object
br__validate_nfe_xmlBr Validate Nfe XmlA
Validate an NF-e/NFC-e XML (modelo 55/65, schema 4.00) against the bundled PL_010d XSD.
NFeXSDValidator selects the schema automatically: documents without a
<ds:Signature> are validated against the unsigned derivative; signed
documents (produced by br__sign_nfe) are validated against the
unmodified official schema, which requires <ds:Signature>.
Returns a dict with valid, errors, warnings, and schema_version.
Inputs: xml_base64, xml_content. Returns: object
br__validate_nfse_xmlBr Validate Nfse XmlA
Validar um DPS ou NFSe contra o XSD v1.01 do ADN.
Seleciona automaticamente o schema com base no elemento raiz:
<DPS>→ valida contraDPS_v1.01.xsd(<ds:Signature>opcional)<NFSe>→ valida contraNFSe_v1.01.xsd(<ds:Signature>obrigatória)
Returns a dict with valid, errors, warnings, and schema_version.
Inputs: xml_base64, xml_content. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 22 tools
Each tool targets a distinct document type and action (NF-e, NFS-e, CT-e, CNPJ/CPF, SEFAZ status). Even similar status or validation tools are clearly separated by resource and described with different schemas and workflows.
All tools follow a br__verb_noun snake_case pattern with consistent verbs like generate, sign, validate, submit, cancel, and consult. Minor inconsistencies exist, such as consult_sefaz_status missing the nfe qualifier while its CT-e counterpart is consult_cte_sefaz_status.
At 22 tools, this is a heavy surface and sits in the 16–25 range that feels oversized for a single server. The breadth is somewhat justified by covering NF-e, NFS-e, and CT-e lifecycles, but the count still strains coherence.
The CT-e workflow has a significant dead end: generate_cte returns an unsigned document but the referenced br__sign_cte tool is not registered, so agents cannot produce a submittable CT-e. Additionally, NF-e lacks cancellation and correction event tools, leaving a notable lifecycle gap despite solid NF-e and NFS-e coverage.
Maintenance
Related MCP Connectors
Brazilian fiscal MCP server - issue NF-e, NFC-e, NFS-e, CT-e, MDF-e and DC-e via SEFAZ.
Issue and manage Brazilian fiscal documents: NF-e for goods, NFS-e for services.
Ferramentas MCP para NF-e, NFS-e, documentos, certificados e tributos brasileiros.
Brazilian e-invoicing (NF-e, NFC-e, NFS-e): issue, cancel and query fiscal documents, plus AP/AR.
Related MCP Servers
- AlicenseAqualityBmaintenanceModel Context Protocol (MCP) server for Spanish Electronic Invoicing. Provides tools to generate, validate, and submit invoices across VERI\*FACTU, Facturae/FACe, SII, TicketBAI, and Crea y Crece B2B.2042 PyPI3Apache 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server to validate Brazilian fiscal documents (NF-e and NFS-e) locally before transmission, offering actionable feedback without requiring certificates or sending data anywhere.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that queries Brazilian electronic invoice (NF-e) numbering invalidations for a company by CNPJ and year. Read-only, hosted, works with any MCP client over HTTP.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for consulting NFC-e (Brazilian electronic consumer invoices) from SEFAZ MA (Maranhão state tax authority) via official sources. Read-only, works with any MCP client over HTTP.MIT