Skip to main content
Glama
nikan

elorus-mcp

by nikan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to elorus-mcp

No user-submitted related servers found.

    Related Servers

    • Elorus MCP Server

      gabrielnika
      A
      license
      A
      quality
      B
      maintenance
      Read-only MCP server for the Elorus invoicing platform, enabling natural language queries about invoices, contacts, expenses, payments, and products.
      10
      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.
      -

    • 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
      19 npm
      2
      MIT
    • docnova-mcp by docnova-ai

      docnova-mcpofficial

      docnova-ai
      A
      license
      A
      quality
      D
      maintenance
      MCP server for e-invoice platforms. Enables natural language querying of invoices, partners, company data, and financial reports.
      18
      14 npm
      6
      MIT

    • mcp-ai-fiskalizacija

      Seyn-Labs
      A
      license
      A
      quality
      C
      maintenance
      MCP server for creating and fiscalizing invoices via solo.com.hr API. Enables AI agents to generate invoices, retrieve invoice details, list invoices, and check next invoice number.
      4
      MIT
    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 43 tools

    Disambiguation5/5

    Each tool targets a specific entity and action, with clear distinctions between similar tools (e.g., list_cash_payments vs list_cash_receipts, list_client_discussions vs list_private_notes). No two tools appear to have overlapping purposes.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_invoice, list_contacts, update_bill). Variations like apply_credit_note or void_invoice still adhere to the same structure.

    Tool Count3/5

    With 43 tools, the server covers a comprehensive accounting domain, but the count exceeds the typical well-scoped range (3-15). While each tool is justified, the sheer number may overwhelm agents or indicate that some operations could be combined.

    Completeness4/5

    The tool surface covers core CRUD for invoices, bills, contacts, expenses, and products, with additional actions like void, export, and apply credits. However, some entities (credit notes, supplier credits, cash receipts/payments) lack dedicated get tools, and there are no delete tools (void is used as an alternative). The gaps are minor and do not severely hinder workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources