Tools
The server exposes 118 tools across 22 resource families — one for each operation of the REST API. Each tool dispatches in-process to the /v1 endpoint that already implements the operation, so filters, validation, business rules and organization isolation are exactly the API's — the tool is the endpoint.
How to read these pages
Each tool is listed with four facts:
dunning_charges_notify· destructive ·charges.notify·POST /v1/charges/{id}/notify
| Field | Meaning |
|---|---|
| read / write / destructive | The annotation the MCP client reads. A destructive tool (deletes, archives, cancels, reaches the debtor or a third party — a message, a credit bureau, a notary, a webhook —, decides on the debt or rotates a secret) runs only after the user confirms in the form the server sends, on revision 2026-07-28; a client that cannot confirm gets confirmation_required. |
| permission | The dashboard permission the person who owns the token must hold in the organization. |
METHOD /path | The /v1 endpoint the tool dispatches to, to cross-reference with the API reference. |
| What it does | The first sentence of the tool's description, exactly as the model receives it. |
Common arguments
They appear on many tools and always mean the same thing.
| Argument | Type | Description |
|---|---|---|
page | integer | Page, starting at 1. |
per_page | integer | Items per page, at most 100. |
sort_by | string | Sort field, in snake_case (e.g. due_date). A value outside the endpoint's list falls back to the default. |
sort_order | asc | desc | Sort direction. |
include | string | Relations to embed in the response, comma-separated (e.g. person). |
idempotency_key | string | Replay guard on every write, sent as X-Idempotency-Key. |
The catalogue
A tool you cannot run does not appear in tools/list. If one from this page is missing, see Authentication.