MCP server for e-Boekhouden.nl · Accounting & invoicing

Stop clicking through e-Boekhouden.nl.
Tell your AI what to do.

Run your e-Boekhouden administration with your AI assistant, without clicking through screens.

Not built yet. Your sign-up decides if and when we build this.
What it will do

Run your e-Boekhouden.nl in plain language.

Run your e-Boekhouden.nl administration without clicking through screens: look up and change invoices, contacts, entries and overviews in plain language. The MCP server runs locally and talks through the e-Boekhouden API.

Examples

What you'll be able to ask your AI.

Send the monthly invoice to all my recurring clients.

The AI drafts the invoices and asks for confirmation per batch.

Which contacts still don't have an email address?

You get a list so you can clean up your records.

What's outstanding in accounts receivable?

The AI totals the outstanding items and shows the sum per client.

Add a new contact from this email signature.

The AI reads the details and creates the contact, you check it.

Planned functions

What we want to build in.

These operations are on the roadmap. Missing one? Add it in the notes field below — it weighs into what we build first.

  • Invoices: drafting, sending, status
  • Contacts: searching, creating, updating
  • Looking up entries and the ledger
  • Outstanding items (receivables/payables)
  • Generic escape hatch for any e-Boekhouden API endpoint

Why EASEO.

We only build MCP servers we would run in production ourselves. Our WeFact MCP server already exists: runs locally, your API key stays on your machine, tested on a real administration. We hold e-Boekhouden.nl to the same standard. No cloud middleman, no telemetry.

Put me on the list.

No obligation. We'll only email you once the e-Boekhouden.nl MCP server exists (or if we're building it and want your input).

We only use your details for this. You can unsubscribe at any time.