Skip to main content
Glama
moneys3-mcp

moneys3-mcp

moneys3-mcp

License: MIT Node.js Version TypeScript

MCP server for Money S3 — the Czech/Slovak accounting system by Seyfor. Connects any MCP-compatible AI client to your Money S3 data via the official GraphQL API.

83 tools covering invoices, contacts, stock, banking, documents, accounting, payroll, controlling and code lists (read, create, update, delete), plus a raw GraphQL tool.

Prerequisites

Money S3 with the API module installed and configured:

  1. API installed on the PC running Money S3 (selected during installation wizard)

  2. API extension module purchased in Money S3

  3. API Key generated: Tools → XML Data Exchange → API Keys → Add & Generate

  4. App ID obtained from money.cz/navod/api-v-money-s3-pro-vyvojare

  5. S3 Automatic task S3Api – fronta XML importu (S3Api – XML import queue) added: Tools → S3 Automatic → Add task. Required for writes: without it every write stays UNPROCESSED. One task serves all agendas and starts by itself when the queue has work.

Related MCP server: SimpleShop MCP

Installation

git clone https://github.com/hlebtkachenko/moneys3-mcp.git
cd moneys3-mcp
npm ci
npm run build

Configuration

Environment Variables

Variable

Description

Required

MONEYS3_DOMAIN

Your domain prefix (the {name} part of {name}.api.moneys3.eu)

Yes

MONEYS3_APP_ID

Application ID from money.cz registration

Yes

MONEYS3_CLIENT_ID

Client ID from Money S3 API Key

Yes

MONEYS3_CLIENT_SECRET

Client Secret from Money S3 API Key

Yes

MONEYS3_AGENDA_GUID

Default agenda GUID (skip m3_set_agenda step)

No

MONEYS3_CACHE_TTL

Response cache lifetime in seconds (default: 120, 0 to disable)

No

MONEYS3_MAX_RETRIES

Max retries for reads that time out and for any request answered 401 or 429 (default: 3). Mutations are never resent after a timeout

No

MCP Client Setup

Cursor

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "moneys3": {
      "command": "node",
      "args": ["/absolute/path/to/moneys3-mcp/dist/index.js"],
      "env": {
        "MONEYS3_DOMAIN": "yourcompany",
        "MONEYS3_APP_ID": "your-app-id",
        "MONEYS3_CLIENT_ID": "your-client-id",
        "MONEYS3_CLIENT_SECRET": "your-client-secret"
      }
    }
  }
}

Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "moneys3": {
      "command": "node",
      "args": ["/absolute/path/to/moneys3-mcp/dist/index.js"],
      "env": {
        "MONEYS3_DOMAIN": "yourcompany",
        "MONEYS3_APP_ID": "your-app-id",
        "MONEYS3_CLIENT_ID": "your-client-id",
        "MONEYS3_CLIENT_SECRET": "your-client-secret"
      }
    }
  }
}

Claude Code

claude mcp add moneys3 -- node /absolute/path/to/moneys3-mcp/dist/index.js

Set environment variables in your shell or .env before running.

Docker

docker build -t moneys3-mcp .
docker run -i --rm \
  -e MONEYS3_DOMAIN=yourcompany \
  -e MONEYS3_APP_ID=your-app-id \
  -e MONEYS3_CLIENT_ID=your-client-id \
  -e MONEYS3_CLIENT_SECRET=your-client-secret \
  moneys3-mcp

Generic stdio

  • Command: node

  • Args: ["/path/to/moneys3-mcp/dist/index.js"]

  • Required env: MONEYS3_DOMAIN, MONEYS3_APP_ID, MONEYS3_CLIENT_ID, MONEYS3_CLIENT_SECRET

Quick Start

After connecting, the typical workflow is:

  1. Test connection: m3_connection_test

  2. List agendas: m3_agendas → pick the one you need

  3. Set agenda: m3_set_agenda with the GUID

  4. Query data: e.g. m3_issued_invoices, m3_stock_cards, m3_employees

If MONEYS3_AGENDA_GUID is set in env, steps 2–3 are skipped.

Available Tools

Annotations: reads are readOnlyHint, creates destructiveHint: false, updates and deletes destructiveHint: true, m3_graphql destructiveHint + openWorldHint.

Setup and utility (6 tools)

Tool

Description

m3_agendas

List agendas with GUIDs

m3_set_agenda

Set the active agenda for subsequent calls

m3_connection_test

Test OAuth2, endpoint and agenda access; auto-selects a single agenda

m3_import_status

Show how Money S3 processed a queued write (importStatus by import GUID)

m3_graphql

Raw GraphQL query or mutation (mutations detected by parsing, never cached or retried); output over 50,000 characters is trimmed to whole records, never cut mid-JSON

m3_orders

Received or issued orders (type: received | issued)

Invoices (7 tools)

Tool

Description

m3_issued_invoices

Issued invoices with VAT summary, payment status, controlling variables

m3_received_invoices

Received invoices with VAT summary, payment status, controlling variables

m3_create_issued_invoice

Create an issued invoice with partner and line items

m3_create_received_invoice

Create a received invoice with partner and line items

m3_update_issued_invoice

Update an issued invoice's header by document number

m3_update_received_invoice

Update a received invoice's header by document number

m3_delete_invoice

Delete an invoice by ID and year

Address book (4 tools)

Tool

Description

m3_address_book

Contacts with addresses, bank accounts, credit limit, discount, maturity terms

m3_create_address

Create a contact (address, postal code, country code, banking, credit limit, maturity)

m3_update_address

Update a contact found by GUID, partner code or IČO

m3_delete_address

Delete an address book entry

Stock (11 tools)

Tool

Description

m3_stock_cards

Articles: catalogue, description, barcode, PLU, weight

m3_stock_lists

Warehouses and price levels

m3_stock_documents

Received stock slips with partner and controlling variables

m3_inventory_documents

Stocktaking documents with counted amounts

m3_stock_takings

Stocktakings (inventury) with state and dates; their IDs feed inventory documents

m3_create_stock_card

Create an article (catalogue, description, barcode, PLU, weight)

m3_create_stock_document

Create a received stock slip with stock items

m3_create_inventory_document

Create a stocktaking document with counted items

m3_update_stock_card

Update an article by catalogue

m3_update_stock_document

Update a received stock slip's description, title, note and texts

m3_update_inventory_document

Update a stocktaking document (counted items) by stocktaking and document ID

Banking (7 tools)

Tool

Description

m3_bank_documents

Bank documents with statement number, VAT summary, controlling variables

m3_cash_desk_documents

Cash desk documents with cash box, VAT summary, controlling variables

m3_bank_accounts

Bank accounts and cash boxes

m3_create_bank_document

Create a bank document (symbols, partner, bank account, controlling)

m3_create_cash_desk_document

Create a cash desk document (partner, cash box, controlling)

m3_update_bank_document

Update a bank document's header by document number

m3_update_cash_desk_document

Update a cash desk document's header by document number

Documents (9 tools)

Tool

Description

m3_internal_documents

Internal documents with VAT summary and controlling variables

m3_liabilities

Liabilities with maturity, remaining amount, VAT summary

m3_receivables

Receivables with maturity, remaining amount, VAT summary

m3_create_internal_document

Create an internal document

m3_create_liability

Create a liability with partner and maturity

m3_create_receivable

Create a receivable with partner and maturity

m3_update_internal_document

Update an internal document's header by document number

m3_update_liability

Update a liability's header by document number

m3_update_receivable

Update a receivable's header by document number

Accounting (8 tools)

Tool

Description

m3_accounting_journal

Accounting journal with controlling variables

m3_chart_of_accounts

Chart of accounts

m3_predefined_entries

Predefined entries (předkontace) for accounting or tax records (ledger: accounting | tax)

m3_vat_accounting

VAT accounting rules (rozúčtování DPH) for accounting or tax records

m3_create_account

Create an account (enum arguments take the schema's values)

m3_create_predefined_entry

Create a predefined entry

m3_update_account

Update an account by account number

m3_update_predefined_entry

Update a predefined entry by shortcut

Payroll and service (4 tools)

Tool

Description

m3_employees

Employees with employment relationships, current address and contact

m3_service_repairs

Service or repair documents (type: services | repairs)

m3_create_wage

Create a monthly wage with worked time per employment relationship

m3_update_wage

Update a monthly wage by employee, year and month

Controlling (9 tools)

Tool

Description

m3_cost_centers

Cost centers (střediska)

m3_projects

Projects (zakázky)

m3_activities

Activities (činnosti)

m3_create_cost_center

Create a cost center

m3_create_project

Create a project

m3_create_activity

Create an activity

m3_update_cost_center

Update a cost center's name or note by code

m3_update_project

Update a project's name or note by code

m3_update_activity

Update an activity's name or note by code

Lookups and code lists (10 tools)

Tool

Description

m3_numerical_series

Numerical series

m3_currencies

Currencies with country and rate unit

m3_exchange_rates

Exchange rate lists by date and bank

m3_vat_classifications

VAT classifications (členění DPH) with type and VAT return row

m3_vat_purposes

VAT purposes (Slovak agendas only)

m3_constant_symbols

Constant symbols

m3_countries

Countries

m3_years

Accounting years of the agenda

m3_code_lists

Smaller code lists (list): job order types, address keys, shipping methods, combined nomenclature, postal codes, non-monetary payments, XML transfer definitions, employment codes and types, stocktaking types, banks, stock card parameters, tax record movements

m3_crm_activities

CRM activity records

Deletes (8 tools)

Tool

Description

m3_delete_internal_document

Delete an internal document by ID and year

m3_delete_liability

Delete a liability by ID and year

m3_delete_receivable

Delete a receivable by ID and year

m3_delete_bank_document

Delete a bank document by ID and year

m3_delete_cash_desk_document

Delete a cash desk document by ID and year

m3_delete_stock_card

Delete an article by ID

m3_delete_stock_document

Delete a received stock slip by ID and year

m3_delete_inventory_document

Delete a stocktaking document by ID

Not covered: wages cannot be read (the API has createWage/updateWage/deleteWage but no wage query). eshops is not exposed because its records hold FTP passwords. Other query roots without a tool (journalTrs, warehouseStocks, offers, inquiries, issued slips, sale slips, transfer and production notes, delivery notes) are reachable through m3_graphql.

Data Model

  • Reading: GraphQL queries with take/skip paging and HotChocolate-style where/order objects. where and order must each be one GraphQL object (checked before sending).

  • Deleted records: Money S3 returns soft-deleted records and does not accept isDeleted as a filter. List tools hide them on the current page and say how many were hidden; totalCount still counts them.

  • Writing: mutations go into Money S3's import queue. A tool reports "queued for import" with an import GUID when isSuccess is true and an error when it is false. Check the processing result with m3_import_status.

  • Updating: update inputs carry no record ID. Money S3 finds the record by the XML transfer definition's key (spojovací klíč): document number for documents, partner code, IČO, bank account or GUID for addresses, catalogue, barcode, GUID or PLU for stock cards, the shortcut for code lists. Update tools use the agenda's standard import definitions (_FP+FV, _ADR, _KK, … as for creates; definitionShortcut overrides it), so they work in every agenda without setup. Those definitions add a record when the key misses, so the read is the guard:

    • Read before write. The tool reads the record by its key first and sends nothing if no record matches (deleted records do not count where the API shows isDeleted), or, for documents, addresses, stock cards and stocktaking documents, if more than one does. Addresses and stock cards can be matched on several keys, so the read uses every key-capable field the update sends (GUID, code, IČO, bank account; catalogue, GUID, barcode, PLU) and refuses when they point at different records.

    • What the read cannot catch. Code lists and accounts exist once per accounting year: a match in any year passes, so an update aimed at a year without the record may add it there. Wages cannot be read through the API: only the employee is checked, so updating a month that has no wage adds one. A record deleted between the read and the import is added back. A custom definition with new records set to chyba (definitionShortcut) closes these gaps for one agenda.

    Update tools send only the key and the fields you give, and refuse a call that would send nothing but the key or that contains a blank string or empty list. Invoice and other document updates send header fields only (no items, no partner); m3_update_stock_document sends the empty items list its input type requires, and m3_update_inventory_document sends counted items. Whether Money S3 keeps the existing items is unverified. Documents with stock items or links to other documents take only selected header fields such as the description and texts (Seyfor's XML transfer manual), and documents Money S3 would not let you edit are refused. Read the record back after the import.

  • Dates: create tools accept YYYY-MM-DD or DD.MM.YYYY and send ISO YYYY-MM-DD, as in money.cz's official mutation examples.

  • Partner: document creates take a partner object (name, street, city, postalCode, countryCode, countryName, identificationNumber, vatIdentificationNumber, email, phone), sent as partnerAddress.

Filtering examples

Invoices from a date:

where: { dateOfIssue: { gte: "2026-01-01" } }

Sort by date descending:

order: { dateOfIssue: DESC }

Unpaid receivables:

where: { remainingAmountToPayHc: { gt: 0 } }
order: { dateOfMaturity: ASC }

Schema coverage

docs/schema.graphql is the full schema of a live S3Api (Money S3 26.900), fetched from GET /graphql/?sdl, which S3Api serves without a token; MONEYS3_DOMAIN=yourcompany npm run introspect regenerates it. npm run check:contract calls every tool (all fields, required fields only, every value of each enum argument) against a fake transport and validates the GraphQL it sends against that schema with graphql-js: field names, argument and input types, required input fields, enum values and scalar literal kinds. It also flags fields marked @legislationDirective(legislationType: SK), which Czech agendas reject at runtime.

Development

npm ci
npm run build
npm test                # node:test suite, real tool handlers against a fake Money S3 transport
npm run check:contract  # validate every tool's GraphQL against docs/schema.graphql
npm run introspect      # refresh docs/schema.graphql from a live S3Api (needs MONEYS3_DOMAIN)

Layout and design: ARCHITECTURE.md. Contributor rules: AGENTS.md.

Security

  • OAuth2 client credentials; token kept in memory and refreshed 60 s before expiry

  • 30 s timeout on every request

  • Reads retry on timeout; any request retries on 401 (token refresh) and 429 (rate limit)

  • Mutations are never resent after a timeout or transport error: the tool reports "outcome unknown" and names the tool to verify with

  • Response cache (configurable TTL) for reads only; mutations bypass and clear it; document collections are never cached

  • Mutation inputs are encoded as GraphQL literals (strings JSON-escaped, numbers finite, enum arguments limited to the schema's values)

  • where/order on read tools are user-supplied GraphQL: they are inserted only after parsing as a single object or list value, and read tools reject any document that contains a mutation

  • m3_graphql sends any document (max 10,000 characters) and is annotated destructive

  • No credentials logged or exposed in error messages

Important Notes

  • Write operations are asynchronous: data goes to the import queue and is processed by S3 Automatic. Check the outcome with m3_import_status.

  • definitionShortcut names an XML transfer definition configured in your Money S3; defaults are the standard definitions of a Money S3 26.900 agenda (_FP+FV, _ADR, _KK, _S, _INVD, _BD, _PD, _ID, _PH+ZV, _ZAK, _STR, _CIN, _UCOSN+POH, _PREDK, _MZDY).

  • Creates of invoices, liabilities, receivables, internal, bank, cash desk and stock documents take numericalSeriePrefix (see m3_numerical_series). All but stock documents also take accountAssignmentCode (předkontace, see m3_predefined_entries) and vatClassificationCode (členění DPH, see m3_vat_classifications); invoices and liabilities take paymentAccountCode (bank account or cash box, see m3_bank_accounts). When omitted, the XML definition's presets apply. The standard definitions of a fresh agenda may have none: Money S3 then rejects the import (no series; an invoice or liability without a payment account; a předkontace without a VAT classification) or saves the document unposted (no předkontace).

  • Some deletes fail if the record has dependent records (e.g. a received invoice whose goods were already dispatched).

  • The API service must be running on the Money S3 PC. If requests fail with 502/503, check the S3Api Windows service.

  • Questions about the API can be directed to api@money.cz.

License

MIT — see LICENSE for details.

Available Tools

61 tools
m3_accounting_journalA

Query the accounting journal with controlling variables (cost center, project, activity). Read-only.

Inputs: skip, take, order, where.

m3_activitiesC

Query activities (činnosti) — controlling variable. Read/write.

Inputs: skip, take.

m3_address_bookA

Query the address book (contacts/partners) with full detail: addresses, bank accounts, credit limits, discount, maturity terms

Inputs: skip, take, order, where.

m3_agendasA

List all agendas (companies/databases) in this Money S3 instance with their GUIDs. Use the GUID to select which agenda to work with via m3_set_agenda.

Inputs: no named parameters.

m3_bank_accountsA

List bank accounts and cash desks configured in Money S3 (read-only)

Inputs: no named parameters.

m3_bank_documentsA

Query bank documents (payments, transfers) with VAT breakdown, payment status, controlling variables

Inputs: skip, take, order, where.

m3_cash_desk_documentsB

Query cash desk (register) documents with VAT breakdown, payment status, controlling variables

Inputs: skip, take, order, where.

m3_chart_of_accountsA

Query the chart of accounts (accounting plan). Read-only.

Inputs: skip, take, order.

m3_connection_testA

Test the Money S3 API connection — verifies OAuth2 auth, endpoint reachability, and agenda access

Inputs: no named parameters.

m3_constant_symbolsC

List constant symbols (konstantni symboly). Read-only.

Inputs: skip, take, order, where.

m3_cost_centersC

Query cost centers (střediska) — controlling variable. Read/write.

Inputs: skip, take.

m3_countriesB

List country codes. Read-only.

Inputs: skip, take, order, where.

m3_create_accountA

Create a new account in the chart of accounts. Async import queue.

Inputs: account (required), name, note, type, +4 more.

m3_create_activityB

Create an activity (činnost). Async import queue.

Inputs: code (required), name (required), definitionShortcut.

m3_create_addressB

Create a new entry in the address book with business/invoice addresses, banking, credit limits, and maturity terms. Async import queue.

Inputs: name (required), web, zip, city, +19 more.

m3_create_bank_documentC

Create a bank document (payment). Supports controlling variables. Async import queue.

Inputs: dateOfIssue (required), isExpense, partnerIco, description, +10 more.

m3_create_cash_desk_documentC

Create a cash desk (register) document. Supports controlling variables. Async import queue.

Inputs: dateOfIssue (required), isExpense, description, projectCode, +6 more.

m3_create_cost_centerA

Create a cost center (středisko). Async import queue.

Inputs: code (required), name (required), definitionShortcut.

m3_create_internal_documentB

Create an internal document with controlling variables. Async import queue.

Inputs: dateOfAccountingEvent (required), description, projectCode, activityCode, +4 more.

m3_create_inventory_documentB

Create an inventory/stocktaking document. Async import queue.

Inputs: dateOfIssue (required), warehouseCode, documentNumber, definitionShortcut.

m3_create_issued_invoiceA

Create a new issued (outgoing) invoice in Money S3. Written to async import queue.

Inputs: items (required), dateOfIssue (required), dateOfTaxing (required), dateOfMaturity (required), +7 more.

m3_create_liabilityB

Create a liability (závazek/payable) with maturity date and controlling vars. Async import queue.

Inputs: dateOfIssue (required), partnerIco, description, partnerName, +10 more.

m3_create_predefined_entryB

Create a predefined accounting entry (predkontace). Async import queue.

Inputs: shortCut (required), note, type, year, +5 more.

m3_create_projectB

Create a project (zakázka). Async import queue.

Inputs: code (required), name (required), definitionShortcut.

m3_create_receivableB

Create a receivable (pohledávka) with maturity date and controlling vars. Async import queue.

Inputs: dateOfIssue (required), partnerIco, description, partnerName, +10 more.

m3_create_received_invoiceA

Create a new received (incoming) invoice in Money S3. Written to async import queue.

Inputs: items (required), dateOfIssue (required), dateOfTaxing (required), dateOfMaturity (required), +6 more.

m3_create_stock_cardB

Create a new stock/inventory card with optional barcode, weight, warranty, category. Async import queue.

Inputs: name (required), catalogueNumber (required), ean, unit, +10 more.

m3_create_stock_documentA

Create a stock/warehouse document (receipt or dispatch) with controlling vars. Async import queue.

Inputs: items (required), dateOfIssue (required), partnerName, projectCode, +5 more.

m3_create_wageA

Create a wage record (mzdovy doklad) for payroll processing. Async import queue.

Inputs: year (required), month (required), employeeId (required), grossWage, +4 more.

m3_crm_activitiesC

List CRM activity records (log of user actions on documents/contacts). Read-only.

Inputs: skip, take, order, where.

m3_currenciesA

List configured currencies with exchange rates. Read-only.

Inputs: skip, take, order, where.

m3_delete_addressB

Delete an address book entry by ID

Inputs: id (required).

m3_delete_bank_documentA

Delete a bank statement by ID and year.

Inputs: id (required), year (required).

m3_delete_cash_desk_documentB

Delete a cash voucher by ID and year.

Inputs: id (required), year (required).

m3_delete_internal_documentB

Delete an internal document by ID and year.

Inputs: id (required), year (required).

m3_delete_inventory_documentB

Delete a stocktaking document by ID.

Inputs: id (required).

m3_delete_invoiceA

Delete an invoice by ID and year. Fails if the invoice has dependent records (e.g. stock movements).

Inputs: id (required), type (required), year (required).

m3_delete_liabilityC

Delete a liability by ID and year.

Inputs: id (required), year (required).

m3_delete_receivableB

Delete a receivable by ID and year.

Inputs: id (required), year (required).

m3_delete_stock_cardB

Delete a stock card (article) by ID.

Inputs: id (required).

m3_delete_stock_documentB

Delete a stock document (received slip) by ID and year.

Inputs: id (required), year (required).

m3_employeesA

Query employees with full detail: address, contact, employment dates, cost center, employment type. Read-only.

Inputs: skip, take, order, where.

m3_flagsB

List flags/labels used for document tagging. Read-only.

Inputs: skip, take, order, where.

m3_graphqlA

Execute a raw GraphQL query or mutation against the Money S3 API. For advanced use when built-in tools don't cover a specific need.

Inputs: query (required), isMutation.

m3_internal_documentsC

Query internal documents with VAT breakdown, payment status, controlling variables

Inputs: skip, take, order, where.

m3_inventory_documentsB

Query inventory (stocktaking) documents with line items and expected vs real amounts

Inputs: skip, take, order, where.

m3_issued_invoicesA

Query issued (outgoing) invoices with VAT breakdown, payment status, controlling variables, filtering and pagination

Inputs: skip, take, order, where.

m3_liabilitiesB

Query liabilities (payables/obligations) with VAT, payment status, maturity dates, controlling vars

Inputs: skip, take, order, where.

m3_numerical_seriesA

List numerical series (numbering rules) for all document types. Read-only.

Inputs: skip, take, order, where.

m3_ordersC

Query order documents (objednávkové doklady) with pagination

Inputs: skip, take, where.

m3_predefined_entriesA

Query predefined accounting entries (předkontace). Read-only.

Inputs: skip, take, order.

m3_projectsC

Query projects (zakázky) — controlling variable. Read/write.

Inputs: skip, take.

m3_receivablesC

Query receivables (amounts owed to you) with VAT, payment status, maturity dates, controlling vars

Inputs: skip, take, order, where.

m3_received_invoicesA

Query received (incoming) invoices with VAT breakdown, payment status, controlling variables, filtering and pagination

Inputs: skip, take, order, where.

m3_service_repairsC

Query service and repair records. Read-only.

Inputs: skip, take, order, where.

m3_set_agendaA

Set the active agenda (company) for all subsequent API calls. Required before querying any data.

Inputs: guid (required).

m3_stock_cardsB

Query stock/inventory cards with full detail: pricing, stock levels, barcodes, weight, warranty, categories

Inputs: skip, take, order, where.

m3_stock_documentsC

Query stock/warehouse documents with controlling variables, partner details, and line items

Inputs: skip, take, order, where.

m3_stock_listsA

Query warehouses and price levels (read-only)

Inputs: no named parameters.

m3_vat_classificationsB

List VAT classifications (DPH). Read-only.

Inputs: skip, take, order, where.

m3_vat_purposesB

List VAT purposes (ucel DPH). Read-only.

Inputs: skip, take, order, where.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    C2.9/5.0

    Scored across 61 tools

    Disambiguation3/5

    Most tools map clearly to a specific entity and action, but several names overlap conceptually: m3_activities vs m3_crm_activities, m3_stock_documents vs m3_inventory_documents, and m3_delete_invoice next to the issued/received invoice tools. Descriptions usually resolve the ambiguity, but the boundaries are not always obvious at a glance.

    Naming Consistency4/5

    The m3_ prefix and the m3_create_* / m3_delete_* conventions are applied consistently, while read tools mostly use plural resource nouns like m3_orders and m3_receivables. Minor exceptions such as m3_graphql, m3_connection_test, and m3_set_agenda break the pattern slightly but do not make the set unpredictable.

    Tool Count2/5

    61 tools is far beyond the typical well-scoped MCP surface and creates a heavy navigation burden for an agent. The high count is purposeful given the breadth of an ERP system, but it still feels oversized for a single MCP server.

    Completeness3/5

    The server covers many Money S3 modules with query/create/delete operations for most resources, but there are no built-in update tools anywhere and some areas are one-sided, such as wages being create-only and orders/employees/service records being read-only. The raw m3_graphql tool provides an escape hatch, but the exposed surface is not a complete lifecycle.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      B
      quality
      D
      maintenance
      MCP server for DACH accounting automation. Connect AI assistants to sevDesk and Lexoffice — create invoices, manage contacts, handle bookings and vouchers for German-speaking businesses.
      15
      59 npm
      -
    • A
      license
      B
      quality
      D
      maintenance
      A read-only MCP server for SimpleShop accounting data, enabling AI agents to find documents, download PDFs, inspect products, and review sales exports.
      5
      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