Connector guide6-minute read26 MCP tools7 languages

Connect SumUp to Gemini CLI via MCP: Payments

Read SumUp merchant accounts, transactions, payouts, checkouts, receipts, card readers, team members and subaccounts from any AI agent. Read-only, with Bearer-token authentication.

HCBy HelpCode teamUpdated 6 min read Open-source on GitHub

No credit card · 7-day trial · Self-host alternative available

SumUp

SumUp

Manage SumUp merchant accounts, transactions, payouts, checkouts, receipts, readers, team members and subaccounts from any AI agent, read-only. Bearer-token authentication.

tools

26

Region

INTL

Category

Payments

Authentication

Bearer Token

Required env vars

SUMUP_API_KEY
Install in one click on Cloud

7-day free trial · No credit card

  • 7-day free trial
    No credit card required
  • GDPR & SOC 2 ready
    EU data residency, audit logs
  • Open-source on GitHub
    Open source · AGPL-3.0
  • Works with ChatGPT, Claude, Gemini
    Any MCP-compatible client

Summary

Read SumUp merchant accounts, transactions, payouts, checkouts, receipts, card readers, team members and subaccounts from any AI agent. Read-only, with Bearer-token authentication.

Guided setup

Connect SumUp to Gemini in 2 minutes

Start a free trial on AnythingMCP Cloud, connect SumUp in the guided setup, then add your MCP URL to Gemini. No code and no server to run.

No credit card · 7-day trial · Self-host alternative available

Try asking

Example prompts for SumUp

Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.

SumUp · live via MCP
Share
Opus 4.7

Claude is AI and can make mistakes. Please double-check responses.

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → SumUp, paste your credentials, mint an MCP API key — done. No Docker, no git clone, no local server.

SumUp + Gemini

Read SumUp merchant accounts, transactions, payouts, checkouts, receipts, card readers, team members and subaccounts from any AI agent. Read-only, with Bearer-token authentication.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

SUMUP_API_KEY

Step 1 — Get credentials

Setting up takes about 2 minutes. You need a SumUp merchant account and an API key from it.

  1. Sign in to the SumUp Dashboard at https://me.sumup.com.
  2. Open Settings → For Developers (or the Developer Portal).
  3. Generate an API key (Personal Access Token) and paste it into SUMUP_API_KEY. It is sent as a Bearer token on every call.
  4. Install the connector and run sumup_get_merchant_profile: it returns the merchant code, company name, currency and country of the account behind the key, which shows the key works.

What it reads: the merchant profile; the transaction history, newest first by default, filtered by status (such as SUCCESSFUL, CANCELLED or FAILED) or to the transactions changed since an ISO 8601 timestamp, up to 100 per page; one transaction by its id or its transaction code (such as TD6Q7P2); the payouts to your bank account between two dates (YYYY-MM-DD); the online checkouts and payment links, filtered by your own checkout reference; and the operator subaccounts under the main account.

Merchant code, receipts, team and card readers: the current SumUp API versions address an account by its merchant code, which sumup_get_merchant_profile returns; if the key reaches several accounts, sumup_list_memberships lists them and sumup_get_merchant shows one. With that code the AI also reads the transactions and payouts on the current API versions (payouts include deductions such as refunds and chargebacks), the receipt of a transaction, a single online checkout, the payment methods offered online, saved customers and their tokenized cards (last four digits only), the members, custom roles and registered persons (owners, legal representatives), and the paired card readers with their live status and the checkout sent to them. The older transaction and payout tools stay for existing setups. A 403 means the key's user lacks the permission for that account in SumUp.

Read only: all 26 tools only read. Nothing in your SumUp account is changed; refunds, new checkouts, reader payments and member changes stay in the SumUp Dashboard.

Already installed? The new tools reach a connector you installed earlier through its catalog update: open the connector in AnythingMCP and, under Catalog update available, check the list of new tools and click Apply update. Your credentials and any tools you added yourself stay as they are.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Gemini

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Gemini CLI reads MCP servers from ~/.gemini/settings.json (on Windows %USERPROFILE%\.gemini\settings.json). Add:

{
  "mcpServers": {
    "anythingmcp": {
      "httpUrl": "https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID",
      "headers": { "X-API-Key": "YOUR_MCP_API_KEY" }
    }
  }
}
  1. Create an MCP API key in AnythingMCP under MCP Servers → your server → API keys, and paste it in place of YOUR_MCP_API_KEY.
  2. Save the file and restart gemini.
  3. Run /mcp inside Gemini CLI (or gemini mcp list in your shell) — anythingmcp should show as connected.
  4. Start prompting — Gemini CLI can now call the SumUp tools.

Available tools

ToolWhat it does
sumup_get_merchant_profileRetrieve the merchant profile and account information associated with the authenticated API key, including merchant code, company name…
sumup_list_transactionsList transaction history for the authenticated merchant account with filtering by date range, payment status, and pagination
sumup_get_transactionRetrieve detailed information for a specific transaction by transaction ID or transaction code
sumup_list_payoutsRetrieve payout history and settlement reports transferred to the merchant bank account, filtered by date range
sumup_list_checkoutsList online checkouts and payment links generated for customers, with optional status and checkout reference filters
sumup_list_subaccountsRetrieve operator subaccounts configured under the main merchant account
sumup_list_membershipsList the merchant accounts (and organizations) the API key's user belongs to, with the merchant code as resource.id, the account name, the…
sumup_get_merchantGet a merchant account by merchant code: company name and legal details, business type and profile, country, default currency and locale…
sumup_list_merchant_payoutsList payouts to the merchant's bank account between two dates (current v1.0 API): payout date, amount, fee, currency, status, reference and…
sumup_list_merchant_transactionsList the merchant's transactions (current v2.1 API): card, cash and online payments, refunds and chargebacks with amount, currency, status…
sumup_get_merchant_transactionGet the full details of one transaction (current v2.1 API): amount, VAT, tip, fee, status, card and entry mode, products, payout plan and…
sumup_get_receiptGet the structured receipt of a transaction: merchant details, transaction data with products and VAT, card (EMV) and acquirer data
sumup_get_checkoutGet one online checkout by its id: amount, currency, status (PENDING, PAID, FAILED, EXPIRED), checkout reference, description, and the…
sumup_get_customerGet a saved customer (used for recurring or tokenized online payments) by the customer id you assigned: personal details such as name…
sumup_list_payment_instrumentsList the saved payment instruments of a customer: the card token, card type and masked details, mandate, creation date and whether it is…
sumup_list_payment_methodsList the payment methods available to the merchant for online checkouts (cards, Apple Pay, Google Pay, iDEAL, Bancontact and others)…
sumup_list_membersList the members (users) of a merchant account with e-mail, roles, status (accepted, pending...) and permissions
sumup_get_memberGet one member of a merchant account: user, e-mail, roles, permissions, status and timestamps
sumup_list_rolesList the custom roles of a merchant account with their names and permissions, to explain what a member's role allows
sumup_get_roleGet one custom role of a merchant account with its permissions
sumup_list_personsList the persons registered for a merchant account (legal representatives, owners and other people of the business, as collected during…
sumup_get_personGet one person registered for a merchant account
sumup_list_readersList the card readers (e.g. SumUp Solo) paired with the merchant account: id, name, status, device model and identifier
sumup_get_readerGet one paired card reader: name, status, device model and identifier, metadata and timestamps
sumup_get_reader_statusGet the live status of a card reader: online or offline, battery level, connection type, firmware and the state of the current checkout
sumup_get_reader_checkoutGet a checkout that was sent to a card reader: amount, status and the resulting transaction

FAQ

Where does Gemini CLI look for MCP servers? In ~/.gemini/settings.json for your user, or in .gemini/settings.json inside a project. gemini mcp list shows each server and whether it connects.

Next steps

Was this guide helpful?

Connect SumUp to Gemini in 2 minutes

Start a free trial on AnythingMCP Cloud, connect SumUp in the guided setup, then add your MCP URL to Gemini. No code and no server to run.

Related guides