Skip to main content
Glama
Szotasz

Billingo MCP Server

by Szotasz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Billingo MCP Server

No user-submitted related servers found.

    Related Servers

    • 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.
      5 npm
      1
      MIT

    • billingo-mcp

      octonull
      A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to access the Billingo v3 invoicing API through MCP, providing 49 read/write tools for managing invoices, partners, and related data over stdio or HTTP transports.
      22
      297 npm
      MIT

    • elorus-mcp

      nikan
      A
      license
      A
      quality
      B
      maintenance
      MCP server for the Elorus invoicing and accounting platform, enabling AI assistants to create invoices, manage contacts, and query financial data through natural language.
      43
      4
      MIT

    • invoiceninja-mcp

      ambaloo
      A
      license
      B
      quality
      D
      maintenance
      MCP server for Invoice Ninja v5 API. Enables AI assistants to manage clients, invoices, quotes, payments, and time tracking through natural language.
      32
      16 npm
      2
      MIT

    • freshbooks-mcp-server

      bitovi
      F
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that connects Claude to FreshBooks, enabling reading and management of invoices, clients, expenses, projects, and time entries via natural language.
      1
      -
    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.2/5.0

    Scored across 42 tools

    Disambiguation5/5

    Each tool targets a distinct operation or entity (e.g., documents, partners, products) with no overlap. Even document creation variants (new, from draft, from proforma) are clearly separated by purpose.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., create_document, delete_partner, download_document_export), making the API predictable and easy to navigate.

    Tool Count3/5

    42 tools is high, but it covers a broad billing domain with multiple entities and operations. While justifiable, it exceeds the typical recommended range for an MCP server.

    Completeness5/5

    The tool set covers full CRUD for all major entities (documents, partners, products, bank accounts, spendings, payments) plus additional operations like cancel, copy, send, export, tax check, and currency rates. No obvious gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources