Skip to main content
Glama
Sign In
billingo-mcp

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
      13
      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.
      9 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
    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

    B3.4/5.0

    Scored across 22 tools

    Disambiguation4/5

    Most tools target a clearly distinct resource and action (list vs get for partners, products, spendings, bank accounts; document-specific operations like payments, reminders, NAV status, POS print). The main overlap is billingo_download_document vs billingo_get_document_public_url, which both default to returning a shareable public URL, making selection ambiguous.

    Naming Consistency4/5

    Names follow a consistent billingo_ prefix with snake_case verb_noun structure (list_documents, get_partner, export_documents, check_tax_number). Minor deviation: billingo_pos_print uses noun_verb ordering rather than the verb_noun pattern used elsewhere.

    Tool Count3/5

    22 tools is on the heavy side for the rubric, though the broad billing domain (documents, partners, products, spendings, org, bank accounts) partly justifies it. Several simple list/get pairs could potentially be consolidated, placing it at borderline.

    Completeness2/5

    The surface is almost entirely read-only: there are no create/update/delete tools for invoices, partners, products, or spendings, yet descriptions reference creating partners and needing block ids to create invoices, implying write operations that don't exist. Core billing workflows (issuing an invoice, recording a payment) cannot be performed, a significant gap.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources