Crystallize MCP vs Swell MCP
Crystallize MCP is an MCP server published by HayoDev. Marketplaces we read that list it: 1 (Official MCP Registry). Swell MCP is an MCP server published by devkindhq. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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 |  Crystallize MCP |  Swell MCP |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.0 Downloads/month (npm): 287 Downloads/week (npm): 48 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.1.0 Downloads/month (npm): 213 Downloads/week (npm): 38 Forks (GitHub): 1 Stars (GitHub): 2 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 | Crystallize MCP | Swell MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 2 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 1 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@hayodev/crystallize-mcp) | On your machine (swell-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 5, secrets among them: 0 | 2, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/hayodev/crystallize-mcp | github.com/devkindhq/swell-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 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
Crystallize MCP
Crystallize headless commerce tools for AI agents via Model Context Protocol
Swell MCP
Model Context Protocol server for Swell e-commerce platform integration with AI assistants
How to run each
Crystallize MCP As a local MCP server: npm package
claude mcp add --transport stdio crystallize-mcp -- npx -y @hayodev/crystallize-mcpSwell MCP As a local MCP server: npm package
claude mcp add --env "SWELL_SECRET_KEY=<YOUR_SWELL_SECRET_KEY>" --env "SWELL_STORE_ID=<YOUR_SWELL_STORE_ID>" --transport stdio swell -- npx -y swell-mcpRequires: SWELL_SECRET_KEY (secret), SWELL_STORE_ID
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 Crystallize MCP asks for
CRYSTALLIZE_ACCESS_MODECRYSTALLIZE_ACCESS_TOKEN_IDCRYSTALLIZE_ACCESS_TOKEN_SECRETCRYSTALLIZE_STATIC_AUTH_TOKENCRYSTALLIZE_TENANT_IDENTIFIER
Only Swell MCP asks for
SWELL_SECRET_KEY (secret)SWELL_STORE_ID
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Crystallize MCP · What it can do: Swell MCP · Compare two other plugins
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.