Skip to main content
Glama
Elorus MCP Server

Elorus MCP Server

by gabrielnika

Elorus MCP Server

A read-only Model Context Protocol server for the Elorus invoicing platform — ask your business data questions in plain language.

CI Python License

Unofficial & read-only. This project is not affiliated with Elorus. It only ever issues GET requests — it cannot create, modify, or delete anything in your organization.

What can you ask?

  • "Which invoices are overdue, and for how much?"

  • "How much did we invoice ACME Ltd in July?"

  • "What did we spend on hosting last month?"

  • "Which payments did we receive this week?"

  • "What is the VAT number of client X?"

Related MCP server: invoiceninja-mcp

Features

  • 10 read-only tools covering invoices, contacts, expenses, cash receipts and products (Elorus API v1.2)

  • Curated filters — period, status, paid/unpaid, overdue, client/supplier, free-text search — documented in every tool schema so the LLM calls them correctly

  • Token-efficient responses — list tools return trimmed summaries; get_* tools return the full record

  • Read-only by construction — the HTTP client implements GET only

  • Clear error messages for authentication, rate-limit and connectivity problems

Architecture

flowchart LR
    A["MCP client (Claude Desktop / Claude Code)"] -- stdio --> B["elorus-mcp (MCP Python SDK)"]
    B --> C["ElorusClient (GET-only, httpx)"]
    C -- "Authorization: Token + X-Elorus-Organization" --> D["Elorus API v1.2"]

Quickstart

1. Get your credentials

  • API key: Elorus web app → User Profile → API token

  • Organization ID: Elorus web app → Settings → Organization → Organization ID

2. Configure your MCP client

Claude Desktop (claude_desktop_config.json):

{
  "mcpServers": {
    "elorus": {
      "command": "uvx",
      "args": ["--from", "git+https://github.com/nikagabriel741agent/Elorus-ERP-MCP-Server", "elorus-mcp"],
      "env": {
        "ELORUS_API_KEY": "your-api-key",
        "ELORUS_ORGANIZATION_ID": "your-organization-id"
      }
    }
  }
}

Claude Code:

claude mcp add elorus \
  -e ELORUS_API_KEY=your-api-key \
  -e ELORUS_ORGANIZATION_ID=your-organization-id \
  -- uvx --from git+https://github.com/nikagabriel741agent/Elorus-ERP-MCP-Server elorus-mcp

Local development install

git clone https://github.com/nikagabriel741agent/Elorus-ERP-MCP-Server.git
cd Elorus-ERP-MCP-Server
uv sync
cp .env.example .env   # fill in your credentials
uv run --env-file .env elorus-mcp

Tools

Tool

Description

Key arguments

list_invoices

List sales invoices (summaries)

period_from, period_to, status, paid, overdue, draft, client, search, ordering, page, page_size

get_invoice

Full invoice record

invoice_id

list_contacts

List clients & suppliers

search, contact_type (client/supplier), active, page, page_size

get_contact

Full contact record

contact_id

list_expenses

List expenses

period_from, period_to, supplier, search, page, page_size

get_expense

Full expense record

expense_id

list_cash_receipts

List payments received

period_from, period_to, contact, invoice, transaction_type, page, page_size

get_cash_receipt

Full cash receipt record

cash_receipt_id

list_products

List products & services

search, active, sales, purchases, page, page_size

get_product

Full product record

product_id

Notes: dates are YYYY-MM-DD; period_from/period_to only apply when both are set. Invoice status is one of draft, pending, issued, partial, unpaid, overdue, paid, void.

Configuration

Environment variable

Required

Description

ELORUS_API_KEY

yes

Personal API key (Elorus web app → User Profile)

ELORUS_ORGANIZATION_ID

yes

Elorus web app → Settings → Organization → Organization ID

ELORUS_BASE_URL

no

Defaults to https://api.elorus.com/v1.2

Development

uv sync                        # install dependencies
uv run pytest -v               # run the test suite (no real API calls)
uv run ruff check .            # lint
uv run ruff format --check .   # formatting

License

MIT

Available Tools

10 tools
get_cash_receiptA

Get the complete record of a single cash receipt by its Elorus ID.

Inputs: cash_receipt_id (required).

get_contactA

Get the complete record of a single contact by its Elorus ID.

Inputs: contact_id (required).

get_expenseB

Get the complete record of a single expense by its Elorus ID.

Inputs: expense_id (required).

get_invoiceA

Get the complete record of a single sales invoice by its Elorus ID.

Inputs: invoice_id (required).

get_productA

Get the complete record of a single product or service by its Elorus ID.

Inputs: product_id (required).

list_cash_receiptsA

List cash receipts (payments received) with summary fields.

Filters:

  • period_from / period_to: date range, YYYY-MM-DD; only applied when BOTH are given.

  • contact: Elorus contact ID of the payer.

  • invoice: Elorus invoice ID the payment applies to.

  • transaction_type: 'dp', 'ip' or 'cnp' (Elorus transaction type codes). Returns {count, page, results}; use get_cash_receipt for the full record.

Inputs: page, contact, invoice, page_size, +3 more.

list_contactsA

List contacts (clients and suppliers) with summary fields.

Filters:

  • search: free-text search (name, VAT number, email, ...).

  • contact_type: 'client' or 'supplier'.

  • active: True = active contacts, False = archived. Returns {count, page, results}; use get_contact for the full record.

Inputs: page, active, search, page_size, +1 more.

list_expensesA

List expenses (purchase documents) with summary fields.

Filters:

  • period_from / period_to: date range, YYYY-MM-DD; only applied when BOTH are given.

  • supplier: Elorus contact ID of the supplier (find it with list_contacts).

  • search: free-text search term. Returns {count, page, results}; use get_expense for the full record.

Inputs: page, search, supplier, page_size, +2 more.

list_invoicesA

List sales invoices with summary fields; use get_invoice for full details.

Filters:

  • period_from / period_to: issue-date range, YYYY-MM-DD; only applied when BOTH are given.

  • status: one of draft, pending, issued, partial, unpaid, overdue, paid, void.

  • paid: True = fully paid invoices only, False = not fully paid.

  • overdue: True = overdue invoices only.

  • draft: True = drafts only, False = finalized only.

  • client: Elorus contact ID of the client (find it with list_contacts).

  • search: free-text search term (number, client name, etc.).

  • ordering: comma-separated sort fields, prefix with '-' for descending, e.g. '-date' or 'client__display_name'. Returns {count, page, results}.

Inputs: page, paid, draft, client, +7 more.

list_productsA

List products and services with summary fields.

Filters:

  • search: free-text search (title, code, ...).

  • active: True = active items, False = archived.

  • sales: True = items sold to clients.

  • purchases: True = items purchased from suppliers. Returns {count, page, results}; use get_product for the full record.

Inputs: page, sales, active, search, +2 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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.

    Related MCP Connectors

    Related MCP Servers

    • 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
      11 npm
      6
      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
      20 npm
      2
      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
      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
      5
      MIT