Minimax MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MINIMAX_HOST | No | HTTP transport host. The Docker image sets 0.0.0.0. | 127.0.0.1 |
| MINIMAX_PORT | No | HTTP transport port. | 8000 |
| MINIMAX_PASSWORD | Yes | Minimax application password. This is not the Minimax login, but an application password created on the user's profile page under 'Gesla za dostop zunanjih aplikacij' -> 'Nova aplikacija'. | |
| MINIMAX_USERNAME | Yes | Minimax application username. This is not the Minimax login, but an application password created on the user's profile page under 'Gesla za dostop zunanjih aplikacij' -> 'Nova aplikacija'. | |
| MINIMAX_CLIENT_ID | Yes | OAuth2 client ID issued by Minimax support on request, once per integrating application. | |
| MINIMAX_LOG_LEVEL | No | Log level. Logs go to stderr; under stdio, stdout is the protocol channel. | INFO |
| MINIMAX_TOKEN_URL | No | Override for the Minimax token URL, e.g. for an outbound proxy. | |
| MINIMAX_TRANSPORT | No | Transport to use: stdio or streamable-http. The Docker image sets streamable-http. | stdio |
| MINIMAX_API_BASE_URL | No | Override for the Minimax API base URL, e.g. for an outbound proxy. | |
| MINIMAX_LOCALIZATION | No | One of SI, HR or RS: selects host, path and OAuth scope. | SI |
| MINIMAX_CLIENT_SECRET | Yes | OAuth2 client secret issued by Minimax support on request, once per integrating application. | |
| MINIMAX_ORGANISATION_ID | No | Used when a tool call omits organisation_id. Without it, such a call fails with an error that points the model to minimax_list_organisations. | |
| MINIMAX_TIMEOUT_SECONDS | No | Per-request timeout in seconds to Minimax. | 30 |
| MINIMAX_MCP_BEARER_TOKEN | No | HTTP transport bearer token. Required unless the server is bound to loopback. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Tools for the Minimax accounting service (moj.minimax.si / .hr / .rs).
Almost everything belongs to an organisation (company). Call minimax_list_organisations first unless the server has a default organisation configured; pass its ID as organisation_id.
Records are grouped into resources (customers, items, issued_invoices, ...). Before creating or updating a record, call minimax_describe_resource to see its fields. References to other records are written {"ID": }.
Lists are paged: page starts at 1; the result reports TotalRows and has_more.
Updates and most actions are guarded by RowVersion. minimax_update_record and minimax_run_action fetch the current RowVersion themselves; pass row_version only to make sure nothing changed since you last read the record.
Single-letter codes are common: D = yes, N = no; invoice Status O = draft, I = issued; journal Status O = draft, P = confirmed.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| minimax_get_current_userB | Return the profile of the Minimax user this server is logged in as. Returns: str: JSON user profile, or an "Error: ..." string. |
| minimax_list_organisationsB | List the organisations (companies) the API user has access to. Every other tool needs one of these IDs as organisation_id. Returns: str: JSON SearchResult {Rows: [{Organisation: {ID, Name}, APIAccess, MobileAccess}], TotalRows, CurrentPageNumber, PageSize, has_more}. |
| minimax_list_all_organisationsA | List every organisation visible to the user with full organisation details (address, tax number, ...), addressed by row range instead of pages. Mostly useful to accounting firms managing many clients; minimax_list_organisations is the usual starting point. Returns: str: JSON array of organisations, or an "Error: ..." string. |
| minimax_get_organisationB | Return one organisation's details: name, address, tax number, VAT status. Returns: str: JSON organisation, or an "Error: ..." string. |
| minimax_get_dashboardA | Return the organisation's dashboard: issued/received invoice summaries, unpaid invoices, top customers, debtors, suppliers and creditors, and revenue versus expenses. A good first call for "how is the company doing" questions. Returns: str: JSON dashboard, or an "Error: ..." string. |
| minimax_list_issued_invoicesA | List issued invoices (or proforma invoices) with filters for customer, dates, status and payment status. Returns: str: JSON {Rows: [{IssuedInvoiceId, InvoiceNumber, Customer, DateIssued, DateDue, Status, PaymentStatus, InvoiceValue, PaidValue, ...}], TotalRows, CurrentPageNumber, PageSize, has_more}. Examples: - "Unpaid overdue invoices" -> payment_status="NeplacanZapadel" - "Invoices to Novak in March 2026" -> customer_name="Novak", date_issued_from="2026-03-01", date_issued_to="2026-03-31" |
| minimax_list_received_invoicesA | List received (supplier) invoices with filters for supplier, dates, status and payment status. Unprocessed incoming e-invoices are in the inbox instead (minimax_list_inbox). Returns: str: JSON {Rows: [{ReceivedInvoiceId, DocumentReference, Customer, DateIssued, DateDue, Status, PaymentStatus, InvoiceAmount, ...}], ...}. |
| minimax_list_issued_invoice_postingsB | List issued invoice postings: bookings of invoices issued outside Minimax (e.g. by a web shop or cash register) as daily or periodic totals. Returns: str: JSON SearchResult with has_more. |
| minimax_list_ordersB | List sales and purchase orders with filters for type, customer, status and the date of each life-cycle step. Returns: str: JSON SearchResult with has_more. |
| minimax_list_stock_entriesB | List stock entries (goods receipts, issues, own use, transfers). Returns: str: JSON SearchResult with has_more. |
| minimax_list_stockB | List stock quantities and values per item and warehouse, optionally as of a past date or by batch number. Returns: str: JSON SearchResult with has_more. |
| minimax_get_item_stockA | Return the stock of one item, across warehouses or in one. Returns: str: JSON stock record(s), or an "Error: ..." string. |
| minimax_list_journalsA | List general-ledger journals (temeljnice) with filters for type, status and date. Use minimax_get_record (resource="journals") for a journal's entries. Returns: str: JSON SearchResult with has_more. |
| minimax_list_journal_entriesA | List individual general-ledger postings (debit/credit lines) across journals: the basis for account balances, open items of a customer, or what was booked to an account in a period. Returns: str: JSON SearchResult with has_more. Examples: - "What was booked to account 4100 in Q1?" -> account="4100", date_from="2026-01-01", date_to="2026-03-31" |
| minimax_list_journals_vod_standardB | List journals in the Slovenian VOD standard format, the layout used to exchange bookkeeping data between accounting programs. Returns: str: JSON SearchResult with has_more. |
| minimax_list_inboxB | List the inbox: incoming e-invoices, bank statements and other documents waiting to be processed. Approve or reject with minimax_run_action. Returns: str: JSON SearchResult with has_more. |
| minimax_list_outboxA | List the outbox: documents Minimax has sent electronically (issued invoices, delivery notes, payslips). Returns: str: JSON SearchResult with has_more. |
| minimax_find_contacts_by_emailA | Find contact persons by e-mail address across all customers -- the way to get from an incoming e-mail to the customer it belongs to. Returns: str: JSON SearchResult of contacts, each with its Customer reference. |
| minimax_list_postal_codesB | List the postal codes of one country. Returns: str: JSON SearchResult with has_more. |
| minimax_describe_resourceA | Describe a resource without calling Minimax: which operations and actions it supports, which tool lists it, and every field of its records with meaning and allowed codes. Call this before minimax_create_record or minimax_update_record. Returns: str: JSON {resource, label, parent, operations, actions, list_with, fields}. |
| minimax_search_recordsA | Search a code-list style resource (customers, items, accounts, warehouses, employees, currencies, ...) by free text, paged. Invoices, orders, journals, stock and the inbox are not here: they have dedicated minimax_list_* tools with date/status filters. Returns: str: JSON {Rows, TotalRows, CurrentPageNumber, PageSize, has_more}. Rows are summaries; use minimax_get_record for the full record. Examples: - "Find customer Novak" -> resource="customers", search_string="Novak" - "Contacts of customer 123" -> resource="customer_contacts", parent_id=123 |
| minimax_get_recordB | Fetch one complete record, including its RowVersion and nested rows (invoice rows, journal entries, ...). Returns: str: JSON record, or an "Error: ..." string. Examples: - Issued invoice 4711 -> resource="issued_invoices", key="4711" - Item with code "SKU-1" -> resource="items", key="SKU-1", by="code" |
| minimax_list_attachmentsB | List the files attached to an issued or received invoice (the generated PDF, e-invoice XML, scanned originals). Returns: str: JSON array of {AttachmentId, AttachmentFileName, AttachmentMimeType, AttachmentDate[, AttachmentData]}. |
| minimax_list_sync_candidatesA | List IDs of records created, changed or deleted in a time window -- the efficient way to answer "what changed since ..." without paging everything. Returns: str: JSON {Rows: [{ID, RowVersion, RecordDtModified, ...}], TotalRows, ...}. |
| minimax_get_record_pdfA | Render an order, or a stock entry's delivery note, as PDF. For issued invoices use minimax_run_action with action 'generatepdf' instead. Returns: str: JSON with the attachment's file name and MIME type; the base64 data only when include_file_data is true. |
| minimax_create_recordA | Create a record (customer, item, issued invoice, order, journal, ...). New invoices, orders and stock entries are created as drafts; issue or confirm them afterwards with minimax_run_action. Field names are checked against the Minimax schema before anything is sent. Returns: str: JSON of the created record (with its new ID and RowVersion), or an "Error: ..." string. Examples: - New customer -> resource="customers", data={"Name": "Novak d.o.o.", "Address": "Slovenska 1", "PostalCode": "1000", "City": "Ljubljana", "Country": {"ID": }} |
| minimax_create_customer_by_tax_numberA | Create a customer by tax number alone: Minimax fills name and address from the national business register. Faster and less error-prone than minimax_create_record for domestic companies. Returns: str: JSON of the created customer, or an "Error: ..." string. |
| minimax_update_recordA | Change fields of an existing record. Reads the current record, applies
Issued (non-draft) invoices cannot be edited; cancel issuing first with minimax_run_action. Returns: str: JSON of the updated record, or an "Error: ..." string. |
| minimax_delete_recordB | Permanently delete a record. Minimax refuses to delete records already used elsewhere (a customer with invoices, an issued invoice); the error says why. Returns: str: JSON {"ok": true} or an "Error: ..." string. |
| minimax_run_actionA | Run a business action on a record: issue an invoice, cancel issuing, generate its PDF, turn it into a credit note, send an e-invoice; confirm, complete or invoice an order; confirm a stock entry; approve or reject an inbox item. Most actions have accounting consequences (issuing assigns the invoice number and posts it); state what you are about to do before running one. Returns: str: JSON result from Minimax (for copy actions, the new record), or an "Error: ..." string. Examples: - Issue draft invoice 4711 with PDF -> resource="issued_invoices", record_id=4711, action="issueAndGeneratepdf" - Turn order 88 into an invoice -> resource="orders", record_id=88, action="createissuedinvoice" |
| minimax_list_vat_ratesA | List VAT rates valid on a date. Invoice rows reference a rate as {"VatRate": {"ID": }}. Returns: str: JSON {Rows: [{VatRateId, Code, Name, Percent, ...}], ...}. |
| minimax_list_vat_accounting_typesC | List VAT accounting types: how a transaction is treated for VAT (domestic, intra-EU supply, export, reverse charge, ...), as used on journal VAT entries. Returns: str: JSON SearchResult. |
| minimax_get_exchange_rateB | Return the exchange rate of a currency against the home currency on a date (the central bank rate Minimax uses for bookkeeping). Returns: str: JSON exchange rate, or an "Error: ..." string. |
| minimax_get_items_settingsB | Return the organisation's item settings (price decimals, stock valuation, whether item codes are generated), useful before creating items. Returns: str: JSON settings, or an "Error: ..." string. |
| minimax_get_items_dataB | Return items with the data needed to put them on a document for a given customer and warehouse: price, discount, VAT rate, stock. Returns: str: JSON list of item data, or an "Error: ..." string. |
| minimax_get_item_price_listsC | Return price-list prices of items, optionally for one customer, warehouse or item. Returns: str: JSON price lists, or an "Error: ..." string. |
| minimax_get_payroll_settingsA | Return a statutory payroll setting by code (minimum wage, contribution rates, ...) valid on a date. Not organisation-specific. Returns: str: JSON SearchResult of payroll settings. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 37 tools
Most tools target clearly distinct resources or actions, and descriptions explicitly cross-reference each other (e.g. stock vs. stock entries vs. item stock). A few pairs overlap enough to invite misselection: list_organisations vs. list_all_organisations, list_journals vs. list_journals_vod_standard, and create_record vs. create_customer_by_tax_number. The guidance notes help, but an agent still has to read descriptions carefully to pick correctly.
Every tool carries the minimax_ prefix followed by a consistent snake_case verb_noun pattern (list_*, get_*, create_*, update_*, delete_*, search_*, find_*, run_action). Variants like list_all_organisations and list_journals_vod_standard still follow the pattern coherently. No camelCase or ad-hoc naming appears.
At 37 tools the surface is heavy for a single MCP server and exceeds the 25-tool threshold, requiring the agent to navigate many similar list_* tools. While an ERP domain plausibly justifies breadth, several listing tools could be consolidated (e.g. the organisation and stock list variants). The count is a cognitive burden rather than a well-scoped set.
Coverage is broad: full record CRUD, dedicated list tools for invoices/orders/journals/stock/inbox, business actions, attachments, PDFs, VAT rates, exchange rates, and payroll settings. Minor gaps exist, such as no explicit attach/upload tool or payroll data operations, but core workflows are covered end to end.