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

    • 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

    • Billingo MCP Server

      Szotasz
      A
      license
      B
      quality
      D
      maintenance
      An MCP server for the Billingo invoicing API (v3) that enables AI assistants like Claude to manage invoices, partners, products, expenses, and more through natural language.
      42
      12
      MIT

    • bill4time-mcp

      RosenAdvertising
      A
      license
      C
      quality
      A
      maintenance
      MCP server for Bill4Time providing API coverage for legal billing and time tracking, enabling natural language interaction with clients, projects, time entries, invoices, payments, and more from Claude Desktop.
      59
      125 PyPI
      1
      MIT

    • invox-mcp

      Edgetive
      F
      license
      Not graded
      quality
      D
      maintenance
      Hosted MCP server that enables AI assistants to manage clients, invoices, and expenses via the Invox API, supporting actions like drafting, sending, cancelling, and marking invoices as paid, as well as logging expenses and updating client information.
      -
    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