GoCardless MCP
for LuumenAI
Build GoCardless payment API integrations.
Operate GoCardless MCP from the same conversation as the hosts it runs on. Check jobs, queues, and interfaces without a second console; run diagnostic reports; and restart or update with the change previewed, approved, and logged.
The GoCardless MCP toolbox
24 tools: 16 read, 8 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet customerRetrieve a single customer by ID.
- ReadGet environmentReturns the current GoCardless environment (sandbox or live) and step-by-step instructions for switching.
- ReadGet mandateRetrieve a single mandate (Direct Debit authorisation) by ID.
- ReadGet paymentRetrieve a single payment by ID.
- ReadGet payoutRetrieve a single payout (settlement to your bank account) by ID.
- ReadGet refundRetrieve a single refund by ID.
- ReadGet subscriptionRetrieve a single subscription (recurring payment schedule) by ID.
- ReadIntegrate with gocardlessReturns an overview of GoCardless integration options for collecting one-off and recurring bank payments.
- ReadList customersList customers, optionally filtered by creation date.
- ReadList eventsAudit log of state changes across all resources (e.g.
- ReadList mandatesSearch or filter mandates (Direct Debit authorisations) by status, customer, or scheme.
- ReadList paymentsSearch, filter, or count payments by status, customer, mandate, subscription, currency, or date range.
- ReadList payoutsSearch or filter payouts (settlements to your bank account) by status, currency, or date range.
- ReadList refundsSearch or filter refunds by payment, mandate, or date range.
- ReadList subscriptionsSearch or filter subscriptions (recurring payment schedules) by status, customer, or mandate.
- ReadRead gocardless resourceServes GoCardless API documentation, how-to guides, and code samples — not live account data.
- WriteCancel mandatePermission required: mandates:write. Approval by default
- WriteCancel paymentPermission required: payments:write. Approval by default
- WriteCreate paymentPermission required: payments:write. Approval by default
- WriteCreate payment linkPermission required: payment_links:write. Approval by default
- WriteCreate payment template linkPermission required: payment_links:write. Approval by default
- WriteCreate refundPermission required: refunds:write. Approval by default
- WriteCreate subscriptionPermission required: subscriptions:write. Approval by default
- WriteSubmit feedbackSubmit a rating (1–5) of how helpful this MCP session was. Approval by default
Questions
Authorize once with OAuth 2.0. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — cancel mandate, cancel payment, create payment, create payment link, and more — is shown as a plan and requires approval by default, including the 7 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to GoCardless MCP — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
SAP BTPGateways, jobs, and subaccounts operated from one governed chat.
SalesforceRecords and integration jobs checked without a second console.
SAP S/4HANAJobs, queues, and records in SAP S/4HANA without a second console.
SAP SuccessFactorsJobs, queues, and records in SAP SuccessFactors without a second console.Put GoCardless MCP to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.