# e-Boekhouden MCP Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## e-Boekhouden MCP

Read and create invoices, manage customers and suppliers, and track bookkeeping in e-Boekhouden.

- Record: https://musedirectory.ai/connector/e-boekhouden-mcp
- Category: Finance & Bills
- Developer: usefulapi (https://usefulapi.io/e-boekhouden/)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 51ms, checked 2026-10-29T11:00:49Z
- Endpoint: https://e-boekhouden.usefulapi.io/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-29T12:56:30Z)
- Source: Found in the official MCP Registry (io.usefulapi/e-boekhouden) https://registry.modelcontextprotocol.io/v0/servers?search=io.usefulapi%2Fe-boekhouden

Connects to e-Boekhouden accounting software. Read relations, invoices, ledgers, bookings and products. Create new relations, products and sales invoices. Query outstanding invoices, ledger balances and cost centers. Requires e-Boekhouden account.

Example request: "Create an invoice for a customer and show me all unpaid invoices from this month."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use e-Boekhouden MCP to help me. It is a free service with an MCP server at https://e-boekhouden.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- eboekhouden_list_relations: List 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_relation: One relation with all its fields (addresses, e-mail addresses, VAT and KvK number, IBAN, payment term, ledger). GET /v1/relation/{id}.
- eboekhouden_list_invoices: Search 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_invoice: One invoice with its items, amounts and relation. GET /v1/invoice/{id}.
- eboekhouden_list_outstanding_invoices: Open (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_mutations: Search 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
- eboekhouden_get_mutation: One mutation with its rows (ledger, VAT code, amount, relation, invoice number). GET /v1/mutation/{id}.
- eboekhouden_list_ledgers: The 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_ledger: One ledger account. GET /v1/ledger/{id}.
- eboekhouden_get_ledger_balance: The balance of one ledger, optionally per cost center and for a period (from/to). GET /v1/ledger/{id}/balance.
- eboekhouden_list_ledger_balances: The balances of all ledgers (a trial balance), optionally per cost center and for a period (from/to). GET /v1/ledger/balances.
- eboekhouden_list_products: List 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_product: One product with price, VAT code, ledger, unit and stock setting. GET /v1/product/{id}.
- eboekhouden_list_product_groups: All product groups. GET /v1/product/groups.
- eboekhouden_list_cost_centers: List cost centers (kostenplaatsen), optionally by parent id or description. Paged: pass next_offset as offset. GET /v1/costcenter.
- eboekhouden_get_cost_center: One cost center. GET /v1/costcenter/{id}.
- eboekhouden_list_units: List product units (piece, hour, ...) with their ids. Paged: pass next_offset as offset. GET /v1/unit.
- eboekhouden_list_invoice_templates: List 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_templates: List e-mail templates. Paged: pass next_offset as offset. GET /v1/emailtemplate.
- eboekhouden_list_members: List members; only available to clubs and associations (others get error MEM_056). Paged: pass next_offset as offset. GET /v1/member.
- eboekhouden_get_member: One member; only available to clubs and associations. GET /v1/member/{id}.
- eboekhouden_create_relation: Create 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_relation: Change 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 + 
- eboekhouden_create_product: Create 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_invoice: Create 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, templa

Screening checks:
- MCP handshake: pass (Answered in 20ms)
- Domain against threat feeds (Cloudflare security DNS): pass (e-boekhouden.usefulapi.io, usefulapi.io not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (25 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)