gocardless
Server Details
Query GoCardless: customers, mandates, payments, subscriptions, payouts, refunds, events.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
15 toolsgocardless_create_customerCreate customerDestructiveInspect
Creates a customer record in GoCardless. Contact details only — no bank account, MOVES NO MONEY. GoCardless: POST /customers (body wrapped as { customers: {...} }).
| Name | Required | Description | Default |
|---|---|---|---|
| city | No | City. | |
| No | Customer email. | ||
| language | No | ISO 639-1 language code for notifications, e.g. en, fr. | |
| metadata | No | Up to 3 key-value string pairs of your own metadata. | |
| given_name | No | First name. | |
| family_name | No | Last name. | |
| postal_code | No | Postal / ZIP code. | |
| company_name | No | Company name (use instead of given/family name for businesses). | |
| country_code | No | ISO 3166-1 alpha-2 country code, e.g. GB, US, DE. | |
| phone_number | No | Phone number in E.164 format. | |
| address_line1 | No | Address line 1. |
gocardless_get_customerGet customerRead-onlyInspect
Retrieve a single customer by id. Read-only. GoCardless: GET /customers/{id}.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Customer id, e.g. CU123. |
gocardless_get_mandateGet mandateRead-onlyInspect
Retrieve a single mandate by id. Read-only. GoCardless: GET /mandates/{id}.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Mandate id, e.g. MD123. |
gocardless_get_paymentGet paymentRead-onlyInspect
Retrieve a single payment by id. Read-only. GoCardless: GET /payments/{id}.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Payment id, e.g. PM123. |
gocardless_get_payoutGet payoutRead-onlyInspect
Retrieve a single payout by id. Read-only. GoCardless: GET /payouts/{id}.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Payout id, e.g. PO123. |
gocardless_get_subscriptionGet subscriptionRead-onlyInspect
Retrieve a single subscription by id. Read-only. GoCardless: GET /subscriptions/{id}.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Subscription id, e.g. SB123. |
gocardless_list_creditorsList creditorsRead-onlyInspect
List creditors (your merchant accounts that receive payouts). Read-only. GoCardless: GET /creditors.
| Name | Required | Description | Default |
|---|---|---|---|
| after | No | Cursor: return records after this id (from meta.cursors.after). | |
| limit | No | Max records per page (1–500). Default 50. | |
| before | No | Cursor: return records before this id (from meta.cursors.before). |
gocardless_list_customer_bank_accountsList customer bank accountsRead-onlyInspect
List customer bank accounts (account details are masked by GoCardless). Read-only. GoCardless: GET /customer_bank_accounts.
| Name | Required | Description | Default |
|---|---|---|---|
| after | No | Cursor: return records after this id (from meta.cursors.after). | |
| limit | No | Max records per page (1–500). Default 50. | |
| before | No | Cursor: return records before this id (from meta.cursors.before). | |
| customer | No | Filter by customer id, e.g. CU123. |
gocardless_list_customersList customersRead-onlyInspect
List customers (payers) with cursor pagination. Read-only observability. GoCardless: GET /customers.
| Name | Required | Description | Default |
|---|---|---|---|
| after | No | Cursor: return records after this id (from meta.cursors.after). | |
| limit | No | Max records per page (1–500). Default 50. | |
| before | No | Cursor: return records before this id (from meta.cursors.before). | |
| created_at_gt | No | Only customers created after this ISO 8601 timestamp (maps to created_at[gt]). | |
| created_at_lt | No | Only customers created before this ISO 8601 timestamp (maps to created_at[lt]). |
gocardless_list_eventsList eventsRead-onlyInspect
List events — the audit / webhook event log (payment confirmed, mandate cancelled, etc.). Read-only. GoCardless: GET /events.
| Name | Required | Description | Default |
|---|---|---|---|
| after | No | Cursor: return records after this id (from meta.cursors.after). | |
| limit | No | Max records per page (1–500). Default 50. | |
| action | No | Filter by action, e.g. confirmed, failed, cancelled, created. | |
| before | No | Cursor: return records before this id (from meta.cursors.before). | |
| mandate | No | Filter by mandate id. | |
| payment | No | Filter by payment id. | |
| resource_type | No | Filter by resource type, e.g. payments, mandates, payouts, subscriptions, refunds. |
gocardless_list_mandatesList mandatesRead-onlyInspect
List mandates (a mandate = a customer's authorization to debit their bank account). Read-only. GoCardless: GET /mandates.
| Name | Required | Description | Default |
|---|---|---|---|
| after | No | Cursor: return records after this id (from meta.cursors.after). | |
| limit | No | Max records per page (1–500). Default 50. | |
| before | No | Cursor: return records before this id (from meta.cursors.before). | |
| status | No | Filter by status, e.g. pending_customer_approval, active, cancelled, expired, failed. | |
| customer | No | Filter by customer id. |
gocardless_list_paymentsList paymentsRead-onlyInspect
List payments (READ ONLY — this server never creates or modifies payments). GoCardless: GET /payments.
| Name | Required | Description | Default |
|---|---|---|---|
| after | No | Cursor: return records after this id (from meta.cursors.after). | |
| limit | No | Max records per page (1–500). Default 50. | |
| before | No | Cursor: return records before this id (from meta.cursors.before). | |
| status | No | Filter by status, e.g. pending_submission, submitted, confirmed, paid_out, failed, cancelled. | |
| mandate | No | Filter by mandate id. | |
| customer | No | Filter by customer id. | |
| subscription | No | Filter by subscription id. |
gocardless_list_payoutsList payoutsRead-onlyInspect
List payouts (funds GoCardless sends to your bank account). Read-only. GoCardless: GET /payouts.
| Name | Required | Description | Default |
|---|---|---|---|
| after | No | Cursor: return records after this id (from meta.cursors.after). | |
| limit | No | Max records per page (1–500). Default 50. | |
| before | No | Cursor: return records before this id (from meta.cursors.before). | |
| status | No | Filter by status, e.g. pending, paid. | |
| creditor | No | Filter by creditor (merchant account) id. |
gocardless_list_refundsList refundsRead-onlyInspect
List refunds (READ ONLY — this server never creates refunds). GoCardless: GET /refunds.
| Name | Required | Description | Default |
|---|---|---|---|
| after | No | Cursor: return records after this id (from meta.cursors.after). | |
| limit | No | Max records per page (1–500). Default 50. | |
| before | No | Cursor: return records before this id (from meta.cursors.before). | |
| mandate | No | Filter by mandate id. | |
| payment | No | Filter by payment id. |
gocardless_list_subscriptionsList subscriptionsRead-onlyInspect
List subscriptions (recurring payment schedules). Read-only. GoCardless: GET /subscriptions.
| Name | Required | Description | Default |
|---|---|---|---|
| after | No | Cursor: return records after this id (from meta.cursors.after). | |
| limit | No | Max records per page (1–500). Default 50. | |
| before | No | Cursor: return records before this id (from meta.cursors.before). | |
| mandate | No | Filter by mandate id. | |
| customer | No | Filter by customer id. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!