The MCP now handles unscheduled tasks and payments

What's new

• The MCP server adds task tools: list tasks to schedule, unassigned ones or those from a chat order, create one with or without a time, give it a time and assign people to it.
• And payment tools: record and void manual payments and look up a task's balance or a customer's account. Fiuit always computes the balance.
• Payments move money, so they require explicit confirmation (confirm=true) and follow the same limits, idempotency and audit trail as the API.
• Payment tools only appear for keys with the matching permission: a key without payment permissions neither sees nor can use them.

Preparation without confirm returns idempotency_key; confirmation requires that key or an agent-supplied key (1-128 characters). Reuse the same key, destination and payload for every retry, including lost responses. A new operation requires a new key, even for an identical payment.

By default, list_tasks omits contacts, exact addresses, coordinates, notes and forms. include_sensitive=true requests full details and also requires customers:read. Movements in get_customer_account and charge history in get_task_balance omit receiver names, notes and reasons; the same opt-in also requires payments:read. Keys with mode=test only see read tools.