e-Boekhouden MCP by usefulapi

io.usefulapi/e-boekhouden · v1.0.0 · finance-and-payments

e-Boekhouden MCP by usefulapi is healthy: it completed an MCP handshake in 714 ms and exposes 25 tools.

Read e-Boekhouden relations, invoices, ledgers, bookings and products; create relations, invoices.

Endpoint: https://e-boekhouden.usefulapi.io/mcp (streamable-http)

Repository · Website · JSON · Add to my inventory

Facts

Users (last 30 days)0
HandshakeHealthy
Auth neededNone
Tool count25
Latency714 ms
Last checked (UTC)2026-10-15T12:05:08.311Z

Health history

Checked (UTC)StatusLatencyError
2026-10-15T12:05:08.311ZHealthy714

Tools (25)

eboekhouden_list_relationsList relations (customers and suppliers of the administration), optionally filtered (filters combine with AND). Text filters match exactly unless match is contains or starts_with. Paged: pass next_offset as offset. GET /v1/relation.
eboekhouden_get_relationOne relation with all its fields (addresses, e-mail addresses, VAT and KvK number, IBAN, payment term, ledger). GET /v1/relation/{id}.
eboekhouden_list_invoicesSearch the invoices created in the invoicing module, by invoice number, relation or date (exact, or from/to). Paged: pass next_offset as offset. GET /v1/invoice.
eboekhouden_get_invoiceOne invoice with its items, amounts and relation. GET /v1/invoice/{id}.
eboekhouden_list_outstanding_invoicesOpen (unpaid) invoices: debtors (D, sales invoices customers still owe) or creditors (C, purchase invoices still to be paid). Paged: pass next_offset as offset. GET /v1/mutation/invoice/outstanding.
eboekhouden_list_mutationsSearch the bookkeeping mutations: type 1 invoice received, 2 invoice sent, 3 invoice payment received, 4 invoice payment sent, 5 money received, 6 money sent, 7 general journal entry. Filter by type, mutation number, description, invoice number or date. Paged: pass next_offset as offset. GET /v1/mut
eboekhouden_get_mutationOne mutation with its rows (ledger, VAT code, amount, relation, invoice number). GET /v1/mutation/{id}.
eboekhouden_list_ledgersThe ledger accounts (grootboekrekeningen): id, code, description and category (BAL balance, VW profit and loss, FIN, DEB, CRED, AF6, AF19, AFOVERIG, VOOR, BTWRC, AF). Use the id as ledger_id in other tools. Paged: pass next_offset as offset. GET /v1/ledger.
eboekhouden_get_ledgerOne ledger account. GET /v1/ledger/{id}.
eboekhouden_get_ledger_balanceThe balance of one ledger, optionally per cost center and for a period (from/to). GET /v1/ledger/{id}/balance.
eboekhouden_list_ledger_balancesThe balances of all ledgers (a trial balance), optionally per cost center and for a period (from/to). GET /v1/ledger/balances.
eboekhouden_list_productsList products and services (articles) with price, VAT code, ledger and unit, optionally by code or group code. Paged: pass next_offset as offset. GET /v1/product.
eboekhouden_get_productOne product with price, VAT code, ledger, unit and stock setting. GET /v1/product/{id}.
eboekhouden_list_product_groupsAll product groups. GET /v1/product/groups.
eboekhouden_list_cost_centersList cost centers (kostenplaatsen), optionally by parent id or description. Paged: pass next_offset as offset. GET /v1/costcenter.
eboekhouden_get_cost_centerOne cost center. GET /v1/costcenter/{id}.
eboekhouden_list_unitsList product units (piece, hour, ...) with their ids. Paged: pass next_offset as offset. GET /v1/unit.
eboekhouden_list_invoice_templatesList invoice templates (the template_id for eboekhouden_create_invoice), optionally by name, type (E editor, A advanced) or active. Paged: pass next_offset as offset. GET /v1/invoicetemplate.
eboekhouden_list_email_templatesList e-mail templates. Paged: pass next_offset as offset. GET /v1/emailtemplate.
eboekhouden_list_membersList members; only available to clubs and associations (others get error MEM_056). Paged: pass next_offset as offset. GET /v1/member.
eboekhouden_get_memberOne member; only available to clubs and associations. GET /v1/member/{id}.
eboekhouden_create_relationCreate a new relation (customer or supplier) in the administration. Only name is required; the code is generated when omitted. Returns the new id and code. POST /v1/relation.
eboekhouden_update_relationChange fields of an existing relation. The tool first reads the relation, then sends its current values with your changes on top (the API requires name on every update), so fields you do not pass keep their values. This overwrites the current values of the fields you pass. GET + PATCH /v1/relation/{
eboekhouden_create_productCreate a product or service. Needs code, description, a sale VAT code and a ledger id, and exactly one of price_excl or price_incl. Returns the new id. POST /v1/product.
eboekhouden_create_invoiceCreate a sales invoice for a relation. PERMANENT: the API cannot change or delete invoices afterwards, and an invoice number is used up. The invoice is created only: it is NOT e-mailed to the customer, NOT booked as a mutation and no direct debit is set. Needs relation_id, template_id (eboekhouden_l