B2C Python SDK vs Decionis Commerce Gate MCP
B2C Python SDK is a plugin bundle for AI coding tools published by Salesforce. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Decionis Commerce Gate MCP is an MCP server published by decionis.com. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-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
| Marketplace |  B2C Python SDK | |
|---|---|---|
| Community marketplace salesforcecommercecloud/b2c-developer-tooling | Listed Version: 0.1.0 Forks (GitHub): 24 Stars (GitHub): 58 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.3.0 Downloads/month (npm): 890 Downloads/week (npm): 346 Forks (GitHub): 59 Stars (GitHub): 688 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.3.0 Downloads/month (npm): 890 Downloads/week (npm): 346 Forks (GitHub): 59 (last published figure) Stars (GitHub): 688 (last published figure) 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 | B2C Python SDK | Decionis Commerce Gate MCP |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 58 (worse) | 688 (better) |
| Forks (GitHub) (differs) | 24 (worse) | 59 (better) |
| Last release (differs) | Not published | 2026-11-04 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@decionis/commerce) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 5, secrets among them: 1 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence | Apache-2.0 | Apache-2.0 |
| Repository (differs) | github.com/salesforcecommercecloud/b2c-developer-tooling | github.com/decionis/commerce |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-11-04 | 2026-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
B2C Python SDK
Consuming the salesforce-b2c-tooling-sdk Python SDK — authenticate to B2C Commerce, resolve dw.json config, and call OCAPI/SCAPI/WebDAV clients and operations from scripts or notebooks.
Decionis Commerce Gate MCP
Commerce preflights, D365 authorization; opt-in agent writes require authorized backend connectors.
How to run each
B2C Python SDK As a Claude Code plugin
/plugin marketplace add salesforcecommercecloud/b2c-developer-tooling
/plugin install b2c-python-sdk@b2c-developer-toolingDecionis Commerce Gate MCP As a local MCP server: npm package
claude mcp add --env "DECIONIS_API_KEY=<YOUR_DECIONIS_API_KEY>" --transport stdio commerce-gate -- npx -y @decionis/commerceRequires: 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
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of B2C Python SDK publish no settings it asks for, so we do not compare settings.
What it can do: B2C Python SDK · What it can do: Decionis Commerce Gate MCP · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.