update_recurring_payment
Update a recurring payment profile.
What update_recurring_payment does
Updates an existing recurring payment. 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_recurring_payment
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_recurring_payment accepts 10 parameters — 1 required, 9 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 payment profile ID |
| profileName | string | optional | — |
| frequency | string | optional | — |
| customDays | number | optional | — |
| amount | number | optional | — |
| currency | string | optional | — |
| paymentMode | string | optional | — |
| endDate | string | optional | — |
| reference | string | optional | — |
| notes | string | 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_recurring_payment call looks like:
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "update_recurring_payment",
"arguments": {
"id": "id_a1b2c3d4",
"profileName": "Acme Corp",
"frequency": "example",
"customDays": 30,
"amount": 1500
}
}
}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_recurring_payment automatically.
“Update this recurring payment — change the …”
“Fix the details on that recurring payment.”
Use it in 30 seconds
Related tools
More from the Recurring Payments category.
list_recurring_paymentsList recurring payment profiles. Optionally filter by status.
create_recurring_paymentCreate a recurring payment profile (e.g. monthly retainer received). Tracks expected incoming payments. To record actual receipts, use record_payment against an invoice.
delete_recurring_paymentDelete a recurring payment profile.
pause_recurring_paymentPause a recurring payment profile.
resume_recurring_paymentResume a paused recurring payment profile.
FAQ — update_recurring_payment
What is update_recurring_payment?▾
update_recurring_payment is one of 102 tools in InvoiceCave's MCP server. Updates an existing recurring payment. 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_recurring_payment?▾
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_recurring_payment 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_recurring_payment take?▾
update_recurring_payment accepts 10 parameters — 1 required (id) and 9 optional. The AI populates these from your plain-English prompt — see the parameter table and request example above.
Does update_recurring_payment 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.