Skip to main content
Glama
gabrielnika

Elorus MCP Server

by gabrielnika
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ELORUS_API_KEYYesPersonal API key (Elorus web app → User Profile)
ELORUS_BASE_URLNoDefaults to https://api.elorus.com/v1.2https://api.elorus.com/v1.2
ELORUS_ORGANIZATION_IDYesElorus web app → Settings → Organization → Organization ID

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
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}.

get_invoiceA

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

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.

get_contactA

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

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.

get_expenseB

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

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.

get_cash_receiptA

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

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.

get_productA

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

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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

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

Resources