Skip to main content
Glama
billingengine

BillingEngine MCP server

Official
by billingengine
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to BillingEngine MCP server

No user-submitted related servers found.

    Related Servers

    • BizDesk MCP

      bikashnayak36331-pixel
      A
      license
      B
      quality
      B
      maintenance
      Enables Claude and other MCP clients to manage a small-business back office, including clients, quotes, invoices, payments, reports, and PDF invoice export, while keeping data in a local SQLite file.
      21
      MIT

    • Invoicer MCP

      InBrief-Inc
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables local desktop AI assistants to query and use invoicing and business data through 15 MCP tools, with no hosted server required.
      MIT

    • elba-mcp

      igor-batrakov
      A
      license
      B
      quality
      C
      maintenance
      Enables MCP clients such as Claude Code, Claude Desktop, and Cursor to work with Kontur.Elba through its public API: finding or creating clients, issuing invoices, acts, and UPDs, obtaining public document links, and tracking payments. It also keeps a local invoice journal with duplicate protection and provides prompt-driven scenarios for invoicing, closing work, and reminding debtors.
      19
      MIT

    • gofact

      kOlapsis
      A
      license
      Not graded
      quality
      A
      maintenance
      Exposes French electronic invoicing as a local stdio MCP server, letting an AI client create EN 16931-compliant Factur-X invoices with guaranteed legal numbering, client and organization management, and invoice history. It can also submit a generated invoice to a French e-invoicing platform (PDP) after explicit confirmation.
      5
      AGPL 3.0
    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 10 tools

    Disambiguation5/5

    Each tool targets a clearly distinct resource and action: customers (find/create/update), invoices (create/update/list/get/download), and payments (record/list). There is no meaningful overlap between tools, and an agent can easily select the right one based on the requested resource and operation.

    Naming Consistency4/5

    All tools use snake_case with a verb_noun pattern, which is highly consistent. The only minor deviation is using 'find_customers' for listing customers while invoices and payments use 'list_*', but this does not create confusion.

    Tool Count5/5

    With 10 tools, the set is well-scoped for a billing engine, covering the core customer, invoice, and payment operations without excessive bloat. Each tool has a clear place in the domain.

    Completeness3/5

    The surface covers create/read/update for customers and invoices plus payment recording, but it lacks a tool to send a draft invoice, which is a critical step because record_payment only works on sent/open invoices. Deletion operations for any entity are also absent, creating notable workflow gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources