Dodo Payments vs comdirect
Dodo Payments is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). comdirect is an MCP server published by mad4ms. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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 |  comdirect | |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.6.1 Downloads/month (PyPI): 0 Downloads/week (PyPI): 336 Forks (GitHub): 0 Stars (GitHub): 3 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 | comdirect |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 3 |
| 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 (comdirect-mcp) |
| Transport (differs) | SSE | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 14, secrets among them: 4 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | Not stated | github.com/mad4ms/comdirect-mcp |
| Changes in the last 7 days (differs) | 0 | 3 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 2 days ago, requires a key | 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.
comdirect
Read-only access to comdirect accounts, transactions, depots, orders and postbox documents.
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)
comdirect As a local MCP server: PyPI package
claude mcp add --env "COMDIRECT_CLIENT_ID=<YOUR_COMDIRECT_CLIENT_ID>" --env "COMDIRECT_CLIENT_SECRET=<YOUR_COMDIRECT_CLIENT_SECRET>" --env "COMDIRECT_PASSWORD=<YOUR_COMDIRECT_PASSWORD>" --env "COMDIRECT_USERNAME=<YOUR_COMDIRECT_USERNAME>" --transport stdio comdirect-mcp -- uvx comdirect-mcpRequires: COMDIRECT_CLIENT_ID (secret), COMDIRECT_CLIENT_SECRET (secret), COMDIRECT_PASSWORD (secret), COMDIRECT_USERNAME (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Dodo Payments 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
Only Dodo Payments asks for
DODO_PAYMENTS_API_KEY (secret)
Only comdirect asks for
COMDIRECT_CLIENT_ID (secret)COMDIRECT_CLIENT_SECRET (secret)COMDIRECT_ENV_FILECOMDIRECT_MCP_CACHE_TTLCOMDIRECT_MCP_CATEGORIESCOMDIRECT_MCP_LOG_FILECOMDIRECT_MCP_LOG_LEVELCOMDIRECT_MCP_MASK_NAMESCOMDIRECT_MCP_MAX_DOCUMENT_BYTESCOMDIRECT_MCP_PUSH_TAN_WAITCOMDIRECT_MCP_SKIP_ELICITATIONCOMDIRECT_MCP_UNMASK_IBANS
Show the remaining 2
COMDIRECT_PASSWORD (secret)COMDIRECT_USERNAME (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Dodo Payments · What it can do: comdirect · 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.