Skip to main content
Glama
beel-es

BeeL MCP server

Official
by beel-es
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to BeeL MCP server

No user-submitted related servers found.

    Related Servers

    • peru-invoice-mcp

      junter1989k-ai
      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

    • Poland Invoice MCP

      junter1989k-ai
      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

    • Mexico Invoice MCP

      junter1989k-ai
      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

    • Scribo MCP Server

      causa-prima-ai
      F
      license
      Not graded
      quality
      C
      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
      -
    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.9/5.0

    Scored across 121 tools

    Disambiguation4/5

    The systematic beel_<verb>_<resource> naming makes nearly every tool's purpose obvious, and overlapping operations (send_invoice vs create_invoice_delivery, PDF vs preview) are clearly differentiated in thorough descriptions. The main exception is beel_create_invoice_batch, which sounds like bulk invoice creation but actually applies ISSUE/STATUS operations to existing invoices, creating genuine misselection risk.

    Naming Consistency4/5

    The dominant pattern is highly consistent, with create/get/list/patch/delete applied uniformly across customers, products, invoices, series, recurring invoices, members, webhooks, and invitations. Minor deviations: patch vs update is split (beel_patch_company vs beel_update_me, beel_update_tax_configuration), and a few one-off verbs (change_managed_access_level, end_management, put_member_grant) break the otherwise predictable scheme.

    Tool Count2/5

    At 121 tools the set is far beyond the well-scoped range, even granting that the underlying platform genuinely spans invoicing, fiscal compliance, accounts, webhooks, payments, and provisioning. The count is inflated by single/bulk pairs, fine-grained sub-resource splits (schedule, customization, representation, logo), and three docs tools, which together will overwhelm an agent's selection. Significant consolidation is needed for the set to be navigable.

    Completeness4/5

    Coverage is remarkably thorough: the full invoice lifecycle (create, derive, issue, send, schedule, void, correct, proforma conversion), complete CRUD for customers/products/series, recurring invoicing, accounts, members, webhooks, payments, and tax configuration are all present. However, the AEAT representation workflow is a dead end, since the documented submit step has no corresponding tool, and bulk PDF archive/export endpoints referenced in descriptions are absent.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources