moneybird_get
Get a single entity by ID from Moneybird.
LABSCO SUMMARY
Three tools that never go stale, in exchange for the caller needing to know the entity name.
A wrapper with a tool per entity is easier to discover and is out of date the moment Moneybird adds something. Naming the entity as a parameter keeps the surface at three definitions and reaches everything, with the escape hatch for whatever the pattern does not fit. The cost is that a model has to know that 'sales_invoices' is what the thing is called, which the tool descriptions partly address by listing common paths. For a bookkeeping API where most work is reading, this is a reasonable trade — and worth noting that it is read-oriented, with writes going through the raw request.
What it is
A deliberately thin Moneybird client: rather than a tool per entity type, three generic tools reach contacts, sales invoices, estimates and the rest by naming the entity.
What you get
- moneybird_list takes the entity type as a parameter, covering contacts, sales invoices, estimates and others through one call.
- moneybird_get fetches a single entity by id.
- moneybird_request makes a custom API request for anything the first two do not cover, with the common paths named in its description.
Requirements
MONEYBIRD_API_TOKEN and MONEYBIRD_ADMINISTRATION_ID — the administration id because a Moneybird account can hold several sets of books.
Setup effort
One command plus a key — npx moneybird-mcp-server, then supply credentials
USE CASES
01
Reading what is in the books
List the entity type you need — contacts, invoices, estimates — through one call rather than a tool per type.
02
Opening one record
Fetch it by id once the list has told you which one.
03
Doing something the two generic tools do not cover
Make the API request directly, using the common paths named in the tool description as a starting point.
3 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
moneybird_list
List entities from Moneybird. Entities: contacts, sales_invoices, estimates, recurring_sales_invoices, products, projects, time_entries, financial_accounts, ledger_accounts. Use filter for server-side filtering (e.g. state:open, period:this_month, contact_id:123).
moneybird_request
Make a custom Moneybird API request. Common paths: contacts, sales_invoices, estimates, recurring_sales_invoices, documents/purchase_invoices, documents/receipts, financial_accounts, financial_mutations, ledger_accounts, products, projects, time_entries, tax_rates, subscriptions, webhooks. See https://developer.moneybird.com for full docs.
BEFORE YOU INSTALL
What to know first
Tools you get
3 tools when we connected. The nine per-resource tools in the documentation, such as list_contacts and get_sales_invoice, no longer exist; pass the resource type to moneybird_list or moneybird_get. Writes go only through moneybird_request.
Requires
- npx on PATH
- Node.js
- MONEYBIRD_API_TOKEN in your environment
- MONEYBIRD_ADMINISTRATION_ID in your environment
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 3 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx moneybird-mcp-serverMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"moneybird": {
"command": "npx",
"args": [
"-y",
"moneybird-mcp-server"
],
"env": {
"MONEYBIRD_API_TOKEN": "<YOUR_MONEYBIRD_API_TOKEN>",
"MONEYBIRD_ADMINISTRATION_ID": "<YOUR_MONEYBIRD_ADMINISTRATION_ID>"
}
}
}
}
