Skip to main content
Glama

informer-mcp

M8ven Live Monitored

A Model Context Protocol server for the Informer bookkeeping API (v2). It gives any MCP client direct access to your relations, sales and purchase invoices, quotations, orders, receipts, products and financial reports.

Every tool is derived from Informer's own OpenAPI document (api.informer.eu/docs/v2). A copy ships with the server so it works offline, and it keeps itself current — see Keeping up with API changes.

Unofficial project. Not affiliated with or endorsed by Informer.


Quickstart

Paste this into any AI assistant that can install MCP servers:

Install the following MCP server: https://github.com/vladxyz/informer-mcp and run the local setup screen for the API keys.

It clones the repository, builds it, registers the server, and opens the page where your API credentials go. Nothing is asked for in the chat, and no key is ever pasted into a conversation.

To do it yourself, first build the server:

git clone https://github.com/vladxyz/informer-mcp.git
cd informer-mcp
npm install          # also builds dist/

Then wire it into whichever client you use. All of them run the same thing: node, with the path to dist/index.js.

Claude Code

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

Add --read-only at the end for a server that cannot change anything.

Claude Desktop

Build a bundle and open it:

npm run bundle       # writes informer-mcp.mcpb

Settings → Extensions → Advanced settings → Install Extension… and pick the file. It carries its own dependencies, and the install dialog asks for an API key, a security code and a read-only switch — all three may be left empty, in which case the setup page opens on first run.

Settings → Connectors → Add custom connector is a different thing: it takes the URL of a remote MCP server. This one runs locally, so it installs as an extension.

Editing claude_desktop_config.json by hand works too — see Any MCP client for the shape, and put the file at ~/Library/Application Support/Claude/ on macOS or %APPDATA%\Claude\ on Windows.

Codex and the ChatGPT desktop app

Codex CLI, the ChatGPT desktop app and the Codex IDE extension share one MCP configuration:

codex mcp add informer -- node /absolute/path/to/informer-mcp/dist/index.js

or in ~/.codex/config.toml:

[mcp_servers.informer]
command = "node"
args = ["/absolute/path/to/informer-mcp/dist/index.js"]

The .mcpb bundle is a Claude Desktop format; everywhere else use the command above.

Any MCP client

The server speaks MCP over stdio, which every client configures the same way — a command and its arguments:

{
  "mcpServers": {
    "informer": {
      "command": "node",
      "args": ["/absolute/path/to/informer-mcp/dist/index.js"]
    }
  }
}

On Windows, either double the backslashes or use forward slashes.

Credentials do not belong in this file: they live in ~/.informer-mcp.json, written by the setup page. To pass them per client anyway, add an env block with INFORMER_API_KEY and INFORMER_SECURITY_CODE.

First run

However you installed it, starting without credentials opens the setup page by itself. Then ask "which administrations do you have access to?" to confirm — that calls list_administrations and lists each alias with its company.


Related MCP server: billingo-mcp

What you get

  • 68 tools covering all 49 documented endpoints — read and write.

  • Setup in the browser. Ask your assistant to open the setup page, or run informer-mcp setup. It checks every key against the API, writes the config file, and the change takes effect without restarting anything.

  • Follows the API. When Informer publishes a new endpoint the server picks it up and adds the tool while your client stays connected — no reinstall, no restart.

  • Several client administrations in one server. Bookkeepers can reach every client's books from one connection, with an administration argument that is required whenever more than one is configured.

  • One question across the whole portfolio. Read-only tools accept a list of aliases or "all" and query them concurrently, returning results keyed by client.

  • Full request schemas. Create/update tools advertise the complete JSON Schema for their payload, so the model knows which fields exist and which are required before it sends anything.

  • Read-only or read-write, your choice. A --read-only flag hides every tool that changes anything, and individual clients can be pinned to read-only while the rest stay writable. Allow/deny lists narrow the surface further.

  • PDFs and attachments are decoded from base64 and can be written straight to disk.

  • Resilient HTTP. Timeouts, retries with Retry-After support, and Informer's Dutch validation errors surfaced verbatim (HTTP 422: invoice_date: ongeldig).

Requirements

  • Node.js 20 or newer

  • An InformerOnline account with API access

Setting up your credentials

Just ask, in the conversation:

"I want to change my Informer administrations" "Add a new client to Informer" "My Informer API key changed"

Your assistant calls the open_setup tool and the page opens. There is no config file to find and nothing to edit by hand — and because the page is a browser form, your API key never has to be typed into a chat. The same page from a terminal:

npm run setup          # or: informer-mcp setup

Starting the server with no credentials at all opens it automatically, since that is exactly the moment you need it. Set INFORMER_AUTO_SETUP=false to turn that off, or INFORMER_OPEN_BROWSER=false on a headless machine to only print the URL. However it was opened, there is only ever one page: asking again hands back the same URL.

What you see on the page

One card per administration, plus Add administration if you look after more than one:

┌─ Administration ────────────────────────────── Remove ─┐
│  ALIAS                        COMPANY NAME             │
│  [ acme                ]      [ ACME BV           ]    │
│  Short handle you use         Optional, shown in       │
│  in prompts.                  tool descriptions.       │
│                                                        │
│  API KEY                      SECURITY CODE            │
│  [ •••••••••••••••••  ]      [ •••••••••••••••  ]     │
│                                                        │
│  ACCESS                                                │
│  [ Read and write   ▾ ]                                │
│  Read only hides every tool that changes this          │
│  client's books.                                       │
└────────────────────────────────────────────────────────┘

  [ Add administration ]   [ Verify & save ]   ☐ Save without verifying

Field

What to put in it

Alias

The short name you will say in prompts — "list open invoices for acme". Letters, digits, - and _.

Company name

Optional label, shown to the model so it knows acme is ACME BV.

API key

Created inside that administration at app.informer.eu/settings/api.

Security code

Shown in that administration's settings at app.informer.eu/settings/account.

Access

Read and write, or Read only to hide every tool that could change this client's books.

Both credentials belong to one administration, so a bookkeeper adds one card per client. See Multiple client administrations.

