update_expense_category
Update an expense category. Use isActive=false to soft-deactivate without deleting.
What update_expense_category does
Updates an existing expense category. Pass only the fields you want to change — every other field is preserved.
This tool is part of InvoiceCave's open MCP server — the most MCP-complete invoicing platform on the market with 102 tools covering invoices, customers, quotes, expenses, payments, recurring schedules, accounting, and reports. Every tool is callable from any MCP-compatible AI client without writing a single line of integration code.
How an AI uses update_expense_category
Use this for partial edits — "change the due date to Net 30", "fix the customer's billing address", "update the line item description". The AI can read the current state with the matching get_* tool first if it needs to confirm what it's editing.
You don't call this tool directly — you ask the AI in plain English and the MCP client decides which tool to invoke based on your request. The example prompts below were lifted from real Claude Desktop sessions, so you can use them verbatim or adapt them to your data.
Parameters
update_expense_category accepts 5 parameters — 1 required, 4 optional. The AI fills these in from your natural-language prompt; you never write them by hand.
| Parameter | Type | Required | Description |
|---|---|---|---|
| id | string | required | Category ID |
| name | string | optional | — |
| color | string | optional | — |
| icon | string | optional | — |
| isActive | boolean | optional | — |
Request example
Under the hood, your AI client sends a JSON-RPC 2.0 tools/call request to InvoiceCave's MCP endpoint at https://www.invoicecave.com/api/mcp/mcp. Here's what a update_expense_category call looks like:
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "update_expense_category",
"arguments": {
"id": "id_a1b2c3d4",
"name": "Acme Corp",
"color": "example",
"icon": "example",
"isActive": true
}
}
}You won't write this yourself — it's shown so developers can see exactly what the MCP client generates. The arguments object maps 1:1 to the parameters above. Authentication is handled by the Authorization: Bearer header with your API key.
Example AI prompts
Type any of these into Claude Desktop, Claude Code, or Cursor — InvoiceCave's MCP server will route them to update_expense_category automatically.
“Update this expense category — change the …”
“Fix the details on that expense category.”
Use it in 30 seconds
Related tools
More from the Expenses category.
list_expensesList expenses with totals. Filter by status, category, vendor, date range, customer, or billable flag.
get_expenseGet full details of a specific expense.
create_expenseRecord a new expense. Auto-generates an EXP-XXXXXX number. If bankAccountId is provided, deducts the amount from the bank balance.
update_expenseUpdate an existing expense. If amount changes and the expense has a bankAccountId, the bank balance is auto-adjusted.
delete_expenseDelete an expense. If it had a bankAccountId, the deducted amount is added back to the balance.
list_expense_categoriesList all active expense categories for the organization.
create_expense_categoryCreate a new expense category.
delete_expense_categoryDelete an expense category. Fails if any expenses still use it — reassign or delete those first, or use update_expense_category with isActive=false.
FAQ — update_expense_category
What is update_expense_category?▾
update_expense_category is one of 102 tools in InvoiceCave's MCP server. Updates an existing expense category. Pass only the fields you want to change — every other field is preserved. It's invoked automatically when an AI client like Claude or Cursor decides the user's request maps to this action.
Which AI clients can call update_expense_category?▾
Any MCP-compatible client. We've tested it with Claude Desktop, Claude Code, Cursor, Windsurf, and Codex. The MCP protocol is open, so any AI tool that speaks MCP can call this endpoint with a valid InvoiceCave API key.
Is calling update_expense_category secure?▾
Yes. Every call is authenticated by the API key you mint in the dashboard, scoped to a single organization, rate-limited per key, and recorded in the audit log with source='mcp'. Sensitive fields (SMTP passwords, encryption keys) are never returned to the AI client.
What parameters does update_expense_category take?▾
update_expense_category accepts 5 parameters — 1 required (id) and 4 optional. The AI populates these from your plain-English prompt — see the parameter table and request example above.
Does update_expense_category count against any quota?▾
MCP tool calls are unmetered on the free plan up to a generous monthly limit. Once you connect Stripe and start charging your customers, every call still counts against the same per-key rate limit but doesn't add to your bill.
Ready to wire this up?
Free plan — no credit card. 102 tools at your AI's disposal.