What list_payments does
Returns a paginated list of payments from the organization, with optional filters (status, date range, customer, search term).
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 list_payments
Use this when the AI needs to scan, count, or summarize payments — for example, "show me everything overdue this week" or "how many payments are open right now?". The AI can chain a list call with a follow-up get_* call to drill into a specific 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
list_payments accepts 2 parameters. The AI fills these in from your natural-language prompt; you never write them by hand.
| Parameter | Type | Required | Description |
|---|---|---|---|
| invoiceId | string | optional | Filter by invoice ID |
| limit | number | optional | Max results (default 20) |
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 list_payments call looks like:
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "list_payments",
"arguments": {
"invoiceId": "inv_a1b2c3d4",
"limit": 20
}
}
}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 list_payments automatically.
“Show me all my payments.”
“How many payments do I have right now? Summarize them.”
Use it in 30 seconds
Related tools
More from the Payments category.
FAQ — list_payments
What is list_payments?▾
list_payments is one of 102 tools in InvoiceCave's MCP server. Returns a paginated list of payments from the organization, with optional filters (status, date range, customer, search term). 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 list_payments?▾
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 list_payments 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 list_payments take?▾
list_payments accepts 2 parameters, all optional. The AI populates these from your plain-English prompt — see the parameter table and request example above.
Does list_payments 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.