What happens when you press Verify & save

  1. Each key/security-code pair is tried against the API, and the page shows you the company name it actually belongs to — so a key pasted into the wrong row is obvious before anything is stored.

  2. If a pair is rejected, nothing is written and the failing row is named. Tick Save without verifying to store it anyway, for instance when you are offline.

  3. On success the credentials are written to ~/.informer-mcp.json with 0600 permissions. Opened through open_setup, the running server picks the change up immediately — a new administration is selectable in the very next message. Opened from a terminal, restart your client.

A few things the page deliberately does:

  • it binds to 127.0.0.1 only, and every run generates a random token that must be in the URL and in the save request, so another site in your browser cannot post to it;

  • it never sends stored keys back to the page — existing administrations show up with their credentials blank and are kept unless you type a new value;

  • it refuses to save credentials the API rejects, unless you tick Save without verifying.

Nothing stops you from writing the file or the environment variables by hand; the page is a convenience, not a requirement.

Where the keys come from

The API authenticates with two headers, both required:

Environment variable

Where to find it

INFORMER_API_KEY

app.informer.eu/settings/api

INFORMER_SECURITY_CODE

app.informer.eu/settings/account

Both are scoped to one administration: the API key belongs to the administration it was created in (GET /administration returns "the administration linked to this API key") and the security code identifies that company. There is no endpoint that lists administrations or switches between them.

A key grants full access to that administration's books. Treat it like a password: keep it in your environment, a secret manager, or a config file outside the repository.

Multiple client administrations

A bookkeeper with several clients needs one key/security-code pair per client administration — an accountant user with access to an administration can create them from its settings. Add them in the setup page, or write ~/.informer-mcp.json (or any file named by INFORMER_CONFIG_FILE) yourself:

{
  "administrations": {
    "acme":     { "label": "ACME BV",         "api_key": "...", "security_code": "..." },
    "bakkerij": { "label": "Bakkerij de Bol", "api_key": "...", "security_code": "...", "mode": "read-only" }
  }
}

With more than one administration configured, every tool requires an administration argument, advertised as an enum of your aliases:

list_sales_invoices({ "administration": "acme", "filter": "open" })

There is deliberately no default. Booking an invoice into the wrong client's ledger is the one mistake that must not happen quietly, so a call without the argument is rejected by schema validation before any HTTP request is made — as is an alias you never configured.

list_administrations shows the configured aliases; pass verify: true to fetch each company name from the API, which confirms both that the credentials work and that every alias points at the company you think it does.

Querying several clients at once

Read-only tools also accept a list of aliases, or "all":

list_sales_invoices({ "administration": "all", "filter": "open", "records": 50 })
list_sales_invoices({ "administration": ["acme", "bakkerij"], "filter": "open" })

The administrations are queried concurrently (INFORMER_FANOUT_CONCURRENCY, four at a time by default) and the answer is keyed by alias:

{
  "administrations": ["acme", "bakkerij"],
  "results": {
    "acme": { "pagination": { "total": 3 }, "invoices": [ ... ] },
    "bakkerij": { "error": "[bakkerij] HTTP 401: Authentication failed" }
  }
}

Three properties worth knowing:

  • One client failing does not sink the query. Its entry carries an error and the rest still return data.

  • The response budget is split evenly. Each administration gets INFORMER_MAX_RESPONSE_CHARS / n characters, so one large client cannot crowd the others out; anything over its share comes back as { "truncated": true, "partial": ... }.

  • Fan-out is read-only. Tools that write, and the PDF/attachment downloads, take a single alias — their schema does not even offer the array or "all", and the handler refuses them a second time. Creating the same invoice in twelve administrations is never an accident worth enabling.

A single administration still returns the API payload unwrapped, exactly as before.

With a single administration — the common case — nothing changes: set INFORMER_API_KEY and INFORMER_SECURITY_CODE as usual and the argument stays optional.

Read-only or read-write

By default every tool is available. To take the writing tools away entirely, start the server with a flag:

informer-mcp --read-only     # only the tools that read
informer-mcp --read-write    # the default: create, update and delete too

INFORMER_READ_ONLY=true does the same thing, and the flag wins over the variable — so you can register the same server twice in one client, once read-only for everyday questions and once read-write for the sessions where you actually book something.

In read-only mode the write tools are not registered at all: they never appear in the tool list, so there is nothing for a model to reach for.

Per client

Individual administrations can be pinned in the config file, which is the useful shape when you may only look at some clients' books:

{
  "administrations": {
    "acme":     { "api_key": "...", "security_code": "..." },
    "bakkerij": { "api_key": "...", "security_code": "...", "mode": "read-only" }
  }
}

"read_only": true works as a shorthand. The most restrictive setting wins:

Server

Client

Result

--read-write (default)

unset

read-write

--read-write

"read-only"

read-only

--read-only

unset

read-only

--read-only

"read-write"

read-only — the flag clamps everything

So a client marked read-only can never be written to by accident, and a session started --read-only stays that way no matter what the config file says.

When some administrations are writable and others are not, the write tools stay registered but their administration enum only offers the writable ones. Asking to create an invoice in a read-only client is refused before any HTTP request:

Administration(s) bakkerij are configured as read-only, so this tool cannot change them.
Writable: acme, garage.

list_administrations reports the effective mode of each client, and the startup banner summarises it: read-write: acme, garage.

Configuration

Variable

Default

Purpose

INFORMER_API_KEY

—

API key for a single administration.

INFORMER_SECURITY_CODE

—

Security code for that administration.

INFORMER_CONFIG_FILE

~/.informer-mcp.json

JSON file listing several administrations. Created by setup if absent.

INFORMER_ADMINISTRATIONS

—

The same JSON inline, as an environment variable. Overrides the file per alias.

INFORMER_ADMINISTRATION_ALIAS

default

Alias for the single INFORMER_API_KEY pair.

INFORMER_ADMINISTRATION_LABEL

—

Human-readable name for that alias.

INFORMER_ADMINISTRATION_MODE

—

read-only or read-write for that alias.

INFORMER_BASE_URL

https://api.informer.eu/v2

Override the API root.

INFORMER_READ_ONLY

false

true exposes only GET tools, for every administration. Same as --read-only.

INFORMER_TOOLS

(all)

Allowlist of tags and/or tool names, comma separated.

INFORMER_EXCLUDE_TOOLS

(none)

Denylist, applied after the allowlist.

