sumup/sumup-skills / skills/sumup-mcp
sumup-mcp
UnverifiedConfigure, authenticate, troubleshoot, or use the SumUp MCP server at mcp.sumup.com. Use for MCP client setup, missing tools, OAuth connection failures, merchant account queries, and SumUp documentation resources.
Use SumUp MCP
First determine whether the request is to use available tools or to configure a connection. If SumUp tools are already available, use them for the requested task; do not reinstall the plugin, add a duplicate server, or repeat setup instructions.
Connection choices
| Connection | Authentication and requirements |
|---|---|
Hosted https://mcp.sumup.com/mcp | Streamable HTTP with OAuth authorization through the client. A SumUp secret API key is not a valid Bearer token for this endpoint. |
Local @sumup/mcp process | stdio with SUMUP_API_KEY; Node.js 22 or later. Use when API-key authentication or a stdio-only client is required. |
For a new setup, prefer the packaged integration when the client supports it. Use its bundled connection if already installed. For direct configuration, read client setup and only the section for the user's client and transport. Merge configuration with existing servers instead of replacing it.
Complete OAuth in the client's browser flow. Verify a new connection with a read-only request such as: "Use the SumUp MCP tools to show my merchant profile." Keep secret keys and tokens in private client configuration or the process environment.
Documentation resources
When the client supports MCP resources, read the documentation index and OpenAPI specification. Otherwise fetch those URLs directly; the API index links to endpoint pages and SDK samples. Use the installed tools and current contract rather than guessing tool names or parameters.
Connection failures
- Unreachable server: check the exact endpoint, transport, and outbound HTTPS access.
- Unauthorized or repeated login: for hosted MCP, remove any manually configured API-key Bearer header and repeat OAuth; for local stdio, check the private
SUMUP_API_KEYenvironment. Confirm the intended merchant account and required permissions. - Missing tools: inspect the active connection and client-supported capabilities, refresh it if needed, and report an absent capability instead of inventing a tool.
Account operations
Use tools only for the requested account and operation. Taking payments through SumUp MCP is not supported. For payment collection, help the user implement a SumUp API or SDK integration in their application; do not collect card details or invoke tools to process a payment or start a reader payment.
For account queries, report the returned state with stable identifiers and relevant limits. A working query needs its result, not another setup guide. Do not infer payment success from a callback; use authorized reads to check the current state.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 467k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 196k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |