Bring Direct Debit
to Cursor
Learn how to connect GoCardless to Cursor and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the GoCardless MCP Server?
Connect your GoCardless account to any AI agent and take full control of your Direct Debit collections and recurring billing workflows through natural conversation.
What you can do
- Customer Orchestration — List and manage bank payers programmatically, including contact info and payment history retrieval
- Mandate Management — Monitor and retrieve detailed status for customer payment authorizations to ensure collection reliability
- Payment Automation — Trigger one-off bank debit collections or manage complex recurring subscription plans directly through your agent
- Financial Visibility — Access payout creditor details and monitor system events to maintain high-fidelity oversight of your cash flow
- Operations Control — Programmatically cancel pending payments and check individual transaction states (confirmed, failed) in real-time
How it works
1. Subscribe to this server
2. Retrieve your Access Token from GoCardless (Developers > Create > Access Token)
3. Specify your environment (live or sandbox) in the configuration
4. Start managing your bank payments from Claude, Cursor, or any MCP client
No more manual payment tracking or digging through bank files. Your AI acts as your dedicated payment operations assistant.
Who is this for?
- Finance Teams — instantly check payment statuses and reconcile payouts using natural language
- Billing Managers — automate customer creation and mandate verification without leaving your workspace
- SaaS Founders — monitor subscription health and manage failed payments through automated queries
Built-in capabilities (12)
Trigger new payment
Add payer to account
Get payer info
Get authorization info
Check transaction state
List payout recipients
List payment authorizations
List bank payers
List all transactions
List all subscriptions
Get activity log
Cancel payment
Why Cursor?
Cursor's Agent mode turns GoCardless into an in-editor superpower. Ask Cursor to generate code using live data from GoCardless and it fetches, processes, and writes. all in a single agentic loop. 12 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
GoCardless in Cursor
GoCardless and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect GoCardless to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for GoCardless in Cursor
The GoCardless MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
GoCardless for Cursor
Every tool call from Cursor to the GoCardless MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my Access Token?
Log in to your GoCardless dashboard, navigate to Developers > Create > Access Token, and generate a token with the required permissions.
Can I collect a payment in a different currency?
Yes! The collect_payment tool accepts a currency parameter (e.g., GBP, EUR, USD). Ensure the customer's mandate supports the requested currency.
What happens if I try to cancel a payment that was already submitted?
If a payment has already been submitted to the banking system, the stop_pending_payment tool will return an error as the transaction can no longer be halted.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