INFORMER_TIMEOUT_MS

30000

Per-request timeout.

INFORMER_MAX_RETRIES

2

Retries for 408/429/5xx and network errors.

INFORMER_MAX_RESPONSE_CHARS

100000

Longer tool results are truncated with a notice. Split evenly across a fan-out query.

INFORMER_FANOUT_CONCURRENCY

4

How many administrations a fan-out query hits at the same time.

INFORMER_AUTO_SETUP

true

false stops the setup page from opening when no credentials are configured.

INFORMER_OPEN_BROWSER

true

false prints the setup URL instead of launching a browser.

INFORMER_SPEC_MAX_AGE_HOURS

24

How old the cached API description may get before a background refresh. 0 disables it.

INFORMER_SPEC_CACHE

~/.informer-mcp.spec.json

Where the downloaded API description is cached.

INFORMER_SPEC_URL

Informer's published document

Override the API description to download.

Filters accept either an OpenAPI tag or a tool name, and are matched case- and punctuation-insensitively:

# read-only access to invoicing data
INFORMER_TOOLS="Sales Invoices,Relations" node dist/index.js --read-only

# everything except deleting attachments
INFORMER_EXCLUDE_TOOLS=delete_sales_invoice_attachment node dist/index.js

Using it

Once connected, ask in plain language:

  • "Which sales invoices from 2026 are still unpaid?" → list_sales_invoices with filter

  • "Create a draft invoice for ACME for 10 hours of consultancy at €125." → get_sales_invoice_options for valid ledger/VAT/template ids, then create_sales_invoice

  • "Download invoice 12345 as a PDF to my desktop." → get_sales_invoice_pdf with save_path

  • "Show the balance sheet for period 6 of 2026." → get_balance_report

Conventions worth knowing

  • Pick the administration explicitly. With several clients configured, every tool takes administration: "<alias>". list_administrations maps aliases to companies, and read-only tools also accept a list or "all".

  • Dates are always YYYY-MM-DD.

  • List tools are paginated through page (default 1) and records (default 20), and return a pagination object with total and pages.

  • Request payloads go in a single body argument. Path and query parameters stay at the top level, so update_relation takes { "id": 42, "body": { ... } }.

  • Call the *_options tool first when creating documents. get_sales_invoice_options, get_quotation_options and friends return the valid ledger, VAT, template, currency and payment-condition ids for your administration.

  • Reports need explicit ranges. get_balance_report requires year_from, year_to and period; get_column_balance_report also wants a ledger range.

PDFs and attachments

Informer returns files as base64 inside JSON. Tools that do this (get_*_pdf, download_sales_invoice_attachment) take an optional save_path:

  • with save_path — the file is decoded and written to that path, and the tool returns { saved_to, filename, bytes, mime_type };

  • without it — the file comes back as an inline MCP resource with the right MIME type, which large documents can make expensive in context.

Uploading works the other way around: upload_sales_invoice_attachment takes { filename, file } where file is base64-encoded content (max 10 MB; PDF, PNG, JPEG, GIF, DOC(X), XLS(X)).

Tool reference

npm run tools prints this list from the current spec; npm run tools -- --md regenerates the tables below.

Besides the endpoint tools there are three server-provided ones:

Tool

What it does

list_administrations

Which client administrations are configured, their companies, and which may be written to.

open_setup

Opens the local page for adding, changing or removing administrations and their credentials.

refresh_api_spec

Re-reads Informer's API description and updates the tools.

Administration

Tool

Endpoint

Description

get_administration

GET /administration

Get administration details

Relations

Tool

Endpoint

Description

get_relation

GET /relations/{id}

Get a single relation

update_relation

PUT /relations/{id}

Update a relation

list_relations

GET /relations

Get a list of relations

create_relation

POST /relations

Create a new relation

Contacts

Tool

Endpoint

Description

get_contact

GET /contact/{id}

Get a single contact

update_contact

PUT /contact/{id}

Update a contact

create_contact

POST /contact

Create a new contact

Sales Invoices

Tool

Endpoint

Description

get_sales_invoice

GET /invoices/sales/{id}

Get a single sales invoice

update_sales_invoice

PUT /invoices/sales/{id}

Update a sales invoice

list_sales_invoices

GET /invoices/sales

Get a list of sales invoices

create_sales_invoice

POST /invoices/sales

Create a new sales invoice

get_sales_invoice_options

GET /invoices/sales/options

Get sales invoice options

get_sales_invoice_pdf

GET /invoices/sales/pdf/{id}

Get sales invoice PDF

send_sales_invoice

POST /invoices/sales/send/{id}

Send a sales invoice

upload_sales_invoice_attachment

POST /invoices/sales/{id}/attachments

Upload an invoice-specific attachment

download_sales_invoice_attachment

GET /invoices/sales/{id}/attachments/{attachment_id}

Download an invoice attachment

delete_sales_invoice_attachment

DELETE /invoices/sales/{id}/attachments/{attachment_id}

Delete an invoice-specific attachment

Purchase Invoices

Tool

Endpoint

Description

get_purchase_invoice

GET /invoices/purchase/{id}

Get a single purchase invoice

list_purchase_invoices

GET /invoices/purchase

Get a list of purchase invoices

create_purchase_invoice

POST /invoices/purchase

Create a new purchase invoice

get_purchase_invoice_options

GET /invoices/purchase/options

Get purchase invoice options

get_purchase_invoice_pdf

GET /invoices/purchase/pdf/{id}

Get purchase invoice PDF

Recurring Invoices

Tool

Endpoint

Description

get_recurring_invoice

GET /invoices/recurring/{id}

Get a single recurring invoice

update_recurring_invoice

PUT /invoices/recurring/{id}

Update a recurring invoice

list_recurring_invoices

GET /invoices/recurring

Get a list of recurring invoices

create_recurring_invoice

POST /invoices/recurring

Create a new recurring invoice

get_recurring_invoice_options

GET /invoices/recurring/options

Get recurring invoice options

Sales Orders

Tool

Endpoint

Description

get_sales_order

GET /orders/sales/{id}

Get a single sales order

update_sales_order

PUT /orders/sales/{id}

Update a sales order

list_sales_orders

GET /orders/sales

Get a list of sales orders

create_sales_order

POST /orders/sales

Create a new sales order

get_sales_order_options

GET /orders/sales/options

Get sales order options

get_sales_order_pdf

GET /orders/sales/pdf/{id}

Get sales order PDF

send_sales_order

POST /orders/sales/send/{id}

Send a sales order

Quotations

Tool

Endpoint

Description

get_quotation

GET /quotations/{id}

Get a single quotation

update_quotation

PUT /quotations/{id}

Update a quotation

list_quotations

GET /quotations

Get a list of quotations

create_quotation

POST /quotations

Create a new quotation

get_quotation_options

GET /quotations/options

Get quotation options

get_quotation_pdf

GET /quotations/pdf/{id}

Get quotation PDF

send_quotation

POST /quotations/send/{id}

Send a quotation

Salesbook

Tool

Endpoint

Description

get_salesbook_invoice

GET /salesbook/{id}

Get a single salesbook invoice

update_salesbook_invoice

PUT /salesbook/{id}

Update a salesbook invoice

list_salesbook_invoices

GET /salesbook

Get a list of salesbook invoices

create_salesbook_invoice

POST /salesbook

Create a new salesbook invoice

get_salesbook_invoice_options

GET /salesbook/options

Get salesbook options

get_salesbook_invoice_pdf

GET /salesbook/pdf/{id}

Get salesbook PDF

Payment Conditions

Tool

Endpoint

Description

list_payment_conditions

GET /payment-conditions

Get all payment conditions

Templates

Tool

Endpoint

Description

list_templates

GET /templates

Get all templates

VAT

Tool

Endpoint

Description

list_vat_options

GET /vat

Get all VAT options

Ledgers

Tool

Endpoint

Description

list_ledgers

GET /ledgers

Get all ledger accounts

Costs

Tool

Endpoint

Description

list_cost_centres

GET /costs

Get all cost centre accounts

Currencies

Tool

Endpoint

Description

list_currencies

GET /currencies

Get all currencies

Journals

Tool

Endpoint

Description

list_journals

GET /journals

Get all journals

Subscription types

Tool

Endpoint

Description

list_subscription_types

GET /subscription-types

Get all subscription types

Attachments

Tool

Endpoint

Description

list_attachments

GET /attachments

Get all attachments

Products

Tool

Endpoint

Description

list_products

GET /products

Get all products

Receipts

Tool

Endpoint

Description

get_receipt

GET /receipts/{id}

Get a single receipt

update_receipt

PUT /receipts/{id}

Update a receipt

list_receipts

GET /receipts

Get a list of receipts

create_receipt

POST /receipts

Create a new receipt

Memorandum

Tool

Endpoint

Description

get_memorandum_entry

GET /memorandum/{id}

Get a single memorandum entry

update_memorandum_entry

PUT /memorandum/{id}

Update a memorandum entry

list_memorandum_entries

GET /memorandum

Get a list of memorandum entries

create_memorandum_entry

POST /memorandum

Create a new memorandum entry

Reports

Tool

Endpoint

Description

get_balance_report

GET /reports/balance

Get balance sheet

get_column_balance_report

GET /reports/column-balance

Get column balance

Tool naming

Names are derived from the HTTP method and path, not from prose, so they stay stable across spec updates:

Pattern

Example

GET /resources

list_relations

GET /resources/{id}

get_relation

POST /resources

create_relation

PUT /resources/{id}

update_relation

GET /resources/options

get_sales_invoice_options

GET /resources/pdf/{id}

get_sales_invoice_pdf

POST /resources/send/{id}

send_quotation

Endpoints the naming table does not recognise fall back to <verb>_<path slug>, so a spec refresh never produces a broken tool.

Keeping up with API changes

The tools are generated from Informer's OpenAPI document, so when Informer adds an endpoint the only thing missing is a fresh copy of that document. The server can fetch it itself.

Three layers, in order of precedence:

  1. A downloaded copy, cached at ~/.informer-mcp.spec.json.

  2. The bundled copy in openapi/api-docs.json, which ships with the server and always works offline.

  3. Neither is ever trusted blindly — a download must parse as an OpenAPI 3 document with at least one usable operation, or it is rejected and the current tools stay. A captive portal or a maintenance page cannot wipe your tool set.

On a schedule

Once a day, shortly after starting, the server checks for a newer document in the background. Startup is never blocked and a failed check is logged and ignored. INFORMER_SPEC_MAX_AGE_HOURS=0 turns it off.

On demand

The refresh_api_spec tool does the same thing when you ask for it — useful when an endpoint you expect is missing, or an argument is rejected as unknown:

"Refresh the Informer API description and tell me what changed."

{
  "adopted": true,
  "api_version": "2.0.0",
  "endpoints": 49,
  "tools": 68,
  "changes": {
    "added":   [{ "tool": "list_projects", "endpoint": "GET /projects" }],
    "removed": [],
    "changed": [{ "tool": "create_sales_invoice", "endpoint": "POST /invoices/sales",
                  "notes": ["body now requires: project_id"] }],
    "unchanged": 66
  },
  "note": "The tool list has been updated; no restart is needed."
}

Pass dry_run to see that report without applying anything.

The diff is deliberately specific: it names the tools that appeared and disappeared, and for the ones that changed it says what changed — a new argument, one that is gone, a field that is now required. That is the part a bare path comparison misses, and it is usually the part that would otherwise surface as a puzzling 422.

Adopting a document updates the running server: new tools are registered, withdrawn ones are removed, changed ones are re-advertised, and a tools/list_changed notification goes out so your client reloads the list mid-session.

The copy in the repository

npm run update-spec updates the bundled document and reports which paths came and went. That is the one to run when you want the change committed for everyone who installs the server; refresh_api_spec only affects your own machine.

Resources

The server also exposes the OpenAPI document itself as an MCP resource at informer://openapi.json, which is handy when you want the model to check a field definition without guessing.

Development

npm install         # install + build
npm run setup       # enter credentials in the browser
npm run bundle      # package as informer-mcp.mcpb for one-click install
npm run dev         # run from source with tsx
npm test            # vitest
npm run typecheck   # tsc --noEmit
npm run build       # compile to dist/
npm run tools       # print the tool surface
npm run update-spec # re-download openapi/api-docs.json and report added/removed paths

Project layout

openapi/api-docs.json   vendored OpenAPI 3.0 document — the source of truth
src/openapi.ts          spec → operations: tool names, JSON Schema conversion
src/client.ts           HTTP client: auth headers, retries, error formatting
src/tools.ts            operations → MCP tools, filtering, result formatting
src/server.ts           server assembly (tools + openapi resource)
src/spec.ts             download, validate, cache and diff the OpenAPI document
src/setup.ts            local setup server: verify credentials, write the config file
src/setup-page.ts       the HTML it serves
src/index.ts            stdio entry point and CLI
manifest.json           extension manifest: entry point and install-time settings
scripts/update-spec.mjs refresh the vendored spec
scripts/list-tools.ts   print/regenerate the tool reference
scripts/bundle.mjs      stage production dependencies and pack the .mcpb

Adding endpoints is normally not a code change at all — the running server picks them up by itself, and npm run update-spec commits the same change to the bundled copy. Only genuinely new URL shapes need a rule in the RESOURCES table in src/openapi.ts; without one they still become tools, just with a duller name.

How schemas are converted

OpenAPI 3.0 is not quite JSON Schema. On the way to the MCP tool definition:

  • #/components/schemas/X references become #/$defs/X, with only the transitive closure each operation actually needs inlined — so tool definitions stay small;

  • nullable: true becomes a ["type", "null"] union;

  • path and query parameters become top-level properties, request bodies go under body, and additionalProperties: false keeps typos from reaching the API.

Arguments are validated against that schema before any HTTP call is made.

Safety notes

  • This server can create, update and delete real bookkeeping records. Start with --read-only if you only need reporting, pin individual clients with "mode": "read-only", and let your MCP client prompt for approval on write tools.

  • Credentials for several clients in one process means one misrouted call touches someone else's books. The required administration argument, the enum of known aliases, the read-only restriction on fan-out, and the alias prefix on every error message ([acme] HTTP 422: ...) all exist for that reason. Keep the config file out of version control and readable only by you.

  • Tools are annotated with readOnlyHint, destructiveHint and idempotentHint, so clients that use those hints can gate the risky ones.

  • Nothing is logged to stdout, and credentials are never echoed in tool output or sent back to the setup page. open_setup returns a URL, never a key — an assistant has no way to read your credentials and no reason to ask you for them in a chat.

  • The API description is downloaded without credentials, and a document that does not parse as a usable OpenAPI 3 file is rejected rather than adopted.

License

MIT — see LICENSE, with one exception.

openapi/api-docs.json is Informer's own API description, retrieved unmodified from their published document. It is their work, carries no licence of its own, and is not covered by the MIT License that applies to the rest of this repository — a licence only grants what the grantor owns. It ships here so the server works offline and its tool surface is reproducible; at runtime the server can fetch the current version instead. See NOTICE.

Available Tools

71 tools
create_contactCreate a new contactC

Create a new contact.

Create a new contact person linked to a relation.

[Contacts] POST /contact

Inputs: body (required), administration.

create_memorandum_entryCreate a new memorandum entryB

Create a new memorandum entry.

Create a new memorandum journal entry. Debit and credit totals across all lines must be equal.

Optionally link a line to an existing sales invoice, purchase invoice or receipt by providing both type and invoice_id on the line.

[Memorandum] POST /memorandum

Inputs: body (required), administration.

create_purchase_invoiceCreate a new purchase invoiceA

Create a new purchase invoice.

Create a new purchase invoice. Use the /invoices/purchase/options endpoint first to determine valid combinations of vat_id and ledger_id.

The amount field per line is the gross amount (excl or incl VAT depending on vat_option). The vat_amount is the VAT portion of that amount.

[Purchase Invoices] POST /invoices/purchase

Inputs: body (required), administration.

create_quotationCreate a new quotationA

Create a new quotation.

Create a new quotation. Use the /quotations/options endpoint first to determine valid combinations of vat_id, ledger_id and vat_option.

For administrations in Austria (AT) or Germany (DE), the delivery_date field is also required.

[Quotations] POST /quotations

Inputs: body (required), administration.

create_receiptCreate a new receiptC

Create a new receipt.

Create a new receipt.

[Receipts] POST /receipts

Inputs: body (required), administration.

create_recurring_invoiceCreate a new recurring invoiceA

Create a new recurring invoice.

Create a new recurring invoice. Use the /invoices/recurring/options endpoint first to determine valid combinations of vat_id, ledger_id and vat_option.

Lines can be either regular lines (with qty, amount, vat_id, ledger_id) or info lines (with info=true and description only).

[Recurring Invoices] POST /invoices/recurring

Inputs: body (required), administration.

create_relationCreate a new relationA

Create a new relation.

Create a new relation. The relation_number is optional; if omitted or 0, a new number is generated. The fields sales_invoice_template_id and payment_condition_id are optional; default values will be used if not provided.

When relation_type is 0 (company): company_name is required, firstname/surname are forbidden. When relation_type is 1 (private): firstname and surname are required, company_name is forbidden.

[Relations] POST /relations

Inputs: body (required), administration.

create_salesbook_invoiceCreate a new salesbook invoiceA

Create a new salesbook invoice.

Create a new salesbook invoice. Use the /salesbook/options endpoint first to determine valid combinations of vat_id, ledger_id and vat_option.

A PDF file can optionally be attached as a base64-encoded string.

For administrations in Austria (AT) or Germany (DE), the delivery_date field is also required.

[Salesbook] POST /salesbook

Inputs: body (required), administration.

create_sales_invoiceCreate a new sales invoiceA

Create a new sales invoice.

Create a new sales invoice. Use the /invoices/sales/options endpoint first to determine valid combinations of vat_id, ledger_id and vat_option.

Lines can be either regular lines (with qty, amount, vat_id, ledger_id) or info lines (with info=true and description only).

For administrations in Austria (AT) or Germany (DE), the delivery_date field is also required.

[Sales Invoices] POST /invoices/sales

Inputs: body (required), administration.

create_sales_orderCreate a new sales orderA

Create a new sales order.

Create a new sales order. Requires the trade module to be active. Use the /orders/sales/options endpoint first to determine valid combinations of vat_id, ledger_id and vat_option.

For administrations in Austria (AT) or Germany (DE), the delivery_date field is also required.

[Sales Orders] POST /orders/sales

Inputs: body (required), administration.

delete_sales_invoice_attachmentDelete an invoice-specific attachmentA
DestructiveIdempotent

Delete an invoice-specific attachment.

Delete a document-specific attachment from a sales invoice. The file is permanently removed from storage.

[Sales Invoices] DELETE /invoices/sales/{id}/attachments/{attachment_id}

Inputs: id (required), attachment_id (required), administration.

download_sales_invoice_attachmentDownload an invoice attachmentA
Read-onlyIdempotent

Download an invoice attachment.

Download the file content of an attachment linked to a sales invoice, base64-encoded. Works for both shared library attachments and invoice-specific document attachments, as long as the attachment is linked to this invoice. The file content is only returned by this endpoint, not in the invoice GET response.

[Sales Invoices] GET /invoices/sales/{id}/attachments/{attachment_id}

Inputs: id (required), attachment_id (required), save_path, administration.

get_administrationGet administration detailsA
Read-onlyIdempotent

Get administration details.

Get details about the administration linked to this API key, including address, contact information, tax IDs and active modules.

[Administration] GET /administration

Inputs: administration.

get_balance_reportGet balance sheetB
Read-onlyIdempotent

Get balance sheet.

Get a balance sheet report for a given year range and period.

[Reports] GET /reports/balance

Inputs: period (required), year_to (required), year_from (required), administration.

get_column_balance_reportGet column balanceB
Read-onlyIdempotent

Get column balance.

Get a column balance (proef- en saldibalans) for a given year, period range and ledger account range.

[Reports] GET /reports/column-balance

Inputs: year (required), period_to (required), period_from (required), ledger_number_to (required), +2 more.

get_contactGet a single contactB
Read-onlyIdempotent

Get a single contact.

Get a single contact person by ID.

[Contacts] GET /contact/{id}

Inputs: id (required), administration.

get_memorandum_entryGet a single memorandum entryA
Read-onlyIdempotent

Get a single memorandum entry.

Get a single memorandum journal entry by ID, including all line items.

[Memorandum] GET /memorandum/{id}

Inputs: id (required), administration.

get_purchase_invoiceGet a single purchase invoiceA
Read-onlyIdempotent

Get a single purchase invoice.

Get a single purchase invoice by ID, including all line items.

[Purchase Invoices] GET /invoices/purchase/{id}

Inputs: id (required), administration.

get_purchase_invoice_optionsGet purchase invoice optionsA
Read-onlyIdempotent

Get purchase invoice options.

Get the available VAT rates with their compatible ledger accounts for creating purchase invoices.

[Purchase Invoices] GET /invoices/purchase/options

Inputs: administration.

get_purchase_invoice_pdfGet purchase invoice PDFA
Read-onlyIdempotent

Get purchase invoice PDF.

Download the PDF attached to a purchase invoice as a base64-encoded string.

[Purchase Invoices] GET /invoices/purchase/pdf/{id}

Inputs: id (required), save_path, administration.

get_quotationGet a single quotationA
Read-onlyIdempotent

Get a single quotation.

Get a single quotation by ID, including all line items.

[Quotations] GET /quotations/{id}

Inputs: id (required), administration.

get_quotation_optionsGet quotation optionsA
Read-onlyIdempotent

Get quotation options.

Get the available VAT rates with their compatible ledger accounts and VAT options for creating quotations.

[Quotations] GET /quotations/options

Inputs: administration.

get_quotation_pdfGet quotation PDFA
Read-onlyIdempotent

Get quotation PDF.

Download the PDF of a quotation as a base64-encoded string.

[Quotations] GET /quotations/pdf/{id}

Inputs: id (required), save_path, administration.

get_receiptGet a single receiptC
Read-onlyIdempotent

Get a single receipt.

Get a single receipt by ID.

[Receipts] GET /receipts/{id}

Inputs: id (required), administration.

get_recurring_invoiceGet a single recurring invoiceA
Read-onlyIdempotent

Get a single recurring invoice.

Get a single recurring invoice by ID, including all line items.

[Recurring Invoices] GET /invoices/recurring/{id}

Inputs: id (required), administration.

get_recurring_invoice_optionsGet recurring invoice optionsA
Read-onlyIdempotent

Get recurring invoice options.

Get the available VAT rates with their compatible ledger accounts and VAT options. Use this endpoint to determine valid combinations of vat_id, ledger_id and vat_option when creating recurring invoices. Per VAT rate the usable ledger accounts and compatible vat_option values are returned.

[Recurring Invoices] GET /invoices/recurring/options

Inputs: administration.

get_relationGet a single relationA
Read-onlyIdempotent

Get a single relation.

Get a single relation by ID. Includes contacts, tags and custom fields (free fields).

[Relations] GET /relations/{id}

Inputs: id (required), administration.

get_salesbook_invoiceGet a single salesbook invoiceA
Read-onlyIdempotent

Get a single salesbook invoice.

Get a single salesbook invoice by ID, including all line items.

[Salesbook] GET /salesbook/{id}

Inputs: id (required), administration.

get_salesbook_invoice_optionsGet salesbook optionsA
Read-onlyIdempotent

Get salesbook options.

Get the available VAT rates with their compatible ledger accounts and VAT options for creating salesbook invoices.

[Salesbook] GET /salesbook/options

Inputs: administration.

get_salesbook_invoice_pdfGet salesbook PDFA
Read-onlyIdempotent

Get salesbook PDF.

Download the PDF file attached to a salesbook invoice as a base64-encoded string.

[Salesbook] GET /salesbook/pdf/{id}

Inputs: id (required), save_path, administration.

get_sales_invoiceGet a single sales invoiceA
Read-onlyIdempotent

Get a single sales invoice.

Get a single sales invoice by ID, including all line items.

[Sales Invoices] GET /invoices/sales/{id}

Inputs: id (required), administration.

get_sales_invoice_optionsGet sales invoice optionsA
Read-onlyIdempotent

Get sales invoice options.

Get the available VAT rates with their compatible ledger accounts and VAT options. Use this endpoint to determine valid combinations of vat_id, ledger_id and vat_option when creating invoices.

[Sales Invoices] GET /invoices/sales/options

Inputs: administration.

get_sales_invoice_pdfGet sales invoice PDFA
Read-onlyIdempotent

Get sales invoice PDF.

Download the PDF of a sales invoice as a base64-encoded string.

[Sales Invoices] GET /invoices/sales/pdf/{id}

Inputs: id (required), save_path, administration.

get_sales_orderGet a single sales orderA
Read-onlyIdempotent

Get a single sales order.

Get a single sales order by ID, including all line items. Requires the trade module to be active.

[Sales Orders] GET /orders/sales/{id}

Inputs: id (required), administration.

get_sales_order_optionsGet sales order optionsA
Read-onlyIdempotent

Get sales order options.

Get the available VAT rates with their compatible ledger accounts and VAT options for creating sales orders. Requires the trade module to be active.

[Sales Orders] GET /orders/sales/options

Inputs: administration.

get_sales_order_pdfGet sales order PDFA
Read-onlyIdempotent

Get sales order PDF.

Download the PDF of a sales order as a base64-encoded string.

[Sales Orders] GET /orders/sales/pdf/{id}

Inputs: id (required), save_path, administration.

list_administrationsList configured administrationsA
Read-onlyIdempotent

List the client administrations this server is configured for, with the alias to pass as the "administration" argument of every other tool, and whether each one may be written to. Set "verify" to also fetch each company name from the API, which confirms the credentials work and that each alias points at the company you expect. To change any of it — add a client, replace a key, switch one to read-only — use open_setup.

Inputs: verify.

list_attachmentsGet all attachmentsB
Read-onlyIdempotent

Get all attachments.

Get a list of all available document attachments for this administration.

[Attachments] GET /attachments

Inputs: administration.

list_cost_centresGet all cost centre accountsA
Read-onlyIdempotent

Get all cost centre accounts.

Get a list of all cost centre accounts for this administration.

[Costs] GET /costs

Inputs: administration.

list_currenciesGet all currenciesA
Read-onlyIdempotent

Get all currencies.

Get a list of all currencies configured for this administration, including exchange rates.

[Currencies] GET /currencies

Inputs: administration.

list_journalsGet all journalsB
Read-onlyIdempotent

Get all journals.

Get a list of all journals (dagboeken) for this administration.

[Journals] GET /journals

Inputs: administration.

list_ledgersGet all ledger accountsA
Read-onlyIdempotent

Get all ledger accounts.

Get a list of all ledger accounts (chart of accounts) for this administration, including VAT codes, cost centre settings, RGS codes and condensation codes.

[Ledgers] GET /ledgers

Inputs: administration.

list_memorandum_entriesGet a list of memorandum entriesA
Read-onlyIdempotent

Get a list of memorandum entries.

Get a paginated list of all memorandum journal entries with their line items.

[Memorandum] GET /memorandum

Inputs: page, records, administration.

list_payment_conditionsGet all payment conditionsB
Read-onlyIdempotent

Get all payment conditions.

Get a list of all payment conditions configured for this administration.

[Payment Conditions] GET /payment-conditions

Inputs: administration.

list_productsGet all productsA
Read-onlyIdempotent

Get all products.

Get a list of all products for this administration, including supplier information. Requires the trade module to be active.

[Products] GET /products

Inputs: administration.

list_purchase_invoicesGet a list of purchase invoicesA
Read-onlyIdempotent

Get a list of purchase invoices.

Get a paginated list of all purchase invoices with their line items.

[Purchase Invoices] GET /invoices/purchase

Inputs: page, sort, filter, records, +3 more.

list_quotationsGet a list of quotationsA
Read-onlyIdempotent

Get a list of quotations.

Get a paginated list of all quotations with their line items.

[Quotations] GET /quotations

Inputs: page, sort, filter, records, +3 more.

list_receiptsGet a list of receiptsB
Read-onlyIdempotent

Get a list of receipts.

Get a paginated list of all receipts (bonnetjes) for this administration.

[Receipts] GET /receipts

Inputs: page, sort, filter, records, +1 more.

list_recurring_invoicesGet a list of recurring invoicesA
Read-onlyIdempotent

Get a list of recurring invoices.

Get a paginated list of all recurring invoices with their line items.

[Recurring Invoices] GET /invoices/recurring

Inputs: page, sort, filter, records, +3 more.

list_relationsGet a list of relationsA
Read-onlyIdempotent

Get a list of relations.

Get a paginated list of all relations. For each relation the contacts, tags and subtypes are included.

[Relations] GET /relations

Inputs: page, search, records, last_edit, +1 more.

list_salesbook_invoicesGet a list of salesbook invoicesB
Read-onlyIdempotent

Get a list of salesbook invoices.

Get a paginated list of all salesbook invoices with their line items.

[Salesbook] GET /salesbook

Inputs: page, sort, filter, records, +3 more.

list_sales_invoicesGet a list of sales invoicesB
Read-onlyIdempotent

Get a list of sales invoices.

Get a paginated list of all sales invoices with their line items.

[Sales Invoices] GET /invoices/sales

Inputs: page, sort, filter, records, +3 more.

list_sales_ordersGet a list of sales ordersA
Read-onlyIdempotent

Get a list of sales orders.

Get a paginated list of all sales orders with their line items. Requires the trade module to be active.

[Sales Orders] GET /orders/sales

Inputs: page, sort, filter, records, +3 more.

list_subscription_typesGet all subscription typesA
Read-onlyIdempotent

Get all subscription types.

Get a list of all subscription types (abonnementstypes) for this administration.

[Subscription types] GET /subscription-types

Inputs: administration.

list_templatesGet all templatesB
Read-onlyIdempotent

Get all templates.

Get a list of all document templates configured for this administration.

[Templates] GET /templates

Inputs: administration.

list_vat_optionsGet all VAT optionsA
Read-onlyIdempotent

Get all VAT options.

Get a list of all VAT/tax rates configured for this administration, including their percentages, codes and availability status.

[VAT] GET /vat

Inputs: administration.

open_setupOpen the Informer configuration pageA
Idempotent

