Moneybird MCP Server

Moneybird MCP server exists for a simple reason — assistants are far more useful when they can act on Moneybird directly instead of describing what you should do. moneybird mcp server.

What you get

A Model Context Protocol (MCP) server that connects AI assistants like Claude to Moneybird accounting software via API.

This server allows AI assistants to interact with your Moneybird accounting data using the Model Context Protocol. It provides various tools to:

• Contact Management — List, retrieve, filter, create, and update contacts
• Advanced filtering by creation date, update date, name, and more
• Financial Data — Access sales invoices, financial accounts, and payments
• Business Operations — Manage products, projects, and time entries
• Custom Requests — Make custom API requests to Moneybird endpoints
• Interactive Assistant — Preconfigured prompt for a Moneybird assistant

What the assistant can call

Once Moneybird is connected, these are the calls the assistant has available:

• list_contacts — List all contacts in Moneybird
• get_contact — Get details for a specific contact by ID
• list_sales_invoices — List all sales invoices
• get_sales_invoice — Get details for a specific sales invoice by ID
• list_financial_accounts — List all financial accounts
• list_products — List all products
• list_projects — List all projects
• list_time_entries — List all time entries
• moneybird_request — Make a custom request to the Moneybird API

Setting it up

moneybird-mcp-server on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration and credentials

You will need 2 environment variables: MONEYBIRD_API_TOKEN, MONEYBIRD_ADMINISTRATION_ID. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js (v18 or higher recommended) - A Moneybird account with API access - A Moneybird API token

Choosing this one

Plenty of payments and commerce servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Moneybird's toolset — list_contacts, get_contact, list_sales_invoices and 6 more — is a fair guide to whether it matches your workflow. It is maintained by vanderheijden86; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Moneybird.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the moneybird mcp server does with a few real requests.