elorus-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ELORUS_ORG_ID | Yes | Your Elorus organization ID | |
| ELORUS_API_KEY | Yes | Your Elorus API key |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_contactsA | List and search contacts (clients, suppliers, or both). Returns paginated results with count and pagination links. |
| get_contactB | Fetch a single contact by its Elorus ID. |
| create_contactB | Create a new contact (client, supplier, or both). Requires either 'company' (for businesses) or at least one of 'first_name'/'last_name' (for individuals). |
| update_contactB | Update fields on an existing contact. Only provided fields are changed (PATCH semantics). |
| list_invoicesB | List and filter sales invoices. Returns paginated results with count and pagination links. |
| get_invoiceB | Fetch a single invoice by its Elorus ID. |
| create_invoiceA | Create a new sales invoice. Monetary values must be strings (e.g. '1500.00') to avoid floating-point issues. Use list_taxes and list_document_types to obtain valid IDs before calling this tool. |
| void_invoiceA | Void an invoice. A voided invoice cannot be edited or paid and is excluded from financial reports. |
| send_invoice_emailA | Email an invoice to the client. Uses the organization's default email template unless overridden. |
| export_invoice_pdfA | Export an invoice as a PDF. Returns a download URL for the generated PDF file. |
| list_productsB | List and search products and services from the catalog. Returns paginated results. |
| get_productA | Fetch a single product or service by its Elorus ID. |
| create_productB | Create a new product or service in the catalog. Monetary values must be strings (e.g. '99.99') to avoid floating-point issues. |
| update_productA | Update fields on an existing product or service. Only provided fields are changed (PATCH semantics). |
| list_taxesA | List all tax rates configured in this organization. Returns tax IDs and rates needed when creating invoices, products, and expenses. |
| list_document_typesA | List all document types available in this organization. Returns document type IDs and names required when creating invoices, bills, and other documents. |
| list_unitsA | List all units of measurement configured in this organization. Returns unit IDs and names used when creating products (e.g. hours, pieces, kg). |
| list_expense_categoriesA | List all expense categories configured in this organization. Returns category IDs and names used when creating expenses. |
| list_cash_receiptsA | List payments received from clients. Returns paginated results. Filter by client, invoice, or date range. |
| record_cash_receiptA | Record a payment received from a client. Optionally links the payment to a specific invoice. Monetary amounts must be strings (e.g. '500.00'). |
| export_cash_receipt_pdfB | Export a cash receipt as a PDF. Returns a download URL for the generated PDF file. |
| list_cash_paymentsA | List payments made to suppliers. Returns paginated results. Filter by supplier, bill, or date range. |
| record_cash_paymentB | Record a payment made to a supplier. Optionally links the payment to a specific bill. Monetary amounts must be strings (e.g. '250.00'). |
| list_credit_notesA | List credit notes issued to clients. Returns paginated results. Filter by client or date range. |
| create_credit_noteA | Create a credit note to reduce or cancel an amount owed by a client. Use list_taxes and list_document_types to obtain valid IDs before calling this tool. |
| apply_credit_noteA | Apply a credit note against an open invoice to reduce the amount owed. The credit note and invoice must belong to the same client. |
| list_supplier_creditsA | List supplier credit notes (credits received from suppliers). Returns paginated results. Filter by supplier or date range. |
| create_supplier_creditA | Record a credit note received from a supplier (e.g. a refund or price correction on a bill). Use list_taxes and list_document_types to obtain valid IDs. |
| apply_supplier_creditB | Apply a supplier credit against an open bill to reduce the amount owed to the supplier. |
| list_expensesA | List expense records. Returns paginated results. Filter by supplier, category, or date range. |
| get_expenseA | Fetch a single expense record by its Elorus ID. |
| create_expenseB | Record a new business expense. Use list_taxes, list_document_types, and list_expense_categories to obtain valid IDs before calling this tool. |
| update_expenseA | Update fields on an existing expense. Only provided fields are changed (PATCH semantics). |
| export_expense_pdfA | Export an expense document as a PDF. Returns a download URL for the generated PDF file. |
| list_billsA | List supplier bills (purchase invoices). Returns paginated results. Filter by supplier, status, or date range. |
| get_billA | Fetch a single supplier bill by its Elorus ID. |
| create_billC | Create a supplier bill (purchase invoice). Use list_taxes and list_document_types to obtain valid IDs before calling this tool. |
| update_billB | Update fields on an existing bill. Only provided fields are changed (PATCH semantics). |
| void_billA | Void a supplier bill. A voided bill is excluded from financial reports and cannot be paid. |
| list_private_notesA | List internal (private) notes attached to an Elorus resource (invoice, contact, payment, etc.). Notes are visible only to organization members. |
| create_private_noteA | Add an internal (private) note to an Elorus resource. Notes are visible only to organization members, not to clients. |
| list_client_discussionsA | List client-visible discussion messages attached to an Elorus resource. These are visible to both the organization and the client. |
| create_client_discussionA | Post a client-visible message on an Elorus resource (invoice or cash receipt). The client can see this message in their client portal. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| contacts | All contacts (clients and suppliers) in the organization. Returns up to 100 contacts. |
| invoices | All sales invoices in the organization. Returns up to 100 invoices ordered by most recent. |
| cashreceipts | All cash receipts (payments received from clients). Returns up to 100 records. |
| cashpayments | All cash payments (payments made to suppliers). Returns up to 100 records. |
| expenses | All expense records in the organization. Returns up to 100 expenses. |
| bills | All supplier bills (purchase invoices) in the organization. Returns up to 100 bills. |
| products | All products and services in the organization catalog. Returns up to 100 items. |
TDQS
Scored across 43 tools
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.
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.
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.
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.