Sumup mcp

Skill sumup/sumup-skills/skills/sumup-mcp

Agent Skills for teaching agents how to build with SumUp.

Install

npx -y skills add sumup/sumup-skills --skill sumup-mcp

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing 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.

What its author says it does

Copied from the file, not written here

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.

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, 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.