Skip to main content
These are the tools your MCP client can call once you’ve connected to https://api.kualia.com/mcp. Names and parameters match exactly what the server registers. The same catalog powers the in-app AI Assistant. See MCP overview for how to connect, and the per-client guides (ChatGPT, Claude, Claude Code, Cursor, Perplexity) for client-specific setup.

Workspaces & accounts

Transactions

Creating transactions

For a regular, single-movement transaction, pass amount and choose one of:
  • categoryId to categorize it.
  • readyToAssign: true to treat it as income for Ready to Assign. This creates a movement with no category.
  • Neither field to leave it uncategorized or let Kualia apply rules and suggestions.
Do not combine readyToAssign: true with categoryId on the same transaction or movement. For split transactions, pass movements and put readyToAssign: true on the specific movement that should go to Ready to Assign.

Categories & groups

Budgets & targets

Reports

Common parameters

  • workspaceId is optional on every tool and defaults to the user’s active workspace. Pass it explicitly only when the user has multiple workspaces and you need a non-default one. Get ids from kualia_list_workspaces.
  • yearMonth is YYYYMM (e.g. 202604 for April 2026). currentDate is YYYY-MM-DD.
  • Batch limits: transactions up to 200 per call; categories up to 50; category groups up to 10.
  • Money is encoded as a signed decimal string in the workspace currency, with at most minorUnit fractional digits (USD = 2 → "51.08"; JPY = 0 → "5108"; KWD = 3 → "5.108"). Each money-bearing response carries currencyCode, minorUnit, and amountEncoding: 'decimal_string'. Don’t scale by 100.
All tools respect per-workspace permissions. The server only returns and modifies data your account can access. Agent-driven updates also preserve a transaction’s reviewStatus: rows created or edited through MCP stay as Needs Review until you mark them reviewed in the app yourself.