Open the Informer settings, configuration or setup page. This is the single answer to every request about configuring this server: first-time setup, "open the config/settings/configuration site", adding a client or administration, changing or rotating an API key or security code, switching a client between read-only and read-write, removing one, or fixing a call that failed with 401 Authentication failed. It opens a form on 127.0.0.1 in the user's browser, one card per administration: alias, company name, API key, security code, access. Call this instead of searching the filesystem for config files, reading the installation directory, running the setup command in a shell, or asking the user for a key in the conversation — credentials belong in the page, not in a chat. Returns the URL to pass on in case the browser did not open. Saving verifies each key against the API and applies the change to this server immediately.

Inputs: no named parameters.

refresh_api_specRefresh the Informer API descriptionA
Idempotent

Download the current OpenAPI description from Informer and update this server's tools to match, without restarting. New endpoints become new tools, removed ones disappear, and changed arguments are re-advertised. Use it when an endpoint you expect is missing, when an argument is rejected as unknown, or to check whether Informer has changed anything. Pass dry_run to see the differences without applying them. This only touches this server; it never changes bookkeeping data.

Inputs: dry_run.

send_quotationSend a quotationA

Send a quotation.

Send a quotation via email, mark as sent, or send via Peppol.

[Quotations] POST /quotations/send/{id}

Inputs: id (required), body (required), administration.

send_sales_invoiceSend a sales invoiceB

Send a sales invoice.

Send a sales invoice via email, mark as sent, or send via Peppol. The invoice will be finalized before sending.

[Sales Invoices] POST /invoices/sales/send/{id}

Inputs: id (required), body (required), administration.

send_sales_orderSend a sales orderA

Send a sales order.

Send a sales order via email or mark as sent. Requires the trade module to be active. Peppol is not available for sales orders.

[Sales Orders] POST /orders/sales/send/{id}

Inputs: id (required), body (required), administration.

update_contactUpdate a contactA
Idempotent

Update a contact.

Update an existing contact person by ID.

[Contacts] PUT /contact/{id}

Inputs: id (required), body (required), administration.

update_memorandum_entryUpdate a memorandum entryA
Idempotent

Update a memorandum entry.

Update an existing memorandum journal entry. All lines are replaced with the newly provided lines. Debit and credit totals across all lines must be equal.

[Memorandum] PUT /memorandum/{id}

Inputs: id (required), body (required), administration.

update_quotationUpdate a quotationB
Idempotent

Update a quotation.

Update an existing quotation by ID.

[Quotations] PUT /quotations/{id}

Inputs: id (required), body (required), administration.

update_receiptUpdate a receiptB
Idempotent

Update a receipt.

Update an existing receipt.

[Receipts] PUT /receipts/{id}

Inputs: id (required), body (required), administration.

update_recurring_invoiceUpdate a recurring invoiceB
Idempotent

Update a recurring invoice.

Update an existing recurring invoice by ID.

[Recurring Invoices] PUT /invoices/recurring/{id}

Inputs: id (required), body (required), administration.

update_relationUpdate a relationB
Idempotent

Update a relation.

Update an existing relation by ID. Not all fields are required; you can send only the fields you want to update.

[Relations] PUT /relations/{id}

Inputs: id (required), body (required), administration.

update_salesbook_invoiceUpdate a salesbook invoiceC
Idempotent

Update a salesbook invoice.

Update an existing salesbook invoice by ID.

[Salesbook] PUT /salesbook/{id}

Inputs: id (required), body (required), administration.

update_sales_invoiceUpdate a sales invoiceA
Idempotent

Update a sales invoice.

Update an existing sales invoice by ID. The invoice must be in concept status.

[Sales Invoices] PUT /invoices/sales/{id}

Inputs: id (required), body (required), administration.

update_sales_orderUpdate a sales orderB
Idempotent

Update a sales order.

Update an existing sales order by ID. Requires the trade module to be active.

[Sales Orders] PUT /orders/sales/{id}

Inputs: id (required), body (required), administration.

upload_sales_invoice_attachmentUpload an invoice-specific attachmentA

Upload an invoice-specific attachment.

Upload a file as a document-specific attachment for a sales invoice. The file content must be base64-encoded. Supported types: PDF, PNG, JPEG, GIF, DOC, DOCX, XLS, XLSX. Maximum size: 10 MB. The attachment is automatically included when the invoice is sent by email and is preserved when the invoice is updated. Do not reference these IDs in the 'attachments' field of POST/PUT requests; manage them only through this endpoint.

[Sales Invoices] POST /invoices/sales/{id}/attachments

Inputs: id (required), body (required), administration.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 71 tools

    Disambiguation4/5

    每个工具都针对不同的资源或操作,命名后缀明确区分了销售发票、销售账簿发票、经常性发票、报价等相似概念。不过销售发票与销售账簿发票名称相近,仍需依赖描述细节来避免误选,因此略扣一分。

    Naming Consistency5/5

    所有工具都遵循一致的 snake_case verb_noun 模式,如 create_sales_invoice、list_relations、update_receipt、get_quotation_pdf,没有混用 camelCase 或不同的动词风格。即使像 open_setup 和 refresh_api_spec 这样的特殊工具也保持了可预测的动词开头。

    Tool Count2/5

    工具数量达到71个,远超25个的合理上限。虽然这个服务器试图完整覆盖 Informer API,但庞大的工具集对代理来说选择负担很重,而且大量重复的 CRUD 模式让规模显得臃肿。

    Completeness4/5

    覆盖了关系、联系人、销售/购买发票、经常性发票、销售订单、报价、收据、备忘录和报告等核心会计领域,并提供了选项、PDF、附件和发送等辅助操作。但缺少购买发票的更新操作,也没有任何通用的删除功能(除附件外),存在一些可绕过的小缺口。

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      MCP server to interact with the Cuéntica accounting API, allowing users to manage invoices, expenses, income, clients, providers, and bank accounts via natural language.
      59
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for the Billingo V3 Hungarian invoicing API. Manage invoices, partners, products, spendings, and bank accounts from any MCP client.
      14 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that wraps the cebelca.biz accounting API, exposing tools for operations like managing partners, invoices, proformas, and fetching PDFs.
      2
      -
    • A
      license
      B
      quality
      C
      maintenance
      Read-only MCP server for self-hosted Manager.io bookkeeping, providing curated GET tools to access accounting data like invoices, balances, and reports.
      10
      84 PyPI
      2
      MIT