Read CashCtrl accounts, journal, orders, people, articles, salaries and reports; book and create. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"cashctrl": {
"url": "https://cashctrl.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"cashctrl": {
"type": "http",
"url": "https://cashctrl.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your CashCtrl organization and CashCtrl API key.
Create the key in CashCtrl under Settings → Users & Roles → Add → Add API user (the API needs a PRO account; one API user per organization). The role of the API user decides what this server can read and change, so a read-only role makes it read-only. The organization is the "myorg" part of myorg.cashctrl.com. Your key is used only to call the CashCtrl API of that organization on your behalf; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your CashCtrl organization and CashCtrl API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
| Tool | Type | What it does |
|---|---|---|
cashctrl_list_accounts | read | List accounts The chart of accounts: number, name, category and the balance for the fiscal period. Not paged. GET /account/list.json. |
cashctrl_get_account | read | Get an account One account of the chart of accounts by id. GET /account/read.json. |
cashctrl_get_account_balance | read | Get an account balance The balance of one account at the end of a day (default: the last day of the current fiscal period). GET /account/balance. |
cashctrl_list_account_categories | read | List account categories The categories of the chart of accounts (assets, liabilities, expenses, revenue and their sub-categories). GET /account/category/list.json. |
cashctrl_list_bank_accounts | read | List bank accounts The bank accounts set up in CashCtrl (name, IBAN, linked ledger account). GET /account/bank/list.json. |
cashctrl_list_journal | read | List journal entries Book entries of the journal (date, title, debit and credit account, amount, reference), newest first, for the current fiscal period unless fiscal_period_id is set. GET /journal/list.json. |
cashctrl_get_journal_entry | read | Get a journal entry One book entry by id, with its items for a collective entry. GET /journal/read.json. |
cashctrl_list_orders | read | List orders Sales or purchase documents (quotes, order confirmations, invoices, delivery notes, credit notes, vendor bills) with number, date, customer, status and total. Newest first. GET /order/list.json. |
cashctrl_get_order | read | Get an order One order (invoice, quote, purchase document) by id, with its items, totals and status. GET /order/read.json. |
cashctrl_list_order_categories | read | List order categories The order categories (Quote, Invoice, Credit note, Purchase invoice and so on) with their statuses (Draft, Open, Paid) and the default accounts and sequence numbers. Use it to find category_id and status_id (type PURCHASE for purchase documents). GET /order/category/list.json. |
cashctrl_list_persons | read | List people Customers, vendors, employees and other contacts (name, company, number, roles, addresses). GET /person/list.json. |
cashctrl_get_person | read | Get a person One person or company by id, with addresses, contact data and bank accounts. GET /person/read.json. |
cashctrl_list_articles | read | List inventory articles Inventory articles (products and services) with number, name, price, stock and accounts. GET /inventory/article/list.json. |
cashctrl_get_article | read | Get an inventory article One inventory article by id. GET /inventory/article/read.json. |
cashctrl_list_salary_statements | read | List salary statements Payroll statements (employee, date, status, gross and net amounts), newest first. Sensitive personal data. GET /salary/statement/list.json. |
cashctrl_get_salary_statement | read | Get a salary statement One payroll statement by id, with its salary items. Sensitive personal data. GET /salary/statement/read.json. |
cashctrl_list_fiscal_periods | read | List fiscal periods All fiscal periods (id, name, start, end, current flag). The id is the fiscal_period_id of the other tools. GET /fiscalperiod/list.json. |
cashctrl_list_tax_codes | read | List tax codes The VAT tax codes (id, code, name, rates). The id is the tax_id of the write tools. GET /tax/list.json. |
cashctrl_list_sequence_numbers | read | List sequence numbers The number sequences (for journal references, order numbers, customer numbers). The id is the sequence_number_id of the write tools. GET /sequencenumber/list.json. |
cashctrl_list_currencies | read | List currencies The currencies set up in CashCtrl with their exchange rates. GET /currency/list.json. |
cashctrl_get_report_tree | read | Get the report tree The reports set up in CashCtrl (balance sheet, income statement, and so on) as a tree of collections and elements. The element id is the input of cashctrl_get_report_data. GET /report/tree.json. |
cashctrl_get_report_data | read | Get report data The data of one report element (for example the balance sheet or the income statement) for a fiscal period or a date range. GET /report/element/data.json. |
cashctrl_create_journal_entry | write | Create a journal entry WRITE: changes the accounting records. Makes one request that is never repeated; check the result before trying again. Creates a manual book entry in the journal. Either a simple entry (debit_account_id, credit_account_id, amount) or a collective entry (items, whose debit and credit sums must match). POST /journal/create.json. |
cashctrl_delete_journal_entries | write | Delete journal entries WRITE: changes the accounting records. Makes one request that is never repeated; check the result before trying again. DELETES manual journal entries by id (entries created by orders or salary statements cannot be deleted this way). Deleted entries are gone from the books; confirm the ids with the user first. POST /journal/delete.json. |
cashctrl_create_order | write | Create an order WRITE: changes the accounting records. Makes one request that is never repeated; check the result before trying again. Creates ONE order document for ONE customer or vendor: a quote, invoice, credit note, purchase bill and so on, depending on category_id. Without status_id the first status of the category is used; a booking status (for example Open) also creates journal entries, so use a draft status unless the user asks otherwise. No e-mail is sent. POST /order/create.json. |
cashctrl_update_order_status | write | Change the status of orders WRITE: changes the accounting records. Makes one request that is never repeated; check the result before trying again. Sets the status of 1-20 orders (for example Draft to Open, or Open to Paid). A status can book journal entries or move stock, so the books change. POST /order/update_status.json. |
cashctrl_delete_orders | write | Delete orders WRITE: changes the accounting records. Makes one request that is never repeated; check the result before trying again. DELETES orders (invoices, quotes, purchase documents) by id, with the journal entries they created. Deleted documents are gone; confirm the ids with the user first. POST /order/delete.json. |
cashctrl_create_person | write | Create a person or company WRITE: changes the accounting records. Makes one request that is never repeated; check the result before trying again. Creates a customer, vendor or other contact. Give company, first_name or last_name (at least one). Search first with cashctrl_list_persons so no duplicate is created. POST /person/create.json. |
cashctrl_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
cashctrl_request_feature | Request a missing feature Tell usefulapi that the user needs something the CashCtrl tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
cashctrl_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED CashCtrl tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
cashctrl_cancel_subscription | Cancel the Pro subscription Cancel the caller's CashCtrl Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run cashctrl_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Proper organization | $9/mo · $90/yr | Unlimited |
Pro covers this CashCtrl server only. Subscribe with cashctrl_upgrade (it returns a Stripe Checkout link). Cancel any time with cashctrl_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running cashctrl_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by CashCtrl. The server calls the CashCtrl API with your own CashCtrl access, so it sees only the data that your account can see.
The login page asks for your CashCtrl organization and CashCtrl API key. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your CashCtrl organization and CashCtrl API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the CashCtrl API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in CashCtrl.
Yes, if you approve it. 6 of the 28 CashCtrl tools can create or change data. The other 22 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this CashCtrl server only. Run cashctrl_usage_status to see how many calls you used.
Ask the AI to run cashctrl_upgrade: it returns a Stripe Checkout link. To cancel, run cashctrl_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with cashctrl_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.