SumUp MCP server
SumUp in any MCP client, through Memtro: SumUp does not publish this server. Memtro's SumUp connector reads SumUp through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
SumUp card payments: transactions with status, amount, payment type and card brand, payouts and fees over a period, the merchant profile, card readers and team members. Can refund a transaction, create or deactivate an online checkout, send an amount to a card reader or stop it, save or edit a customer, rename or remove a reader, and invite or remove a team member, each only when asked.
Reads
sumup_transactionsSumUp card transactions: code, time, type (payment, refund, chargeback), status, amount and currency, refunded amount, payment type, card brand…sumup_payoutsSumUp payouts to the merchant's bank and the deductions against them, for a date range: date, type, amount, fee, currency, status…sumup_merchantThe SumUp merchant profile: customer-facing business name, business type, country, default currency and locale, website, whether it is a sandbox…sumup_readersThe merchant's SumUp card readers: id (needed to send a payment to one), name, pairing status, model and serial, created and updated.sumup_membersTeam members of the SumUp merchant account: member id (needed to remove one), email, nickname, roles, status (accepted, pending, expired…
Acts, when you ask
These change something in SumUp. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
sumup_refund_transactionRefund a SumUp card transaction back to the cardholder, in full or in part.sumup_create_checkoutCreate a SumUp online checkout for an amount, to be paid later by card.sumup_deactivate_checkoutDeactivate an unpaid SumUp checkout so it, and any payment page link for it, can no longer be paid.sumup_start_reader_checkoutSend an amount to a paired SumUp card reader so the customer in front of it can tap or insert a card.sumup_terminate_reader_checkoutStop the payment currently waiting on a SumUp card reader (waiting for card or PIN).sumup_create_customerSave a customer record in SumUp under an id you choose (for linking checkouts and repeat payments).sumup_update_customerOverwrite fields of a saved SumUp customer's personal details.sumup_rename_readerRename a SumUp card reader.sumup_delete_readerRemove a paired card reader from the SumUp account.sumup_invite_memberInvite a person to the SumUp merchant account with the named roles.sumup_remove_memberRemove a team member from the SumUp merchant account.
Connect it
First connect SumUp on Dashboard → Connections, then add Memtro to your client once. The SumUp tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared SumUp connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › What did we take on Saturday?
- › Any refunds this week?
- › How much did SumUp take in fees on last month's payouts?
- › Were there any chargebacks this month?
- › Refund £4.50 of this morning's 9:14 transaction, the oat milk was missing.
Questions
- Is this an official SumUp MCP server?
- No. It is Memtro's MCP server with Memtro's SumUp connector behind it: the connector reads SumUp through its API with the credentials you connect on Dashboard → Connections, and SumUp publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in SumUp?
- Only when you ask, and only what it has been granted: refund a card transaction, in full or in part (moves money back to the cardholder, permanent); create an online checkout for an amount, optionally with a SumUp payment page link; deactivate an unpaid checkout so it can no longer be paid (permanent); send an amount to a card reader for the customer to pay (takes a payment if they do); stop the payment showing on a card reader; save a customer record; edit a saved customer's details; rename a card reader; remove a card reader from the account (permanent until it is paired again); invite a person to the SumUp account with named roles (emails them); remove a team member from the SumUp account. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.