Skip to main content
Glama
cmendezs

mcp-nfe-br

by cmendezs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-nfe-br

No user-submitted related servers found.

    Related Servers

    • fiscal-mcp

      JoseTorquato
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP 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

    • mcp-cfdi-mx

      cmendezs
      A
      license
      A
      quality
      A
      maintenance
      Model Context Protocol (MCP) server for Mexican Electronic Invoicing (CFDI 4.0, Complemento de Pagos 2.0). Provide tools to validate, generate, and explore API specifications for SAT/PAC interoperability.
      6
      150 PyPI
      Apache 2.0

    • mcp-facturacion-electronica-es

      cmendezs
      A
      license
      A
      quality
      A
      maintenance
      Model 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.
      20
      2
      Apache 2.0

    • SEFAZ RS: NFC-e Resumida

      mcp-dir
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for querying summarized Brazilian NFC-e (electronic invoice) data from the official SEFAZ RS source. It provides a read-only tool for consulting tax invoice summaries via natural language in any MCP-compatible client.
      MIT

    • SEFAZ MA: NFC-e

      mcp-dir
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP 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
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 22 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count3/5

    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.

    Completeness2/5

    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

    ActivityActive
    ResponsivenessWithin a week

    Resources