e-Boekhouden API and MCP server

e-Boekhouden's API covers relations, invoices and bookings, but it takes an API token and session code you write and host. Sign in to e-Boekhouden once in your own Cloud Browser, and your AI agent does the work there for you. The same tools work over MCP for agents and as a REST API for scripts.

Not affiliated with e-Boekhouden.

e-Boekhouden has no API for this. So we run one for you.

e-Boekhouden's own API, a GitHub MCP server and Cotlet compared
What you need e-Boekhouden's APIGitHub MCP serverCotlet
Use without an API key or code No No Yes, 14 tools
Acts as you, signed in 24/7 No No Yes, Cloud Browser
Fixed for you when e-Boekhouden changes N/A No Yes, tested every 6h
Runs with your laptop off N/A No Yes, hosted

Checked Oct 14, 2026. Sources: e-Boekhouden API reference (OpenAPI) · e-Boekhouden: API-koppeling · e-Boekhouden: Prijzen (API listed among the features)

Your own Cloud Browser, on 24/7. Sign in once. We keep it connected.

  1. 01Sign in to e-Boekhouden in your own Cloud Browser

  2. 02Connect it for your agents

  3. 03Cotlet keeps it signed in and working

How do I connect e-Boekhouden to Claude, ChatGPT or my code?

AI agents connect over MCP, scripts call the REST API. Both reach the same 14 tools with one API key.

For AI agents: MCP

Add Cotlet to your agent once. e-Boekhouden and every other app you connect show up as its tools.

  • Claude
  • ChatGPT
  • OpenClaw
  • Hermes
  • GrokBot
  • Cursor
  • n8n
  • Any MCP client
  1. 1

    Add Cotlet to your agent

    Claude Code
    claude mcp add --transport http cotlet \
      https://cotlet.dev/mcp/v1 \
      --header "Authorization: Bearer $COTLET_API_KEY"
    Cursor
    {
      "mcpServers": {
        "cotlet": {
          "url": "https://cotlet.dev/mcp/v1",
          "headers": {
            "Authorization": "Bearer ${COTLET_API_KEY}"
          }
        }
      }
    }
    Codex
    # ~/.codex/config.toml
    [mcp_servers.cotlet]
    url = "https://cotlet.dev/mcp/v1"
    bearer_token_env_var = "COTLET_API_KEY"

    Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

For scripts: REST API

Every tool is an endpoint under /api/v1/e-boekhouden with its own method and path, such as POST /api/v1/e-boekhouden/relations/{relation_id}/invoices, with the same API key. Our open-source repo has ready scripts to start from.

REST API docs

What can the e-Boekhouden API and MCP server do?

14 tools on your own e-Boekhouden account. Agents call them as operations of the MCP tools e_boekhouden_read and e_boekhouden_write; scripts call each one at its own REST endpoint, with the same inputs and answers.

e-Boekhouden tools in Cotlet's MCP server and REST API
Tool What it does Access
list_relations Customers and suppliers (relations) with code, name, city and email, filtered by name, email, code, city or type. read
get_relation One relation with address, contacts, email addresses, VAT number, IBAN and payment term. read
list_ledgers Ledger accounts (grootboekrekeningen) with ID, code, name and category. read
get_ledger_balances The balance of every ledger, optionally from and up to a date and for one cost center. read
list_products Products and services with ID, code, description, price and VAT code. read
list_invoice_templates Invoice templates (layout and standard texts) with their IDs. read
list_invoices Invoices you created, searched by invoice number, relation or date. read
get_invoice One invoice with its lines, VAT per line and totals. read
list_mutations Bookings (mutations) filtered by type, date, invoice number or description. read
list_outstanding_invoices Open invoices of debtors (customers who owe you) or creditors (suppliers you owe), with the open amount. read
create_relation Add a customer or supplier with name, address, email, VAT number and IBAN. write
update_relation Change fields of a relation, or set it inactive. write
create_invoice Create an invoice for a relation from one or more lines, and optionally email it to the relation. writeasks first
create_mutation Book a mutation: a payment, money received or sent, or a general journal entry. writeasks first

Scroll the table for all 14 tools.

Ask in plain words. Your agent does the rest.

Is it safe to connect e-Boekhouden?

You sign in yourself in your own Cloud Browser, we never save your password, and anything that reaches your readers waits for your OK. The browser profile is encrypted in the EU. Independent scanners grade cotlet.dev A+.

How much do the e-Boekhouden API and MCP server cost?

One price for both: a tool call costs the same over MCP or REST. Free 7-day trial with 2,000 credits, no card needed. Then one-time credit packs, no subscription, valid 12 months. Most calls use 25 credits, and your Cloud Browser uses 50 credits a day while e-Boekhouden is enabled for agents, so 20 calls a day come to 550 credits.

Cotlet credit packs: price, credits and calls at 25 credits each
Credits Price, one time Calls at 25 credits Per 1,000 credits
5,000 $29 200 $5.80
15,000 $79 600 $5.27
32,000 $149 1,280 $4.66
60,000 $249 2,400 $4.15

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.

Questions

Does e-Boekhouden have an API?

Yes. e-Boekhouden has a REST API with an OpenAPI description (checked 14 Oct 2026). It covers relations, invoices, bookings (mutations), ledgers, products and outstanding invoices. It has no official MCP server, you create an API token in your account settings that is shown once, and you write the code that exchanges it for a short-lived session token.

How do I get access?

Sign up free, open e-Boekhouden under Integrations in the console and press Request access. Your free trial starts with your account, no card needed.

Is the MCP server different from the API?

No, only the way in. Cotlet builds each integration as a REST API and puts an MCP server on top, so both have the same 14 tools, the same inputs and answers, one API key and one price. AI agents such as Claude, ChatGPT or Cursor use MCP; scripts, cron jobs and HTTP steps in n8n, Make or Zapier use the REST API.

What is the Cloud Browser?

Your own Chrome that Cotlet runs for you in the EU, around the clock. You open it from the console, sign in to e-Boekhouden yourself and press Enable for agents. Your agent's calls go through it, from its IP with its cookies, so e-Boekhouden sees the browser you signed in with. Password saving is off and the profile is stored encrypted with AES-256-GCM.

Can my agent act without asking me?

Not on anything that reaches other people: create_invoice, create_mutation wait for your OK by default. You can switch that off per tool for scheduled runs.

Can my agent send an invoice to a client without asking me?

Only if you switch confirmation off for create_invoice. By default every create_invoice and create_mutation call waits for your OK, because an invoice is a legal document and a booking changes your books.

Should I use a e-Boekhouden MCP server from GitHub instead?

Pick one if you want the code on your own computer and do not mind the upkeep: you install it, sign it in and fix it when e-Boekhouden changes. Pick Cotlet if you want it hosted and kept working for you.

Can I use it in n8n, Make or Zapier?

Yes. Add https://cotlet.dev/mcp/v1 in n8n's MCP Client node, or call the REST endpoints from an HTTP step in Make or Zapier.

Who runs Cotlet?

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

Is Cotlet affiliated with e-Boekhouden?

No. Cotlet is independent and not affiliated with e-Boekhouden.

Give your agent access to e-Boekhouden.

Free 7-day trial with 2,000 credits, no card needed.