Skip to main content
Glama
gabrielnika

Elorus MCP Server

by gabrielnika

Related Servers

Alternatives to Elorus MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      A
      quality
      B
      maintenance
      Read-only MCP server for the Greek AADE myDATA e-books API, enabling natural language queries about invoices, income, and expenses with decoded bilingual labels.
      4
      1
      MIT
    • 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
    • A
      license
      A
      quality
      D
      maintenance
      Read-only MCP server for accessing Wallet by BudgetBakers financial data, allowing users to query accounts, transactions, categories, budgets, and more via natural language.
      10
      MIT
    • 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
    • A
      license
      Not graded
      quality
      D
      maintenance
      Read-only MCP server for Omie ERP, enabling AI assistants to query financial data, accounts payable/receivable, bank reconciliation, invoices, and movements via natural language.
      12
      MIT

    TDQS

    A4/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct entity (invoices, contacts, expenses, cash receipts, products) and action (list vs get). The list tools return summaries with filters, while get tools return full records by ID, so there is no overlap or ambiguity.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern: list_<plural> and get_<singular> (e.g., list_invoices, get_invoice). The naming is uniform, lowercase, and predictable.

    Tool Count5/5

    With 10 tools covering 5 core entities via list/get pairs, the tool count is well-scoped. Each tool earns its place and there is no redundancy or bloat.

    Completeness2/5

    The server is entirely read-only, providing only list and get operations. There are no create, update, or delete tools for any entity, which is a significant gap that prevents agents from performing common accounting workflows like creating invoices or modifying contacts.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues