Skip to main content
Glama
beel-es

BeeL MCP server

Official
by beel-es

Related Servers

Alternatives to BeeL MCP server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to issue Peruvian electronic invoices (factura/boleta) declared to SUNAT via Nubefact. Supports creating, querying, and canceling invoices with automatic IGV tax computation.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to issue Poland structured e-invoices (faktura ustrukturyzowana) through KSeF 2.0, handling FA(3) XML building, encrypted session flow, and KSeF number retrieval.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to issue Mexico CFDI 4.0 electronic invoices (factura electrónica) via Facturapi, with tools for creating, querying, canceling, and sending invoices.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to create and manage e-invoices through natural language, supporting EU compliance formats like ZUGFeRD and XRechnung, as well as US plain PDF invoices.
      7
      -

    TDQS

    A3.7/5.0

    Scored across 131 tools

    Disambiguation4/5

    Despite the enormous surface, most tools target a distinct resource+action and the long descriptions clarify boundaries. A few subtle pairs remain confusable, such as ensure_default_series vs set_default_series, create_invoice_batch vs the single-invoice creation/issue tools, and bulk vs batch used for similar bulk operations.

    Naming Consistency3/5

    All names share the beel_ prefix and snake_case, but the verb convention is mixed: patch/put (HTTP-derived) sit alongside update/set/ensure/change for similar partial-update operations (patch_product vs update_tax_configuration), and docs/rules/schema tools invert the verb order (docs_list vs list_invoices). Readable but not fully predictable.

    Tool Count1/5

    131 tools is far beyond the 50+ threshold for an extreme mismatch, even for a broad invoicing platform. The set spans invoices, customers, products, series, accounts, members, webhooks, payment connections and docs, but an agent cannot navigate this many tools efficiently.

    Completeness5/5

    The surface covers full CRUD and lifecycle for every apparent domain entity: invoices (create, issue, void, correct, derive, exchange, convert, send, PDF/preview, schedule, status, VeriFactu records), customers, products, series, companies, accounts, members/grants, webhooks, payment connections, representation, tax/VeriFactu config, plus docs, rules and schema helpers.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues