Skip to content

GoCardless MCP connector

The GoCardless connector brings your customers, mandates and direct debit payments into Claude, ChatGPT, Cursor and any MCP client, so your team can check, create, retry or cancel them in plain language, with every action logged.

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect GoCardless to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect GoCardless once

  1. Open Connections, choose Add connection, and pick GoCardless.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a GoCardless API key. One person generates a token in GoCardless and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

gocardless
GoCardless
Airwallex
Cashfree Payments
ChargeDesk
Chimoney
Circle
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

GoCardless MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

GoCardless MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

GoCardless MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect GoCardless to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with GoCardless through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Finance

    Chase failed direct debits the same morning

    Ask which GoCardless payments failed overnight and why, then retry the ones whose mandate is still active before the customer notices anything is wrong.

  • Billing

    Set up a new payer end to end

    Create the customer in GoCardless, attach their mandate and schedule the first payment straight from the signed order form, without opening a second tab.

  • Support

    Answer a charge question in one look

    Pull up a customer's GoCardless payments and mandate status while they are still on the phone, and cancel a payment that should not go out.

  • Customer success

    Reinstate a mandate for a returning customer

    When a customer comes back, reinstate their existing GoCardless mandate instead of asking them to enter their bank details all over again.

  • Operations

    Keep payer details current after a change

    Update a customer's email, address or company name in GoCardless as soon as they tell you, so payment notifications reach the right place.

  • Revenue operations

    Resend notifications your billing system missed

    If your invoicing system missed a GoCardless notification, ask which webhooks failed to deliver and send them again so both records line up.

Try asking

  • “Show me all failed payments from this week.”
  • “List customers with pending mandates.”
  • “Which webhooks failed to deliver yesterday.”

See all 137 GoCardless tools below

Compare

Elaichi vs Zapier MCP vs Composio for GoCardless

All three can connect GoCardless to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for GoCardless, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over GoCardless tools Allow or restrict single GoCardless tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per GoCardless call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price $15 per user per month. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

AI tools

GoCardless tools for your AI agents

137 tools are ready to call through Elaichi's MCP endpoint the moment you connect GoCardless, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting GoCardless gets you

6 screens from the product, each doing one job for your GoCardless account.

The agent

Ask GoCardless questions in plain language.

Get answers pulled straight from live customer and payment records.

  • customers
  • payments
  • webhooks
  • mandates

Ask Elaichi to work across your apps.

Show me all failed payments from this week.

List customers with pending mandates.

Which webhooks failed to deliver yesterday.

Also runs in Claude, ChatGPT or Cursor

MCP clients

One GoCardless endpoint, every MCP client.

Connect Claude, ChatGPT or Cursor through a single governed endpoint, no API keys shared.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

Tool catalog

137 GoCardless tools, ready to call.

Every customer, payment and webhook method cataloged, no custom code required.

  • Create a GoCardless customer
  • List all GoCardless customers
  • Get single GoCardless customer by ID
  • Update a GoCardless customer by ID
ElaichiTools
Tool Action Description
Create a GoCardless customer Create Create a GoCardless customer with the contact details used for Direct Debit mandates. Returns: id, created_at, email, given_name, family_name, address_line1, address_line2, city, postal_code, country_code, metadata. Requires given_name and family_name; email is required in most cases. Legacy endpoint restricted to GoCardless Pro/Enterprise accounts.
List all GoCardless customers List List GoCardless customers, cursor-paginated. Returns: id, created_at, email, given_name, family_name, address_line1, address_line2, address_line3, city, region, postal_code, country_code, language, phone_number, swedish_identity_number, danish_identity_number, metadata. Filterable by created_at date range, currency, and action_required; sortable via sort_field and sort_direction.
Get single GoCardless customer by ID Get Get a single GoCardless customer by id. Returns the full customer object including id, created_at, email, given_name, family_name, address fields, language, phone_number, and metadata. Required: id.
Update a GoCardless customer by ID Update Update a GoCardless customer's contact details by id. Returns the updated customer object including id, created_at, email, given_name, family_name, address fields, language, and metadata. Required: id.
Delete a GoCardless customer by ID Delete Delete a GoCardless customer by id. This action cannot be reversed. Returns an empty 204 response on success.

Toolboxes

Every team gets its own GoCardless toolbox.

Finance, support and engineering each work from a toolbox scoped to their role.

  • Finance
  • Sales
  • Support
  • Engineering
