GoCardless MCP for AI agents
Agents read GoCardless MCP at once. Changes and sends are held for a person's approval by default.
About GoCardless MCP
Build GoCardless payment API integrations.
What an agent can do in GoCardless MCP
Every GoCardless MCP action is classed by the platform as a read, a change or a send. Reads run at once. Changes and sends are held for a person by default.
Runs at once (reads)
Looks things up in GoCardless MCP without asking first. 16 actions.
- Get customerRetrieve a single customer by ID. PII fields are partially masked. Use when you have a known customer ID (CU…). To search or list multiple customers, use list_customers.
- Get environmentReturns the current GoCardless environment (sandbox or live) and step-by-step instructions for switching. Use this when the user asks which environment they are in, wants to switch to live, wants to s
- Get mandateRetrieve a single mandate (Direct Debit authorisation) by ID. Use when you have a known mandate ID (MD…). To search or filter across mandates, use list_mandates.
- Get paymentRetrieve a single payment by ID. Use when you have a known payment ID (PM…). To search or filter across multiple payments, use list_payments.
- Get payoutRetrieve a single payout (settlement to your bank account) by ID. Use when you have a known payout ID (PO…). To search or filter across payouts, use list_payouts.
- Get refundRetrieve a single refund by ID. Use when you have a known refund ID (RF…). To search or filter across refunds, use list_refunds.
- Get subscriptionRetrieve a single subscription (recurring payment schedule) by ID. Use when you have a known subscription ID (SB…). To search or filter across subscriptions, use list_subscriptions.
- Integrate with gocardlessReturns an overview of GoCardless integration options for collecting one-off and recurring bank payments. This tool returns an overview only — you MUST then call read_gocardless_resource with the rele
- List customersList customers, optionally filtered by creation date. PII fields are partially masked. For a single known customer ID, use get_customer.
- List eventsAudit log of state changes across all resources (e.g. payment confirmed, mandate cancelled). Use for audit trails and webhook debugging. Not for querying amounts or counts — use list_payments for that
- List mandatesSearch or filter mandates (Direct Debit authorisations) by status, customer, or scheme. For a single known mandate ID, use get_mandate.
- List paymentsSearch, filter, or count payments by status, customer, mandate, subscription, currency, or date range. Use for any multi-record query. For a single known payment ID, use get_payment.
Show all 16
- List payoutsSearch or filter payouts (settlements to your bank account) by status, currency, or date range. For a single known payout ID, use get_payout.
- List refundsSearch or filter refunds by payment, mandate, or date range. For a single known refund ID, use get_refund.
- List subscriptionsSearch or filter subscriptions (recurring payment schedules) by status, customer, or mandate. For a single known subscription ID, use get_subscription.
- Read gocardless resourceServes GoCardless API documentation, how-to guides, and code samples — not live account data. Use this to fetch API endpoint details, integration guides, and code samples. Available URIs: - gocardless
Held for approval by default (changes and sends)
Held for a person's approval by default. The approval is recorded and the action is sent once, never twice, with 10 seconds to undo. 8 actions.
- Cancel mandatePermission required: mandates:write. Ask the user to reconnect GoCardless and grant this permission to enable this tool.
- Cancel paymentPermission required: payments:write. Ask the user to reconnect GoCardless and grant this permission to enable this tool.
- Create paymentPermission required: payments:write. Ask the user to reconnect GoCardless and grant this permission to enable this tool.
- Create payment linkPermission required: payment_links:write. Ask the user to reconnect GoCardless and grant this permission to enable this tool.
- Create payment template linkPermission required: payment_links:write. Ask the user to reconnect GoCardless and grant this permission to enable this tool.
- Create refundPermission required: refunds:write. Ask the user to reconnect GoCardless and grant this permission to enable this tool.
- Create subscriptionPermission required: subscriptions:write. Ask the user to reconnect GoCardless and grant this permission to enable this tool.
- Submit feedbackSubmit a rating (1–5) of how helpful this MCP session was. Call this at the end of a session when the user expresses satisfaction or dissatisfaction, or when they explicitly ask to leave feedback.
Changes wait in Needs you
Changes and sends in GoCardless MCP are held for a person's approval by default. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
GoCardless MCP questions
Can an agent change data in GoCardless MCP on its own?
Not by default. Changes and sends in GoCardless MCP are held for a person's approval. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
What can an agent read in GoCardless MCP?
This connector lists 16 read actions. Reads run at once, without waiting for approval.
How does GoCardless MCP connect?
It connects with dcr oauth. Connectors are built and maintained by third-party developers; availability is confirmed during scoping.