GoCardless MCP. Manage Mandates and Direct Debits via Conversation
Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
GoCardless connects your merchant account to your AI client via Model Context Protocol (MCP). It lets you manage direct debit payments, track customer mandates, and oversee bank payouts by talking to your agent.
Use it to initiate collections, check mandate status, or list payment history without logging into a separate portal. It handles the full lifecycle of recurring and one-off bank payments.
What your AI agents can do
Create new payment
Initiates a direct debit collection for a specific customer.
Get account details
Fetches basic identifying information for the connected GoCardless account.
Get customer details
Retrieves detailed metadata for a specified customer record.
Initiates a direct debit collection using the create_new_payment tool.
Retrieves a customer's profile and bank account details using get_customer_details.
Checks the active status and details of a customer's payment mandate via get_mandate_status.
Retrieves a list of all direct debit collections, showing their current status using list_direct_debit_payments.
Gets a list of funds being sent from GoCardless to your bank account using list_merchant_payouts.
Retrieves details on all active and inactive recurring subscription plans using list_recurring_subscriptions.
Ask AI about this MCP
Supported MCP Clients
Waiting for input…
GoCardless MCP Server: 12 Tools for Payment Operations
Use these 12 tools to programmatically manage every aspect of your direct debit payments, from checking mandates to listing payouts.
019d75a7create new payment
Initiates a direct debit collection for a specific customer.
019d75a7get account details
Fetches basic identifying information for the connected GoCardless account.
019d75a7get customer details
Retrieves detailed metadata for a specified customer record.
019d75a7get mandate status
Checks the current status and details of a customer payment mandate.
019d75a7get payment details
Gets the specific metadata and status for a single payment transaction.
019d75a7list direct debit payments
Lists all direct debit collections, including their status (confirmed, failed).
019d75a7list merchant payouts
Retrieves a list of funds that have been paid out to your bank account.
019d75a7list payment customers
Lists all customer accounts registered in the GoCardless system.
019d75a7list payment mandates
Lists all active payment mandates associated with customers.
019d75a7list payment refunds
Lists all processed refunds and reversed payments for auditing purposes.
019d75a7list recurring subscriptions
Retrieves a list of active and inactive recurring payment plans.
019d75a7verify api connection
Confirms that the MCP server connection to GoCardless is active and authorized.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with GoCardless, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
You connect your GoCardless merchant account to your AI client using the Model Context Protocol (MCP). This lets your agent handle direct debits, track customer mandates, and manage bank payouts without you having to log into a separate portal. It manages the whole lifecycle of recurring and one-off bank payments.
Running Payments
Your agent uses create_new_payment to initiate a direct debit collection for a specific customer.
Checking Customer Data
It retrieves a customer's profile and bank account details using get_customer_details. You can also get basic identifying information for the connected GoCardless account with get_account_details. To see all registered customer accounts, use list_payment_customers.
Managing Mandates
Your agent checks a customer's payment mandate status and details with get_mandate_status. You can also list all active payment mandates associated with customers using list_payment_mandates.
Listing Payments
It pulls a list of all direct debit collections, showing their current status—like confirmed or failed—via list_direct_debit_payments. You can also get the specific metadata and status for any single payment transaction with get_payment_details. You can list all recurring payment plans, whether active or inactive, with list_recurring_subscriptions.
Tracking Payouts and Refunds
It pulls a list of funds that GoCardless pays out to your bank account using list_merchant_payouts. For auditing, it lists all processed refunds and reversed payments using list_payment_refunds.
Other Tools
It helps you see all direct debit collections, and you can also list all payment mandates.
How GoCardless MCP Works
- 1 Subscribe to the GoCardless MCP Server on Vinkius and provide your GoCardless Access Token.
- 2 Your AI client sends a request (e.g., 'Check mandate MD12345') to the MCP server.
- 3 The server uses the required tool (e.g.,
get_mandate_status) to query GoCardless and returns the status and data directly to your AI client.
The bottom line is, your AI client acts like a dedicated financial operations analyst, querying your payment data instantly without needing to log into the GoCardless portal.
Who Is GoCardless MCP For?
Anyone whose job involves reconciling payments, verifying customer payment credentials, or managing recurring billing cycles. If you spend time clicking through payment portals to verify a mandate or check a payout status, this server cuts that time down to seconds.
Uses the server to list all direct debit payments or check if a mandate is active, confirming collection eligibility.
Retrieves a customer's payment history or subscription status via simple commands, providing real-time updates to the client.
Monitors list_merchant_payouts and list_payment_refunds to reconcile bank transfers and audit payment activity.
What Changes When You Connect
- Check mandate status instantly: Use
get_mandate_statusto confirm if a customer's authorization is active. This confirms you have the legal right to collect payment before attempting a charge. - Automate collection tracking:
list_direct_debit_paymentsshows every collection—confirmed or failed—so your agent can flag immediate payment issues without you checking a dashboard. - Reconcile funds easily:
list_merchant_payoutsprovides a clear list of money sent to your bank account, making monthly reconciliation faster and more reliable. - Understand revenue cycles:
list_recurring_subscriptionsshows both active and inactive plans, giving your agent a quick overview of predictable revenue health. - Maintain an audit trail:
list_payment_refundstracks every reversal and refund. This keeps your financial records accurate and immediately accessible to your agent. - Client oversight:
get_customer_detailsgives your agent instant access to a customer's full profile and bank account metadata when you need it.
Real-World Use Cases
Verifying Collection Eligibility
An account manager needs to charge a client, but first must confirm their mandate is valid. They ask their agent to run get_mandate_status for the client. The agent confirms the mandate is 'Active' and ready for a one-off payment, allowing the manager to proceed with confidence.
Handling Failed Payments
A billing ops specialist sees a failed payment report and needs the details. They ask the agent to list_direct_debit_payments and filter for failed status. The agent immediately provides the log and details, pinpointing the failure reason without manual portal navigation.
Monthly Financial Reconciliation
The finance analyst needs to match bank deposits to internal records. They ask the agent to list_merchant_payouts. The agent returns a list of all recent payouts, allowing the analyst to quickly reconcile the bank statement against the system records.
Checking Subscription Status
A sales team member is onboarding a new client and needs to see their payment history. They ask the agent to list_payment_customers and then list_recurring_subscriptions to give the client a full overview of their billing status.
The Tradeoffs
Treating tools as a manual checklist
Running list_payment_customers first, then manually taking the resulting IDs, and feeding them into get_mandate_status one by one. This is slow, error-prone, and requires complex prompting.
→
Don't run tools sequentially for the same goal. Instead, ask your agent to combine the steps. For example: 'List all customers who have an inactive mandate status.' The agent handles the necessary calls to list_payment_customers and then filters the results using get_mandate_status internally.
Forgetting the payment lifecycle
Only calling create_new_payment without checking the mandate first. This fails if the underlying mandate has expired or was never set up.
→
Always verify the mandate first. Before initiating payment, ask the agent to run get_mandate_status. If the status isn't 'Active,' the payment call will fail, saving you time and money.
Confusing customer data with payment data
Calling get_customer_details to get bank info, but forgetting that the payment history is tracked by get_payment_details. You miss the critical transaction record.
→
Remember that customer details are static metadata. For transactions, always use get_payment_details or list_direct_debit_payments. They track the actual money movement.
When It Fits, When It Doesn't
Use this server if your core process is managing recurring revenue, direct debit collections, or financial reconciliation. You need to answer questions like: 'Is the mandate active?' or 'What did we get paid for last month?'
Don't use this if you only need to read a static list of customer names or basic contact info. For that, a simple CRM sync tool might suffice. If your process involves complex, multi-step financial logic—like 'Find all customers with active mandates who haven't paid in 60 days'—this tool's combination of list_payment_customers, get_mandate_status, and list_direct_debit_payments is required.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by GoCardless. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 12 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Manually checking mandate status and payout records is a nightmare.
Today, verifying a customer's mandate or checking a payout requires jumping between the GoCardless dashboard, your internal CRM, and your bank's portal. You copy IDs, switch tabs, and wait for pages to load. It's slow, and you're always playing catch-up with data.
With the GoCardless MCP Server, your AI client handles the whole sequence. You ask, 'What's the status of the payment for Acme Corp?' and it runs `get_mandate_status` and `get_payment_details` to give you a single, definitive answer instantly.
GoCardless MCP Server: Control Payments and Mandates
You eliminate manual tasks like logging into the payment portal to check the current payment status or listing refunds. The agent runs `list_direct_debit_payments` and `list_payment_refunds` on demand, pulling the raw data you need.
The process moves from 'I need to log in and click through three different sections' to 'Tell your agent what you need.' You get real-time, accurate payment data without leaving your workflow.
Common Questions About GoCardless MCP
How do I get an Access Token for GoCardless? +
Log in to your GoCardless dashboard, navigate to Developers > Access Tokens, and you can generate a new token for either Sandbox or Live use there.
What is a 'Mandate' in GoCardless? +
A mandate is an authorization from your customer that allows you to collect payments from their bank account automatically in the future.
In what units should I provide the payment amount? +
The API uses minor units for currency. For example, to collect $1.00 USD (or £1.00 GBP), you must provide the value 100 (cents/pence).
Can I test this without using real money? +
Yes! Use the 'sandbox' environment by setting the 'Environment' credential and providing a Sandbox Access Token from your GoCardless account.
How do I use the `list_direct_debit_payments` tool to check payment status? +
The list_direct_debit_payments tool provides the status of collections. It returns details like 'confirmed', 'failed', or 'pending' for each payment record. You can then filter the results to see only the payments that need follow-up.
What is the difference between `get_customer_details` and `list_payment_customers`? +
Use list_payment_customers to get a full roster of all customers. Then, use get_customer_details with a specific customer ID to fetch their complete profile, bank metadata, and payment history.
Does GoCardless support listing refunds using `list_payment_refunds`? +
Yes, list_payment_refunds tracks all processed refunds and reversed payments. This tool helps you maintain an accurate financial audit trail for reconciliation.
How do I initiate a payment using the `create_new_payment` tool? +
The create_new_payment tool initiates a collection. You must provide the target customer ID, the mandate ID, and the specific amount for the payment you want to process.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Mercado Pago
Process payments, generate Pix QR codes, manage customers and refunds via Mercado Pago API.
Binance
Get real-time cryptocurrency prices, order books, candlesticks and trades from Binance exchange.
Stripe Legacy
Manage payments, customers, and account balances on Stripe via the legacy API with AI agents.
You might also like
Pinecone
Equip your AI agent to manage your Pinecone vector databases. Query embeddings, fetch metrics, manage collections, and run stats natively via chat.
SetSmart
Analyze hotel market performance with benchmarking data that compares your property against competitors and market trends.
Semrush
Grant your AI agent access to Semrush's massive SEO database to analyze competitor backlink profiles, track domain ranks, and research profitable keywords contextually.