MCP Nfe Br MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add mcp-nfe-br -- uvx mcp-nfe-br

{
  "mcpServers": {
    "mcp-nfe-br": {
      "command": "uvx",
      "args": [
        "mcp-nfe-br"
      ]
    }
  }
}

[mcp_servers.mcp-nfe-br]
command = "uvx"
args = ["mcp-nfe-br"]

{
  "mcpServers": {
    "mcp-nfe-br": {
      "command": "uvx",
      "args": [
        "mcp-nfe-br"
      ]
    }
  }
}

{
  "servers": {
    "mcp-nfe-br": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "mcp-nfe-br"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: BR_READ_ONLY (Master switch. Set to '1' to disable all write-side tools across NF-e, NFC-e, NFS-e, AND CT-e (br__submit_nfe, br__distribute_dfe, br__submit_nfse, br__cancel_nfse, br__submit_cte, br__cancel_cte, br__correct_cte). Read-only mode for safe exploration. Setting only this variable is sufficient to disable all CT-e writes too — BR_CTE_READ_ONLY is an additional, independent gate, not a required second step), BR_CTE_READ_ONLY (Set to '1' to disable the three CT-e write-side tools (br__submit_cte, br__cancel_cte, br__correct_cte). Independent of BR_READ_ONLY — either variable being set to '1' is sufficient to block CT-e writes; use this one to gate CT-e alone while leaving NF-e/NFS-e writes enabled), LOG_LEVEL (Logging level: DEBUG, INFO (default), WARNING, or ERROR).