What create_expense_category does
Creates a new expense category in the organization. Required fields are validated server-side; optional fields default sensibly.
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 create_expense_category
Use when the AI needs to record something new — typically as the final step of a "set this up for me" workflow. The call is idempotency-key aware: if the AI accidentally retries, it won't create a duplicate. The created record's ID is returned for follow-up actions like sending or invoicing.
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
create_expense_category accepts 3 parameters — 1 required, 2 optional. The AI fills these in from your natural-language prompt; you never write them by hand.
| Parameter | Type | Required | Description |
|---|---|---|---|
| name | string | required | Category name |
| color | string | optional | Hex color (e.g. #ef4444). Default: #6b7280 |
| icon | string | optional | Icon name (lucide icon) |
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 create_expense_category call looks like:
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "create_expense_category",
"arguments": {
"name": "Acme Corp",
"color": "example",
"icon": "example"
}
}
}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 create_expense_category automatically.
“Create a new expense category for me.”
“Set up a expense category with these details: …”
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.
update_expense_categoryUpdate an expense category. Use isActive=false to soft-deactivate without deleting.
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 — create_expense_category
What is create_expense_category?▾
create_expense_category is one of 102 tools in InvoiceCave's MCP server. Creates a new expense category in the organization. Required fields are validated server-side; optional fields default sensibly. 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 create_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 create_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 create_expense_category take?▾
create_expense_category accepts 3 parameters — 1 required (name) and 2 optional. The AI populates these from your plain-English prompt — see the parameter table and request example above.
Does create_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.