Link CLI MCP Server
Online purchases by your AI agent from your Link wallet: it requests a specific purchase, you approve it, and it gets a one-time card for checkout.Read full description
stripeLABSCO SUMMARY
Two ways in: the hosted endpoint over OAuth, or a local CLI with an API key.
Because it runs as a Worker rather than a local process, connecting is a URL and an authorization, and the session pinning means a conversation keeps its state across requests. The one thing to get right before you start is the credential: this is an OAuth resource server, so it wants a token issued for the MCP resource, and the SumUp API key you already have will be rejected there. That key belongs to the other route, SumUp's local CLI (npx -y @sumup/mcp with SUMUP_API_KEY, Node.js 22 or later).
What it is
SumUp's Model Context Protocol server, running as a Cloudflare Worker at mcp.sumup.com. It is the transport between an MCP client and SumUp's APIs, so there is nothing to host. SumUp also publishes a local CLI, @sumup/mcp, for clients configured with an API key.
What you get
- A hosted endpoint your client connects to directly: /mcp speaks Streamable HTTP, and /sse remains for clients still on the legacy transport.
- Session state that survives across requests — both routes are pinned to a Durable Object within the same Worker deployment, so a multi-step conversation does not lose its place.
- Authorization discovery without manual configuration: the worker publishes protected resource metadata pointing at SumUp's authorization server, so an OAuth-capable client finds where to authenticate on its own.
- A route in for clients that do not speak the transport natively — mcp-remote bridges to the same endpoint with the token passed as a header.
Requirements
An OAuth access token issued for the MCP resource — specifically a JWT issued by SumUp's authorization host and valid for the worker's resource URL, sent as Authorization: Bearer. A SumUp API key in the sup_sk_ form is not accepted here, which is the mistake worth avoiding up front. OAuth-capable clients discover the authorization server from the endpoint's metadata rather than needing a token configured by hand. The local CLI is the one that takes the sup_sk_ key: it reads SUMUP_API_KEY and needs Node.js 22 or later.
Setup effort
One command plus a key — npx -y @sumup/mcp, then supply credentials
USE CASES
01
Working with a SumUp account without opening the dashboard
Connect the client once and ask in plain language rather than assembling API requests.
02
Connecting a client that has no MCP support of its own
Bridge to the hosted endpoint and pass the access token as a header.
03
Avoiding another local process to keep running
The server is hosted, so there is nothing to install, update or restart.
BEFORE YOU INSTALL
What to know first
Requires
- Node.js 22 or later (local CLI)
- SUMUP_API_KEY in your environment (local CLI)
Where it runs
Of the 3 documented clients, 2 run the server on your machine and 1 connects to a hosted endpoint.
INSTALLATION
Connect your client
Server setup
npx
TERMINAL
npx -y @sumup/mcpHosted endpoint
ENDPOINT URL
https://mcp.sumup.com/mcpAdd this hosted endpoint to your MCP client using the credentials listed under Requirements.
MCP Clients
Any MCP client — mcp-remote
ANY MCP CLIENT — MCP-REMOTE · JSON
{
"mcpServers": {
"sumup": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.sumup.com/mcp",
"--header",
"Authorization: Bearer <YOUR_ACCESS_TOKEN>"
]
}
}
}Cursor, Claude Desktop
JSON
{
"mcpServers": {
"sumup": {
"command": "npx",
"args": [
"-y",
"@sumup/mcp"
],
"env": {
"SUMUP_API_KEY": "<YOUR_SUMUP_API_KEY>"
}
}
}
}This runs SumUp's local MCP CLI, which needs Node.js 22 or later and a SumUp API key (sup_sk_…) in SUMUP_API_KEY. That key works only here — the hosted endpoint at mcp.sumup.com rejects it and wants an OAuth sign-in instead.
