All 102 tools
Chart of Accounts & Journals

delete_account

Delete an account. Fails if it has any journal lines — deactivate via update_account isActive=false instead.

Write · Remove record

What delete_account does

Permanently deletes the specified account. Most domains soft-delete (the record stays in the audit log) so this is reversible by an admin.

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 delete_account

The AI should always confirm with the user before calling a delete_* tool. InvoiceCave's audit log records the source as 'mcp' so you can always trace which AI client and which tool call removed the record.

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

delete_account accepts 1 parameter — 1 required, 0 optional. The AI fills these in from your natural-language prompt; you never write them by hand.

ParameterTypeRequiredDescription
idstringrequiredAccount ID

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 delete_account call looks like:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "delete_account",
    "arguments": {
      "id": "id_a1b2c3d4"
    }
  }
}

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 delete_account automatically.

“Delete this account (I'll confirm first).”

Use it in 30 seconds

Claude Desktop
Paste a JSON config
Claude Code
One CLI command
Cursor
Edit MCP config

Related tools

More from the Chart of Accounts & Journals category.

list_accounts

List chart of accounts. Optionally filter by type (Asset, Liability, Equity, Revenue, Expense).

list_journal_entries

List journal entries. Optionally filter by status (Draft, Posted, Void).

create_account

Create a new account in the chart of accounts. Codes must be unique within the org.

update_account

Update an existing chart-of-accounts entry. Code uniqueness is enforced.

seed_chart_of_accounts

Seed the org with a standard 39-account chart of accounts (Assets/Liabilities/Equity/Revenue/Expense). Fails if any accounts already exist.

create_journal_entry

Create a journal entry. Validates double-entry (sum of debits must equal sum of credits). Pass status="Posted" to auto-post and update account balances; otherwise creates as Draft.

post_journal_entry

Post a Draft journal entry. Updates affected account balances. Cannot be undone — to reverse, use void_journal_entry.

void_journal_entry

Void a journal entry. If it was Posted, account balances are reversed. Voided entries cannot be edited.

FAQ — delete_account

What is delete_account?▾

delete_account is one of 102 tools in InvoiceCave's MCP server. Permanently deletes the specified account. Most domains soft-delete (the record stays in the audit log) so this is reversible by an admin. 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 delete_account?▾

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 delete_account 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 delete_account take?▾

delete_account accepts 1 parameter — 1 required (id). The AI populates these from your plain-English prompt — see the parameter table and request example above.

Does delete_account 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.

Get an API key Back to /mcp