Ext Ops Panel
Open dashboard
Comparison

Stripe vs Decionis Commerce Gate MCP

Stripe is an MCP server published by stripe. Marketplaces we read that list it: 1 (Docker MCP Catalog). Decionis Commerce Gate MCP is an MCP server published by decionis.com. 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

Where each is published
MarketplaceStripeDecionis Commerce Gate MCP
Docker MCP Catalog Listed
Version: sha256:92ba43f82377
Forks (GitHub): 370
Pulls (Docker Hub): 45 677
Stars (Docker Hub): 9
Stars (GitHub): 1 952
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.0
Downloads/month (npm): 759
Downloads/week (npm): 179
Forks (GitHub): 59
Stars (GitHub): 688
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

Stripe vs Decionis Commerce Gate MCP
FactStripeDecionis Commerce Gate MCP
Marketplaces that list it11
Stars (GitHub) (differs)1 952 (better)688 (worse)
Pulls (Docker Hub) (differs)45 677No figure on Docker Hub
Forks (GitHub) (differs)370 (better)59 (worse)
Last release (differs)Not published2026-10-15
Where it runs (differs)On your machine (mcp/stripe)On your machine (@decionis/commerce)
Transportstdiostdio
Tools it declares (differs)22Not published
Environment variables it asks for (differs)1, secrets among them: 15, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/stripe/agent-toolkitNot stated
Changes in the last 7 days (differs)03
First seen2026-10-112026-10-11

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

Stripe

In its own words, on Docker MCP Catalog:

Interact with Stripe services over the Stripe API.

Decionis Commerce Gate MCP

In its own words, on Official MCP Registry:

Commerce preflights, agent run mandates, D365 authorization, and offer checks; no external writes.

How to run each

Stripe As a local MCP server: Docker image

Claude Code
claude mcp add --env "STRIPE_SECRET_KEY=<YOUR_STRIPE_SECRET_KEY>" --transport stdio stripe -- docker run -i --rm -e STRIPE_SECRET_KEY mcp/stripe

Requires: STRIPE_SECRET_KEY (secret)

Decionis Commerce Gate MCP As a local MCP server: npm package

Claude Code
claude mcp add --env "DECIONIS_API_KEY=<YOUR_DECIONIS_API_KEY>" --transport stdio commerce-gate -- npx -y @decionis/commerce

Requires: DECIONIS_API_KEY (secret)

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

Tools each declares

The marketplaces of Decionis Commerce Gate MCP publish no list of tools, so we do not compare tools.

Settings each asks for

Only Stripe asks for

  • STRIPE_SECRET_KEY (secret)

Only Decionis Commerce Gate MCP asks for

  • AGENTOPS_AUTO_PROVISION
  • AGENTOPS_HOME
  • DECIONIS_API_BASE
  • DECIONIS_API_KEY (secret)
  • DECIONIS_ORG_ID

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Stripe · What it can do: Decionis Commerce Gate MCP · 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.

Where the data comes from: how the catalog is built