Crystallize headless commerce tools for AI agents via Model Context Protocol
Connect Crystallize MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Crystallize headless commerce tools for AI agents via Model Context Protocol. The crystallize mcp mcp server is what makes that connection.
MCP server for Crystallize headless commerce. Gives AI agents read and write access to your catalogue, products, shapes, orders, customers, and tenant config — with deep links back to the Crystallize UI, dry-run safety for mutations, and PII masking for customer data.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
browse_catalogue — Traverse the item tree by pathget_item — Fetch an item by path or ID with full component datasearch_catalogue — Keyword search across all itemsget_product_variants — List variants with pricing and stocklist_discovery_shapes — List all shapes with their queryable fieldsbrowse_shape — Browse items of a shape with filters, pagination, and field selectionget_shape_fields — Detailed field info for a specific shapelist_shapes — All shapes with component summariesget_shape — Full component definition for a shapeget_tenant_info — Tenant configuration and available languageslist_orders — List orders for a customer with paginationget_order — Full order details — cart, payments, customer, totalsConfiguration is passed through the environment: CRYSTALLIZE_TENANT_IDENTIFIER, CRYSTALLIZE_ACCESS_TOKEN_ID, CRYSTALLIZE_ACCESS_TOKEN_SECRET, CRYSTALLIZE_ACCESS_MODE, CRYSTALLIZE_DRY_RUN, CRYSTALLIZE_STATIC_AUTH_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Installation goes through your MCP client rather than a global install: point it at @hayodev/crystallize-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
This sits in the browser automation group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Crystallize MCP's toolset — browse_catalogue, get_item, search_catalogue and 11 more — is a fair guide to whether it matches your workflow. It is maintained by HayoDev; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Crystallize MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| browse_catalogue | Traverse the item tree by path |
| get_item | Fetch an item by path or ID with full component data |
| search_catalogue | Keyword search across all items |
| get_product_variants | List variants with pricing and stock |
| list_discovery_shapes | List all shapes with their queryable fields |
| browse_shape | Browse items of a shape with filters, pagination, and field selection |
| get_shape_fields | Detailed field info for a specific shape |
| list_shapes | All shapes with component summaries |
| get_shape | Full component definition for a shape |
| get_tenant_info | Tenant configuration and available languages |
| list_orders | List orders for a customer with pagination |
| get_order | Full order details — cart, payments, customer, totals |
| list_customers | Search and list customers with pagination |
| get_customer | Full customer profile — addresses, meta, external references |
{
"mcpServers": {
"crystallize": {
"command": "npx",
"args": ["-y", "@hayodev/crystallize-mcp"],
"env": {
"CRYSTALLIZE_TENANT_IDENTIFIER": "your-value",
"CRYSTALLIZE_ACCESS_TOKEN_ID": "your-value",
"CRYSTALLIZE_ACCESS_TOKEN_SECRET": "your-value",
"CRYSTALLIZE_ACCESS_MODE": "your-value",
"CRYSTALLIZE_DRY_RUN": "your-value",
"CRYSTALLIZE_STATIC_AUTH_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| CRYSTALLIZE_TENANT_IDENTIFIER | Configuration value read at startup. | Optional |
| CRYSTALLIZE_ACCESS_TOKEN_ID | Credential the server authenticates with. | Yes |
| CRYSTALLIZE_ACCESS_TOKEN_SECRET | Credential the server authenticates with. | Yes |
| CRYSTALLIZE_ACCESS_MODE | Configuration value read at startup. | Optional |
| CRYSTALLIZE_DRY_RUN | Configuration value read at startup. | Optional |
| CRYSTALLIZE_STATIC_AUTH_TOKEN | Credential the server authenticates with. | Yes |
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.