Ext Ops Panel
Open dashboard
Comparison

sumup vs payware

sumup is a plugin bundle for AI coding tools published by sumup. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-official). payware is an MCP server published by payware. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacesumuppayware
Claude Code: claude-plugins-official Listed
Version: 1.0.0
Forks (GitHub): 1
Stars (GitHub): 5
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.4.0
Downloads/month (npm): 828
Downloads/week (npm): 45
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

sumup vs payware
Factsumuppayware
Marketplaces that list it11
Stars (GitHub) (differs)5 (better)0 (worse)
Forks (GitHub) (differs)1 (better)0 (worse)
Last release (differs)Not published2026-10-13
Where it runs (differs)Remote server (mcp.sumup.com/mcp)On your machine (@payware/mcp-server)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published7, secrets among them: 1
Parts of the bundle (differs)7Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/sumup/sumup-skillsgithub.com/payware/mcp-server
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 3 h ago, requires a keyno remote endpoint we check

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

sumup

In its own words, on Claude Code: claude-plugins-official:

SumUp payment integrations across terminal and online checkout flows. Build Android and iOS POS apps with SumUp card readers, online checkout with server SDKs and the checkout widget, and control card readers remotely via Cloud API.

payware

In its own words, on Official MCP Registry:

payware A2A payments API for merchants, ISVs and payment institutions

How to run each

sumup As a Claude Code plugin

Claude Code
/plugin install sumup@claude-plugins-official

payware As a local MCP server: npm package

Claude Code
claude mcp add --env "PAYWARE_OAUTH_CLIENT_SECRET=<YOUR_PAYWARE_OAUTH_CLIENT_SECRET>" --env "PAYWARE_PARTNER_ID=<YOUR_PAYWARE_PARTNER_ID>" --env "PAYWARE_SANDBOX_PRIVATE_KEY_PATH=<YOUR_PAYWARE_SANDBOX_PRIVATE_KEY_PATH>" --transport stdio payware -- npx -y @payware/mcp-server

Requires: PAYWARE_OAUTH_CLIENT_SECRET (secret), PAYWARE_PARTNER_ID, PAYWARE_SANDBOX_PRIVATE_KEY_PATH

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only sumup has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of sumup publish no settings it asks for, so we do not compare settings.

What it can do: sumup · What it can do: payware · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built