Storefront Next vs Heimdall
Storefront Next is a plugin bundle for AI coding tools published by Salesforce. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Heimdall is an MCP server published by erayendes. Marketplaces we read that list it: 3 (Official MCP Registry, npm registry (MCP servers), Community GitHub marketplaces). 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 |  Storefront Next |  Heimdall |
|---|---|---|
| Community marketplace salesforcecommercecloud/b2c-developer-tooling | Listed Version: 1.15.2 Forks (GitHub): 24 Stars (GitHub): 58 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 3.0.0 Downloads/month (npm): 3 373 Downloads/week (npm): 513 Forks (GitHub): 6 Stars (GitHub): 57 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 3.0.0 Downloads/month (npm): 3 373 Downloads/week (npm): 513 Forks (GitHub): 6 Stars (GitHub): 57 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 | Storefront Next | Heimdall |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 58 (better) | 57 (worse) |
| Forks (GitHub) (differs) | 24 (better) | 6 (worse) |
| Last release (differs) | 2026-11-10 (better) | 2026-11-08 (worse) |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@erayendes/asc-mcp) |
| 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) | 24 | 1 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/salesforcecommercecloud/b2c-developer-tooling | github.com/erayendes/app-store-connect-mcp |
| Changes in the last 7 days (differs) | 2 | 20 or more |
| 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
Storefront Next
Storefront Next development skills for building React 19 storefronts on Salesforce B2C Commerce.
Heimdall
Every App Store Connect + StoreKit 2 endpoint. 786 tools in 14 profiles, narrow to 17.
How to run each
Storefront Next As a Claude Code plugin
/plugin marketplace add salesforcecommercecloud/b2c-developer-tooling
/plugin install storefront-next@b2c-developer-toolingHeimdall As a local MCP server: npm package
claude mcp add --env "ASC_PRIVATE_KEY=<YOUR_ASC_PRIVATE_KEY>" --transport stdio asc-mcp -- npx -y @erayendes/asc-mcp "<YOUR_PROFILE>"Requires: ASC_PRIVATE_KEY (secret), <profile>
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 Storefront Next publish no settings it asks for, so we do not compare settings.
What it can do: Storefront Next · What it can do: Heimdall · 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.