Skip to content

Connectors · Accounting & finance

SumUp MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to SumUp and the rest of your systems. It gives your agent 42 SumUp actions (21 reads, 14 writes and 7 that wait for a confirmation) and holds the SumUp credential itself, so the agent never does. It paces SumUp's limits and records every call. Connecting SumUp needs your own SumUp OAuth app and one admin sign-in.

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

claude mcp add --transport http actionlake https://connect.actionlake.com/mcp
the first call
do {  action: "sumup.checkouts.list",  intent: "check which SumUp account is connected"}# List checkouts · read · 1 upstream call
  • 42actionsin one signed file
  • 21readlook, never change
  • 14writecreate and update
  • 7wait for a yesdestructive, confirmed first

Set up

Connect SumUp in three steps.

  1. 01

    Add actionlake to Claude.

    Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.

    https://connect.actionlake.com/mcp
  2. 02

    Connect SumUp.

    OAuth 2.0, authorization code. You register your own OAuth app with SumUp, an admin signs in once, and you paste the app's client id and secret and the tokens from that sign-in; actionlake renews the access token from then on. actionlake stores what you paste write-only, sealed under your tenant's key.

    Before the first sign-in, SumUp needs an OAuth app of your own, registered in its developer portal. actionlake has no SumUp app to lend you.

    • access_tokenAccess token from one sign-in with your own OAuth app
    • refresh_tokenRefresh token from the same sign-in; the access token is renewed from it
    • client_idSumUp OAuth client id
    • client_secretSumUp OAuth client secret for the same application
    account { op: "connections.requirements", service: "sumup" }
    # free: exactly what to paste, and what is found for you
  3. 03

    Make the first call. Check before a write.

    Ask in plain words; Claude picks the action. Before anything changes, check validates the call and prices it, for free.

    do    { action: "sumup.checkouts.list" }# list checkouts · read · 1 upstream callcheck { action: "sumup.members.create", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

SumUp at a glance

Sign-in
OAuth 2.0, authorization code. You register your own OAuth app with SumUp, an admin signs in once, and you paste the app's client id and secret and the tokens from that sign-in; actionlake renews the access token from then on.
You provide
access_tokenrefresh_tokenclient_idclient_secret
Limits we pace to
100 calls a minute, per connection
API covered
SumUp REST API 1.0.0 (OpenAPI 3.1, published in the official SDK repositories)api.sumup.com
Built from
SumUp's documentation, read 23 October 2026OpenAPI spec (GitHub)developer.sumup.com
Service file
Version 1.0.0, signed (Ed25519)
Cached reads
21 of 21 reads, for up to 5 minutes; a write clears what it affects
Shared entities
4, so ask can line SumUp up with your other systems
Data
Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in SumUp.

42 actions in 13 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

  • 21readlook, never change
  • 14writecreate and update
  • 7destructivewait for a confirmation
  1. Readers

    10

    4 read · 4 write · 2 destructive

    List Readers · Retrieve a Reader · Create a Reader · Create a Reader Checkout

  2. Checkouts

    7

    2 read · 4 write · 1 destructive

    Create a checkout · List checkouts · Retrieve a checkout · Update a checkout

  3. Members

    5

    2 read · 2 write · 1 destructive

    List members · Create a member · Retrieve a member · Update a member

  4. Roles

    5

    2 read · 2 write · 1 destructive

    List roles · Create a role · Retrieve a role · Update a role

  5. Customers

    3

    1 read · 2 write · 0 destructive

    Create a customer · Retrieve a customer · Update a customer

  6. Transactions

    3

    2 read · 0 write · 1 destructive

    List transactions · Retrieve a transaction · Refund a transaction

  7. Payment instruments

    2

    1 read · 0 write · 1 destructive

    List payment instruments · Deactivate a payment instrument

  8. Persons

    2

    2 read · 0 write · 0 destructive

    List Persons · Get Person

5 more areas · 5 actions
  • Memberships 1
  • Merchants 1
  • Payment methods 1
  • Payouts 1
  • Receipts 1

Top actions

The SumUp API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 25 of SumUp's 28 action names are shared with at least one other connector, so an agent learns them once.

ActionWhat it doesEffectSame name in
sumup.members.listList membersList members.readidentity.user.list474 connectors
sumup.roles.listList rolesList roles.readidentity.role.list184 connectors
sumup.members.createCreate a memberCreate a member.writeidentity.user.create262 connectors
sumup.roles.createCreate a roleCreate a role.writeidentity.role.create105 connectors
sumup.members.deleteDelete a memberDelete a member.destructiveidentity.user.delete253 connectors
sumup.transactions.listList transactionsList transactions.readfinance.payment.list75 connectors
sumup.payouts.listList payoutsList payouts.readfinance.payout.list14 connectors
sumup.transactions.getRetrieve a transactionRetrieve a transaction.readfinance.payment.get80 connectors
sumup.customers.createCreate a customerCreate a customer.writecommerce.customer.create43 connectors
sumup.customers.getRetrieve a customerRetrieve a customer.readcommerce.customer.get45 connectors
sumup.payment_methods.listGet available payment methodsGet available payment methods.readfinance.payment_method.list29 connectors
sumup.checkouts.createCreate a checkoutCreate a checkout.writecommerce.checkout.create7 connectors

Try it

Prompts to paste into Claude.

Each one names the SumUp actions it will call, so you know what it reads and what it changes before you send it.

  1. Readread

    List the payments recorded in SumUp this month, largest first.

    callssumup.transactions.list

  2. Writewrite

    Create a member in SumUp. Show me exactly what you will send before you save it.

    callssumup.members.create

Governance for SumUp

Destructive actions wait for a yes.

7 SumUp actions are destructive. These are all of them:

  • Delete a membersumup.members.delete
  • Delete a rolesumup.roles.delete
  • Deactivate a checkoutsumup.checkouts.deactivate
  • Delete a readersumup.readers.delete
  • Refund a transactionsumup.transactions.refund
  • Terminate a Reader Checkoutsumup.readers.terminate_checkout
  • Deactivate a payment instrumentsumup.payment_instruments.deactivate

A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

dosumup.members.deleteconfirm_policy: human

Delete a member?

intent: the user asked me to delete a member

run suspended · waiting for a named person · key sumup-agent cannot confirm itself
In the console, or from an emailed signed link.
a key for this connector
account {  op: "keys.create", name: "sumup-agent",  allowed_actions: ["sumup.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "sumup.members.delete", approver: "[email protected]" },    { match: "sumup.roles.delete", approver: "[email protected]" },    { match: "sumup.checkouts.deactivate", approver: "[email protected]" }  ]}
Illustrative. Scoped to SumUp only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

What SumUp costs on actionlake.

Every SumUp action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call SumUp refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

  • 1upstream call per actionall 42 SumUp actions
  • 42actions pageeach page of a long list is one call
  • 21reads can be cacheda cache hit costs nothing
  • 100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every SumUp action.

42 actions by area: the id your agent calls, what it does, and its effect.

Readers10
  • sumup.readers.createCreate a Readerwrite
  • sumup.readers.create_checkoutCreate a Reader Checkoutwrite
  • sumup.readers.create_go_checkoutCreate a Go Reader Paymentwrite
  • sumup.readers.deleteDelete a readerdestructive
  • sumup.readers.getRetrieve a Readerread
  • sumup.readers.get_checkoutGet a Reader Checkoutread
  • sumup.readers.get_statusGet a Reader Statusread
  • sumup.readers.listList Readersread
  • sumup.readers.terminate_checkoutTerminate a Reader Checkoutdestructive
  • sumup.readers.updateUpdate a Readerwrite
Checkouts7
  • sumup.checkouts.createCreate a checkoutwrite
  • sumup.checkouts.create_apple_pay_sessionCreate an Apple Pay sessionwrite
  • sumup.checkouts.deactivateDeactivate a checkoutdestructive
  • sumup.checkouts.getRetrieve a checkoutread
  • sumup.checkouts.listList checkoutsread
  • sumup.checkouts.processProcess a checkoutwrite
  • sumup.checkouts.updateUpdate a checkoutwrite
Members5
  • sumup.members.createCreate a memberwrite
  • sumup.members.deleteDelete a memberdestructive
  • sumup.members.getRetrieve a memberread
  • sumup.members.listList membersread
  • sumup.members.updateUpdate a memberwrite
Roles5
  • sumup.roles.createCreate a rolewrite
  • sumup.roles.deleteDelete a roledestructive
  • sumup.roles.getRetrieve a roleread
  • sumup.roles.listList rolesread
  • sumup.roles.updateUpdate a rolewrite
Customers3
  • sumup.customers.createCreate a customerwrite
  • sumup.customers.getRetrieve a customerread
  • sumup.customers.updateUpdate a customerwrite
Transactions3
  • sumup.transactions.getRetrieve a transactionread
  • sumup.transactions.listList transactionsread
  • sumup.transactions.refundRefund a transactiondestructive
Payment instruments2
  • sumup.payment_instruments.deactivateDeactivate a payment instrumentdestructive
  • sumup.payment_instruments.listList payment instrumentsread
Persons2
  • sumup.persons.getGet Personread
  • sumup.persons.listList Personsread
Memberships1
  • sumup.memberships.listList membershipsread
Merchants1
  • sumup.merchants.getGet Merchantread
Payment methods1
  • sumup.payment_methods.listGet available payment methodsread
Payouts1
  • sumup.payouts.listList payoutsread
Receipts1
  • sumup.receipts.getRetrieve receipt detailsread

Questions

The SumUp MCP server, answered.

Is there a SumUp MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 42 SumUp actions across readers, checkouts, members and roles, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by SumUp.

What do I need to connect SumUp?

Your own SumUp OAuth app, registered with SumUp (its client id and client secret), and the access and refresh tokens from one admin sign-in. actionlake has no SumUp app of its own, so this is not a one-step consent. actionlake renews the access token as it expires. The free call account { op: "connections.requirements", service: "sumup" } lists exactly what to paste.

Can an AI agent delete or change things in SumUp?

Only if its key allows it, and only with an explicit confirmation. 7 SumUp actions are destructive, including delete a member, delete a role and deactivate a checkout. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

Will an AI agent use up my SumUp API limit?

actionlake paces every call to the limits in the SumUp service file: 100 calls a minute per connection. Repeated reads are answered from cache (21 SumUp actions can be), which never reaches SumUp.

What does a SumUp action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (42 SumUp actions page). Cache hits, searches, dry runs and calls SumUp refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

Which SumUp API does it cover?

The SumUp REST API 1.0.0 (OpenAPI 3.1, published in the official SDK repositories) at api.sumup.com. It is built from SumUp's documentation as read on 23 October 2026. 42 actions in 13 areas, each one in the signed service file (version 1.0.0).

Does actionlake keep my SumUp data, and where?

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your SumUp credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Which AI clients can use it?

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

Give your agent SumUp today.

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.