Dodo Payments vs payware
Dodo Payments is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). 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-14. 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
| Marketplace |  payware | |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published 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
| Fact | Dodo Payments | payware |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | Not published | 2026-10-13 |
| Where it runs (differs) | Remote server (mcp.dodopayments.com/sse) | On your machine (@payware/mcp-server) |
| Transport (differs) | SSE | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 7, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | Not stated | github.com/payware/mcp-server |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | no 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
Dodo Payments
Tools for cross-border payments, taxes, and compliance.
payware
payware A2A payments API for merchants, ISVs and payment institutions
How to run each
Dodo Payments As a remote MCP server
claude mcp add --transport sse dodo-payments https://mcp.dodopayments.com/sseRequires: DODO_PAYMENTS_API_KEY (secret)
payware As a local MCP server: npm package
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-serverRequires: 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.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only Dodo Payments asks for
DODO_PAYMENTS_API_KEY (secret)
Only payware asks for
PAYWARE_MCP_TOOLSETSPAYWARE_OAUTH_CLIENT_IDPAYWARE_OAUTH_CLIENT_SECRET (secret)PAYWARE_PARTNER_IDPAYWARE_PARTNER_TYPEPAYWARE_PRODUCTION_PRIVATE_KEY_PATHPAYWARE_SANDBOX_PRIVATE_KEY_PATH
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Dodo Payments · What it can do: payware · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.