Stripe · Payments
STRIPE_LIST_CUSTOMERS
List customers from the connected Stripe account. Returns { customers: [{ id, email, name, created }], has_more }.
- Provider
- Stripe
- Access
- Read
- Category
- Payments
- Version
- v1
Input schema
{
"type": "object",
"properties": {
"limit": {
"type": "number",
"description": "Max customers to return (default 10, max 100)."
},
"startingAfter": {
"type": "string",
"description": "Cursor: a customer ID to page after."
},
"email": {
"type": "string",
"description": "Optional exact email filter."
}
},
"additionalProperties": false
}How to call it
Expose this tool to any MCP-capable agent (Claude, GPT, or your own) through CybrLink's MCP server. The agent calls stripe_list_customers with arguments matching the schema above.
CybrLink validates the input, injects the connected Stripe credentials server-side, and runs a single scoped provider API call through the shared proxy — the same guarded path as the generic call_api tool. The raw secret never reaches the model, and the response is trimmed to just the fields the agent needs.
Frequently asked
- How do I let an AI agent stripe list customers?
- Connect Stripe to CybrLink, then expose the `stripe_list_customers` tool to any MCP-capable agent (Claude, GPT, or a custom framework). The agent calls it with typed arguments; CybrLink injects the Stripe credential server-side and runs one scoped API call. List customers from the connected Stripe account. Returns { customers: [{ id, email, name, created }], has_more }.
- Does the AI model see my Stripe credentials when using STRIPE_LIST_CUSTOMERS?
- No. CybrLink stores the credential in a token vault and injects it on the server for each call, so the model can read this data from Stripe without the OAuth token or API key ever entering its context.