Sumup mcp
Use the SumUp MCP server (https://mcp.sumup.com/mcp) from Cursor, Claude Code, Codex, or any MCP-capable client. Use when the user mentions SumUp MCP, needs to wire mcp.sumup.com, or wants tool-based access to SumUp APIs.From its SKILL.md
npx -y skills add sumup/sumup-skills --skill sumup-mcpAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
- fetches URLsInstructs the agent to fetch 1 URL, including https://mcp.sumup.com/mcp.
What its file declares
Copied from the file, not written here
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.5 KB, 474 tokens by cl100k_base, as published. Nobody here has run it
SumUp MCP Server Guide
Use this skill when setup or usage of the SumUp MCP server is requested.
Canonical endpoint:
https://mcp.sumup.com/mcp
What this skill covers
- MCP server wiring in MCP-capable clients
- Auth handshake troubleshooting
- Prompt patterns for tool-driven SumUp API tasks
- Safe usage guardrails for production and sandbox contexts
Minimal Setup Checklist
- Add an MCP server entry named
sumup. - Set URL to
https://mcp.sumup.com/mcp. - Use streamable HTTP transport if the client requires explicit transport.
- Complete authentication flow when prompted by the client.
- Confirm tools are discoverable before first task prompt.
Example MCP Server Declaration
{
"servers": {
"sumup": {
"url": "https://mcp.sumup.com/mcp",
"transport": "streamable_http"
}
}
}
Adapt field names to the target client's MCP config schema.
Prompt Patterns
- "List my SumUp merchant checkouts from the last 24 hours."
- "Create a sandbox checkout for 12.34 EUR and return the checkout id."
- "Inspect this checkout id and summarize status transitions."
- "Show what data is needed to reconcile failed payments for this reference."
Common Failure Modes
Server not reachable
- Confirm exact URL and transport.
- Check client allows outbound HTTPS.
- Retry from a clean session.
Auth loop or unauthorized
- Re-run auth handshake and ensure correct account/environment.
- Confirm the token/session has required scopes.
Tools not appearing
- Refresh/reload MCP server in client.
- Confirm server alias matches the expected name in prompts/config.
Safety and Reliability Rules
- Never expose secrets or raw tokens in prompts or logs.
- Prefer sandbox for new workflows and regression tests.
- For payment-critical actions, verify final checkout status through deterministic reads.
- Record checkout ids/references for auditability and reconciliation.
Required Response Contract
When answering MCP setup/use requests, include:
- Exact server configuration snippet.
- Authentication steps and where failures usually happen.
- One verification command/prompt to confirm setup.
- A safe first task in sandbox before production usage.
What ships with it: 3 files
4.4 KB alongside SKILL.md
agents/
- openai.yaml452 B
assets/
- large-logo.png3.5 KB
- small-logo.svg416 B
Gives 0 of the 12 instructions most mcp tooling skills give in 474 tokens
Counted across 780 of the 1,136 authors here whose files we hold, read 2026-09-06
- Use Zod for input validationin 34 of 780, across 21 files
- Use stdio for local clientsin 27 of 780, across 10 files
- Restart Claude Code after configurationin 26 of 780, across 23 files
- Verify MCP server connection before using toolsin 23 of 780, across 17 files
- Define input schemas for every toolin 20 of 780, across 11 files
- Use Streamable HTTP for remote clientsin 18 of 780, across 8 files
- Pin SDK version in package.jsonin 17 of 780, across 6 files
- Keep server logic independent of transportin 16 of 780, across 6 files
- Verify SDK methods against official documentationin 15 of 780, across 5 files
- Format evaluation results as an XML filein 15 of 780, across 12 files
- Test servers using the MCP Inspectorin 15 of 780, across 14 files
- Create ten complex and independent evaluation questionsin 14 of 780, across 11 files
Said here and by no other author read
- Add an MCP server entry named sumup
- Set URL to https://mcp.sumup.com/mcp
- Complete authentication flow when prompted
- Confirm tools are discoverable before first task
- Prefer sandbox for new workflows
- Verify payment status through deterministic reads
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.