delete_recurring_invoice
Delete a recurring invoice profile. Already-generated invoices are NOT deleted.
What delete_recurring_invoice does
Permanently deletes the specified recurring invoice. 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_recurring_invoice
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_recurring_invoice accepts 1 parameter — 1 required, 0 optional. The AI fills these in from your natural-language prompt; you never write them by hand.
| Parameter | Type | Required | Description |
|---|---|---|---|
| id | string | required | Recurring invoice profile 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_recurring_invoice call looks like:
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "delete_recurring_invoice",
"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_recurring_invoice automatically.
“Delete this recurring invoice (I'll confirm first).”
Use it in 30 seconds
Related tools
More from the Recurring Invoices category.
list_recurring_invoicesList recurring invoice profiles. Optionally filter by status.
create_recurring_invoiceCreate a recurring invoice profile. Generates an invoice automatically on each period (weekly/monthly/etc.). Use generate_recurring_invoice_now to fire one immediately.
update_recurring_invoiceUpdate a recurring invoice profile. Note: line item changes require deleting and recreating the profile. Use this for metadata, frequency, end date, and discount/shipping/adjustment.
pause_recurring_invoicePause a recurring invoice profile so the cron stops generating invoices for it. Resume later with resume_recurring_invoice.
resume_recurring_invoiceResume a paused recurring invoice profile.
generate_recurring_invoice_nowManually trigger generation of an invoice from a recurring profile right now. Advances the profile's nextInvoiceDate.
FAQ — delete_recurring_invoice
What is delete_recurring_invoice?▾
delete_recurring_invoice is one of 102 tools in InvoiceCave's MCP server. Permanently deletes the specified recurring invoice. 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_recurring_invoice?▾
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_recurring_invoice 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_recurring_invoice take?▾
delete_recurring_invoice 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_recurring_invoice 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.