Back to MCP Servers

GoCardless MCP Server

Official GoCardless MCP server for bank payments. Natural language integration guidance and read-only queries over customers, mandates, payments, subscriptions and payouts.

Payments by GoCardless OAuth2 active
Overview

GoCardless MCP is the official Model Context Protocol server from GoCardless, the bank payments platform specialising in direct debit and account-to-account payments. Announced in February 2026, it lets developers and merchants interact with the GoCardless platform using natural language through any MCP-compatible LLM client (Claude, Cursor, VS Code Copilot, Windsurf, Gemini CLI, ChatGPT, Codex).

The server has two main roles. First, it acts as an integration assistant: it gives the LLM structured, up-to-date knowledge of the GoCardless API, including endpoint documentation, webhook patterns, payment page implementation guidance and code samples across all officially supported languages. Second, it provides read-only access to account data so users can query the status of payments, customers, mandates, subscriptions, payouts and events in plain English. Sensitive fields such as emails, phone numbers and bank details are automatically masked before being returned to the LLM.

Authentication is handled via an OAuth browser sign-in flow, so API keys never need to be shared with the LLM. Users choose between the Sandbox and Live environments at login. Because the server is provider-hosted at https://mcp.gocardless.com, there is nothing to install or run locally, the MCP client simply connects over HTTP.

Tools

Tool Description
Integration guidance (resource) Provides the LLM with API endpoint documentation, integration patterns, webhook configuration guidance and code samples in supported languages so it can produce context-aware GoCardless code.
Payment queries (read-only) Look up payment status and details, including links to the related mandate and subscription.
Customer queries (read-only) List and retrieve customers in the connected GoCardless account. Sensitive PII is masked in the response.
Mandate queries (read-only) List and retrieve direct debit mandates, including customer linkage.
Subscription queries (read-only) List subscriptions and inspect their status, linked mandate and customer.
Payout queries (read-only) Review payouts made to your connected bank account and the payments included in them.
Event queries (read-only) Examine recent events on the account to help diagnose payment, mandate and subscription state changes.
Setup Guide

GoCardless hosts the MCP server at https://mcp.gocardless.com. There is no package to install. Authentication is performed in the browser via OAuth when you first connect, and you select either Sandbox or Live during sign-in.

Cursor (~/.cursor/mcp.json or .cursor/mcp.json):

{
  "mcpServers": {
    "GoCardless": {
      "url": "https://mcp.gocardless.com"
    }
  }
}

Claude Code (CLI):

claude mcp add --transport http GoCardless https://mcp.gocardless.com

Claude Desktop: requires a Pro, Max, Team or Enterprise plan. Add the server through Settings > Connectors > Add custom connector and paste https://mcp.gocardless.com.

VS Code (GitHub Copilot):

code --add-mcp '{"type":"http","name":"GoCardless","url":"https://mcp.gocardless.com"}'

Windsurf:

{
  "mcpServers": {
    "GoCardless": {
      "serverUrl": "https://mcp.gocardless.com"
    }
  }
}

Gemini CLI:

gemini mcp add --transport=http GoCardless https://mcp.gocardless.com

Prerequisites: a GoCardless account with access to Sandbox or Live. No API tokens need to be pasted into the client, the OAuth flow handles credentials.

Use Cases
  • Generate ready-to-use integration code for recurring payments, hosted payment pages or custom payment flows in your preferred language
  • Debug failed transactions by asking the LLM to look up payment status, related mandates and recent events
  • Answer operational questions like "How many payments are overdue today?" or "Which subscriptions are pending submission?" without writing SQL or hitting the dashboard
  • Get guidance on webhook configuration, retry behaviour and idempotency when building or hardening a GoCardless integration
  • Audit customer, mandate, subscription and payout records from inside an AI coding environment while sensitive PII is automatically masked
Example Prompts
  • "Show me all payments that failed in the last 7 days and the mandates they belong to."
  • "Generate a Node.js example for creating a customer, mandate and subscription using the GoCardless API."
  • "How do I verify webhook signatures from GoCardless? Give me a Python snippet."
  • "List my most recent 5 payouts and tell me which payments are included in the latest one."
  • "Walk me through implementing a hosted billing request flow for a UK customer paying monthly."
Pros
  • Officially built and hosted by GoCardless, no third-party intermediary handling payment credentials
  • OAuth browser sign-in means API keys never leave your account or get pasted into chat
  • Combines API documentation, code samples and live account data in a single endpoint
  • Sensitive customer data (emails, phone numbers, bank details) is automatically masked before reaching the LLM
Limitations
  • Account data access is read-only, you cannot create or cancel payments, mandates or subscriptions through the MCP
  • Claude Desktop integration requires a paid plan (Pro, Max, Team or Enterprise)
  • Public tool list and schema are not exhaustively documented, capabilities are described at a high level rather than as a fixed function reference
Alternatives
  • Stripe MCP server for card and subscription billing workflows
  • PayPal MCP server for PayPal payment and invoice operations
  • jmceleney/gocardless-mcp, a community-built MCP server that exposes write tools (create customer, create payment) against the GoCardless REST API using a personal access token