# SumUp MCP Server [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://github.com/sumup/sumup-agent-toolkit  
**GitHub Stars:** 14  
**npm Downloads (last month):** 1009  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/sumup-mcp-server

## Description
Tools to explore SumUp accounts, payments, customers, and payouts.

## Tools
Capabilities this server exposes over MCP:

- **create_checkout** — Creates a new payment checkout resource. The unique `checkout_reference` created by this request, is used for further manipulation of the checkout.

For 3DS checkouts, add the `redirect_url` parameter to your request body schema.
To use the [Hosted Checkout](https://developer.sumup.com/online-payments/checkouts/hosted-checkout/) page, set the `hosted_checkout.enabled` to `true`.

Follow by processing a checkout to charge the provided payment instrument.
- **create_customer** — Creates a new saved customer resource which you can later manipulate and save payment instruments to.
- **create_merchant_member** — Create a merchant member.
- **create_merchant_role** — Create a custom role for the merchant. Roles are defined by the set of permissions that they grant to the members that they are assigned to.
- **create_reader** — Create a new Reader for the merchant account.
- **create_reader_checkout** — Creates a Checkout for a Reader.

This process is asynchronous and the actual transaction may take some time to be started on the device.


There are some caveats when using this endpoint:
* The target device must be online, otherwise checkout won't be accepted
* After the checkout is accepted, the system has 60 seconds to start the payment on the target device. During this time, any other checkout for the same device will be rejected.


**Note**: If the target device is a Solo, it must be in version 3.3.24.3 or higher.
- **create_reader_terminate** — Terminate a Reader Checkout stops the current transaction on the target device.

This process is asynchronous and the actual termination may take some time to be performed on the device.


There are some caveats when using this endpoint:
* The target device must be online, otherwise terminate won't be accepted
* The action will succeed only if the device is waiting for cardholder action: e.g: waiting for card, waiting for PIN, etc.
* There is no confirmation of the termination.

If a transaction is successfully terminated and `return_url` was provided on Checkout, the transaction status will be sent as `failed` to the provided URL.


**Note**: If the target device is a Solo, it must be in version 3.3.28.0 or higher.
- **deactivate_checkout** — Deactivates an identified checkout resource. If the checkout has already been processed it can not be deactivated.
- **deactivate_payment_instrument** — Deactivates an identified card payment instrument resource for a customer.
- **delete_merchant_member** — Deletes a merchant member.
- **delete_merchant_role** — Delete a custom role.
- **delete_reader** — Delete a reader.
- **get_checkout** — Retrieves an identified checkout resource. Use this request after processing a checkout to confirm its status and inform the end user respectively.
- **get_customer** — Retrieves an identified saved customer resource through the unique `customer_id` parameter, generated upon customer creation.
- **get_merchant** — Retrieve a merchant.
- **get_merchant_member** — Retrieve a merchant member.
- **get_merchant_role** — Retrieve a custom role by ID.
- **get_payment_methods** — Get payment methods available for the given merchant to use with a checkout.
- **get_person** — Returns a single person related to the merchant.
- **get_reader** — Retrieve a Reader.
- **get_receipt** — Retrieves receipt specific data for a transaction.
- **get_transaction_v2_1** — Retrieves the full details of an identified transaction. The transaction resource is identified by a query parameter and *one* of following parameters is required:
- `id`
- `transaction_code`
- `foreign_transaction_id`
- `client_transaction_id`
- **list_checkouts** — Lists created checkout resources according to the applied `checkout_reference`.
- **list_memberships** — List memberships of the current user.
- **list_merchant_members** — Lists merchant members.
- **list_merchant_roles** — List merchant's custom roles.
- **list_payment_instruments** — Lists all payment instrument resources that are saved for an identified customer.
- **list_payouts_v1** — Lists payout and payout-deduction records for the specified merchant account within the requested date range.

The response can include:
- regular payouts (`type = PAYOUT`)
- deduction records for refunds, chargebacks, direct debit returns, or balance adjustments

Results are sorted by payout date in the requested `order`.
- **list_persons** — Returns a list of persons related to the merchant.
- **list_readers** — List all readers of the merchant.
- **list_transactions_v2_1** — Lists detailed history of all transactions associated with the merchant profile.
- **refund_transaction** — Refunds an identified transaction either in full or partially.
- **update_customer** — Updates an identified saved customer resource's personal details.

The request only overwrites the parameters included in the request, all other parameters will remain with their initially assigned values.
- **update_merchant_member** — Update the merchant member.
- **update_merchant_role** — Update a custom role.
- **update_reader** — Update a Reader.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "sumup-mcp-server": {
    "command": "npx",
    "args": ["-y","@sumup/mcp"],
    "env": {
      "SUMUP_API_KEY": ""
    }
  }
}
```

**Requires environment variables:** `SUMUP_API_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What SumUp MCP Server MCP server does

SumUp MCP Server MCP server exposes SumUp functionality to AI agents through the Model Context Protocol. The available capabilities cover four main areas: account exploration, payment activity, customer information, and payout data. These tools can support payment-processing workflows and reporting tasks in applications that can connect to MCP servers.

The repository is part of SumUp AI, a broader toolkit for building AI-enhanced applications that integrate with SumUp. The MCP component is distinct from the TypeScript Agent Toolkit, which is installed separately as `@sumup/agent-toolkit`.

## How it works

SumUp provides a hosted MCP endpoint at `https://mcp.sumup.com`. An MCP-compatible client can use that endpoint to give an agent access to the SumUp capabilities exposed by the service.

The server can also run locally through the published `@sumup/mcp` package. The documented command starts the package with `npx` and passes a SumUp API key through an environment variable. This option is useful when the MCP process needs to run in the same environment as the client or application using it.

## Setup and configuration

For local execution, provide a valid SumUp API key and run:

```sh
SUMUP_API_KEY=YOUR_SUMUP_API_KEY npx -y @sumup/mcp
```

The required configuration variable is `SUMUP_API_KEY`.

The repository also points to separate MCP installation instructions and to SumUp developer documentation. Those references should be consulted for client-specific setup details, authentication guidance, and the current hosted-service behavior.

## Tools and capabilities

The documented capability areas are:

- Explore SumUp accounts.
- Work with payment data and payment-processing workflows.
- Access customer information.
- Inspect payouts.
- Support reporting use cases involving SumUp data.

The SumUp MCP Server MCP server is therefore a fit for agents that need to answer questions about SumUp activity or assist with workflows spanning payments, customers, and payouts.

## Limitations and notes

It also does not state whether each capability is read-only or can mutate SumUp data, so developers should verify operation permissions before allowing an agent to perform changes.

The repository includes both MCP resources and a TypeScript SDK. Installing `@sumup/agent-toolkit` is not the same as running the SumUp MCP Server MCP server; the local MCP command uses `@sumup/mcp`.

Confirm the appropriate connection format and authentication steps in the referenced MCP installation documentation before deployment.

_Full upstream README: https://allmcps.com/mcp/sumup-mcp-server/readme_