GoCardless

GoCardless API guidance plus live merchant access: payments, customers, mandates, payouts.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the GoCardless connector does

The GoCardless MCP server connects your GoCardless merchant account to Claude, ChatGPT or any MCP-compatible agent. It does two jobs: it teaches a model the GoCardless API so it can write integration code, and it reads and acts on your live account — payments, customers, mandates, payouts, refunds. GoCardless documents money-moving write actions here, not read-only lookups alone.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

GoCardless tools (2)

  • integrate_with_gocardless
  • read_gocardless_resource

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • The "Read only" label understates the server. GoCardless documents creating payments, retrying and cancelling payments, issuing refunds, cancelling mandates, creating subscriptions and creating payment links. Read-only is a permission set you may choose, not the server's ceiling.
  • The vendor documentation contradicts itself. One section of the GoCardless MCP page describes write access; another on the same page says queries are strictly read-only and nothing can be created, cancelled or modified. Both were live on 2026-08-19.
  • No tool schemas are published. GoCardless documents capabilities in prose and example prompts, with no tool table, no input schema and no response fields. The mapping from the directory's two tool names to the two documented capabilities is our inference.
  • No scopes are advertised. Neither the RFC 9728 descriptor nor the RFC 8414 document carries scopes_supported, so permissions are not machine-discoverable before sign-in.
  • We could not verify tool behaviour ourselves. The endpoint is gated, so no schemas and no safety annotations were readable. Every capability claim here is GoCardless's documentation.
  • Masking is partial, by design. Bank details are never shared and contact and identity fields are masked, but customer records, mandates, payment history and event trails describing identifiable payers remain readable.
  • Write caps exist but only one is published. GoCardless states some write tools cap how much can change at once, giving a maximum of 25 payments created at once as its only example. Other caps are undocumented.
  • Confirmation is a client-side prompt, not a server guarantee you control. Money-moving actions show a preview and wait for approval; GoCardless states plainly that you are responsible for actions taken via your AI tool, and urges extreme caution with autonomous agents.
  • Environment changes need a reconnect. There is no in-session switch between Sandbox and Live, and reconnecting also re-selects permissions.
  • Prompts are unconfirmed. Anthropic's snapshot lists no prompt names, and the gated endpoint blocked our own check.
  • Client plan gates access. A Pro, Max, Team or Enterprise plan is needed for Claude Desktop, and GoCardless notes free AI tiers typically do not support connectors.

Frequently asked questions

Can the GoCardless MCP server move money or create payments?

Yes. GoCardless documents write capabilities including creating payments, retrying and cancelling payments, issuing refunds, cancelling mandates, creating subscriptions and creating payment links. Money-moving actions display a preview and wait for your explicit confirmation before running. You choose which permissions to grant during sign-in, and read-only is one of the options offered.

Is the GoCardless MCP server just documentation help, or does it reach my real account?

Both, and the account access is real. GoCardless describes two capabilities: integration guidance covering endpoints, webhooks and code samples, and live account management. Once signed in, an agent can look up payments, customers, mandates, subscriptions, payouts, refunds and events on the environment you authorised, and take documented write actions on them.

What does read_gocardless_resource actually read?

GoCardless does not publish a per-tool schema, so the exact surface is undocumented. Its documentation enumerates the resource families an agent reaches: payments, customers, mandates, subscriptions, payouts, refunds and events. In GoCardless vocabulary those are API resources on your merchant account, not documentation pages, so the tool reads live merchant data rather than reference material.

Does the GoCardless MCP connector use Sandbox or Live?

You choose during sign-in. GoCardless runs two environments, Live for real payments and Sandbox for testing, and the connection journey asks which one you want. There is no in-session switch: changing environment means disconnecting and reconnecting. GoCardless recommends testing write actions in a free Sandbox account before running them against Live.

Does the GoCardless MCP server expose my customers' bank details?

No. GoCardless states that bank account details are never shared with the AI tool, and that customer email addresses, phone numbers, post codes and identity numbers are masked before the model sees them. Customer records, mandates and payment history remain readable, so the connector still reaches data about identifiable payers even with masking applied.

Do I need a GoCardless account to use the MCP server?

Yes. The endpoint answered our anonymous probe with HTTP 401 and an OAuth challenge on 2026-08-19, so nothing is reachable without signing in. A free Sandbox account is enough for the integration-guidance side and for testing write actions. GoCardless also notes that free AI provider tiers typically do not support connectors.

Sources

  • GoCardless MCP developer documentation — https://developer.gocardless.com/developer-tools/mcp/ (fetched 2026-08-19 as Markdown via https://developer.gocardless.com/developer-tools/mcp.md, the path named in GoCardless's own machine index) · retrieved 2026-08-19
  • GoCardless support guide, "Use AI to manage your account", source of the capability table, masking statement, permission model and write caps — https://support.gocardless.com/hc/articles/26830050176028 (fetched 2026-08-19) · retrieved 2026-08-19
  • GoCardless developer docs machine index — https://developer.gocardless.com/llms.txt (fetched 2026-08-19) · retrieved 2026-08-19
  • developer.gocardless.com/robots.txt allows all paths, names one sitemap, and carries no content-signal directive (fetched 2026-08-19) · retrieved 2026-08-19
  • GoCardless Sandbox sign-up, confirming self-serve free access — https://manage-sandbox.gocardless.com/sign-up (HTTP 200, fetched 2026-08-19) · retrieved 2026-08-19
  • Live anonymous probe — 2026-08-19: an initialize POST to https://mcp.gocardless.com returns HTTP 401 with a www-authenticate Bearer challenge naming a resource_metadata URL. No authentication was attempted and no tool was called. · retrieved 2026-08-19
  • Live RFC 9728 protected-resource descriptor — https://mcp.gocardless.com/.well-known/oauth-protected-resource (HTTP 200, 97 bytes, fetched 2026-08-19; declares authorization_servers and no scopes_supported) · retrieved 2026-08-19
  • Live RFC 8414 authorization-server metadata — https://mcp.gocardless.com/.well-known/oauth-authorization-server (HTTP 200, 394 bytes, fetched 2026-08-19; PKCE S256, dynamic registration, no scopes_supported) · retrieved 2026-08-19
  • Anthropic connector directory — https://claude.ai/directory/d242c454-3a8c-4271-8a8a-e334b111c7c5 (snapshot 2026-08-16; two tools, permissions label Read only, no prompts listed) · retrieved 2026-08-16

More Finance connectors

  • Affinity

    Search your CRM, prep for meetings and update deal records from your AI assistant.

  • Aiera

    Pull earnings-call transcripts, event calendars, SEC filings and company publications into your AI assistant.

  • Airwallex Developer

    Search Airwallex documentation and exercise a sandbox account from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put GoCardless to work.

Connect GoCardless once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio
Call (650) 285-1019Our AI receptionist answers.