ElaichiToolboxes
Name Source template Tools Created

Finance toolbox

GoCardless · payments and payouts

GoCardless starter 18 Mar 4, 2026

Sales toolbox

GoCardless · customers and mandates

— 9 Mar 2, 2026

Support toolbox

GoCardless · customer records and disputes

— 24 Feb 27, 2026

Engineering toolbox

GoCardless · webhook configuration and retries

GoCardless starter 6 Feb 19, 2026

Revenue Operations toolbox

GoCardless · payment retries and reconciliation

— 31 Jan 30, 2026

Compliance toolbox

GoCardless · mandates and dispute records

— 12 Jan 22, 2026

Shared connections

Delegate GoCardless access without sharing credentials.

See who connected each account and how many teams and members use it.

  • Finance EMEA
  • Sales
  • Support
  • Engineering
ElaichiConnections
Connection Scope Status Access
GO

GoCardless (Finance EMEA)

Connected by Emily Carter

Personal • Active 1 team · 6 members
GO

GoCardless (Sales)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
GO

GoCardless (Support)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
GO

GoCardless (Engineering)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
GO

GoCardless (Revenue Operations)

Connected by Ryan Hayes

Personal • Active Not shared
GO

GoCardless (Compliance)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Audit log

Every GoCardless call, logged and traceable.

Answer who did what, when, across every payment, mandate and webhook action.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

emily.carter@northwind.io

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

jake.morgan@northwind.io

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

megan.brooks@northwind.io

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

tyler.reed@northwind.io

GoCardless Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

ryan.hayes@northwind.io

GoCardless Customers Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

ashley.parker@northwind.io

GoCardless Customers List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

GoCardless runs, a person approves the finish.

A schedule fetches payment records, groups them, drafts a digest, then posts back after approval.

GoCardless digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch customers

    GoCardless

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    GoCardless

    Queued

Collections and dashboards

GoCardless health, computed on a schedule.

Four metrics and a 14 day chart track payments created, broken down by team.

GoCardless health

Refreshed 4 minutes ago · every 15 minutes · from the customers collection

Live

Customers

1,284 ↓ 12%

Payments

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Customers created

Last 14 days

By team

Share of activity

Finance EMEA 34%

Sales 27%

Support 21%

Engineering 18%

FAQ

Frequently asked questions

How do I connect GoCardless to Claude?

It takes two steps. In Elaichi, choose GoCardless and paste an access token from your GoCardless dashboard, which is the whole sign-in step, with no OAuth application to register and no client ID or secret to generate. Then in Claude, open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude asks you to sign in to Elaichi and GoCardless is ready to use.

Does GoCardless work with ChatGPT and Cursor as well as Claude?

Yes. Once GoCardless is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect GoCardless once and every client you use picks it up.

What can an AI agent actually do with my GoCardless data?

It can look up a customer, check whether their mandate is active, canceled or pending, and list their payments along with any that failed. It can also create a customer, mandate or payment in GoCardless, retry or cancel a payment, cancel or reinstate a mandate, update creditor details, and resend webhooks that did not get through. Because GoCardless has a large set of actions, short concrete asks such as "failed payments this week" work better than long sentences.

Does connecting GoCardless give the AI access to my whole account?

The AI can only reach what the GoCardless account behind the connection is allowed to reach, and nothing beyond it. Elaichi can then narrow that further, for example to looking up customers and payments without creating or canceling anything. It can never widen access past what GoCardless itself allows.

Can my team share one GoCardless connection?

Yes. One person connects GoCardless in Elaichi and shares it with a team, and nobody else ever handles the GoCardless access token. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who retried a payment or canceled a mandate, not the person who set up the connection.

Can I stop an agent from deleting or changing things in GoCardless?

Yes. Restrictions in Elaichi work per action, so you can block deleting customers, canceling mandates or canceling payments in GoCardless while still allowing lookups and retries. A blocked action is never shown to Claude, ChatGPT or any other client at all, so no prompt, however worded, can reach it.

What happens to a GoCardless connection when someone leaves?

Offboarding that person in Elaichi ends their access to GoCardless at once, across every client they used. A shared GoCardless connection keeps working for everyone else on the team. If you want to remove GoCardless entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.

Does the GoCardless MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. GoCardless is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for GoCardless?

Yes. Both let Claude, ChatGPT or Cursor use GoCardless. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every GoCardless call.

How is Elaichi different from Composio for GoCardless?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to GoCardless: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put GoCardless in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.