Skip to main content
Glama
octonull

billingo-mcp

by octonull
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to billingo-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • billingo-mcp

      bartadaniel
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for the Billingo V3 Hungarian invoicing API. Manage invoices, partners, products, spendings, and bank accounts from any MCP client.
      4 npm
      1
      MIT

    • Elementary POS MCP

      pedrocastellanos
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to interact with a point-of-sale public API through 32 MCP tools for managing bills, customers, items, orders, receipts, stock, suppliers, taxes, and webhooks over stdio and HTTP transports.
      -

    • SuperFaktura MCP Server

      jurajgh
      A
      license
      Not graded
      quality
      D
      maintenance
      Model Context Protocol (MCP) server for SuperFaktura invoicing system. Enables AI assistants to interact with SuperFaktura API for managing invoices, clients, and expenses.
      Apache 2.0

    • invoiceshelf-mcp

      homeserverhq
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that acts as a secure, multi-tenant proxy to the InvoiceShelf API, enabling AI assistants to manage invoices, estimates, customers, payments, expenses, and more with 109 tools and TOON compression for efficient token usage.
      GPL 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.6/5.0

    Scored across 22 tools

    Disambiguation4/5

    Most tools map cleanly to a distinct resource and action, and the list/get pairs are easy to separate. The main ambiguity is between billingo_download_document and billingo_get_document_public_url, which both return a shareable public URL by default; billingo_pos_print also adds mild PDF-output overlap. Descriptions provide usage guidance, so the confusion is limited to a couple of tools.

    Naming Consistency4/5

    The billingo_ prefix and snake_case verb_noun pattern are used consistently across almost all tools. Minor deviations include billingo_pos_print, which inverts the verb/object order, and billingo_get_online_szamla_status using a Hungarian term, but the overall naming remains predictable.

    Tool Count3/5

    At 22 tools, the server is on the heavy side and requires grouping to navigate, though it covers a broad set of Billingo resources. Some tools overlap in output, such as download_document, get_document_public_url, and pos_print, suggesting a leaner set could be achieved without losing capability.

    Completeness2/5

    The set is strong for reading and exporting Billingo data: list/get for major entities plus PDF download, NAV status, payments, reminders, and export are all covered. However, there are no create/update/delete tools for partners, products, invoices, or spendings, and the descriptions reference creating invoices and partners without offering tools for those actions. This creates significant dead ends for common Billingo workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources