sumup-mcp
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.