list_payment_methods
List configured payment methods for one project. Credentials and provider secrets are never returned.
List configured payment methods for one project. Safe to call for agents deciding whether a plan can charge against a given provider.
Provider secrets — API keys, webhook secrets, Stripe Connect account IDs — are always stripped before the response returns.
Requires ability
The token behind the MCP session must hold it, or the call is refused with TOKEN_MISSING_ABILITY.
Runs the same action as
The REST endpoint and this tool share one action, so validation, permissions and events are identical.
Annotations
It reads and never changes anything.
Arguments
project_id*stringUUID of the project whose payment methods to list.
active_onlybooleanoptionalWhen true, omits deactivated payment methods.
What it returns
{ "data": [ { "id": "8b0c4a15-e792-4360-95d8-1f47c0b3e926", "provider": "stripe", "connector": null, "mode": "live", "active": true, "created_at": "2026-03-01T00:00:00Z" } ], "meta": { "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13", "total": 2 }}How it fails
TOKEN_MISSING_ABILITYtoken lacks project-payment-method:view-any.
RESOURCE_NOT_FOUNDproject_id names a project the token cannot see: unknown, another team's, or outside the token's scope:project: allow-list. A project with no payment methods returns an empty list, not an error.
How is this guide?
Last updated on