Crystallize headless commerce tools for AI agents via Model Context Protocol
Connect Runs on your machine
claude mcp add crystallize-mcp -e CRYSTALLIZE_TENANT_IDENTIFIER=<CRYSTALLIZE_TENANT_IDENTIFIER> -e CRYSTALLIZE_ACCESS_TOKEN_ID=<CRYSTALLIZE_ACCESS_TOKEN_ID> -e CRYSTALLIZE_ACCESS_TOKEN_SECRET=<CRYSTALLIZE_ACCESS_TOKEN_SECRET> -e CRYSTALLIZE_STATIC_AUTH_TOKEN=<CRYSTALLIZE_STATIC_AUTH_TOKEN> -e CRYSTALLIZE_ACCESS_MODE=<CRYSTALLIZE_ACCESS_MODE> -- npx -y @hayodev/[email protected]{
"mcpServers": {
"crystallize-mcp": {
"command": "npx",
"args": [
"-y",
"@hayodev/[email protected]"
],
"env": {
"CRYSTALLIZE_TENANT_IDENTIFIER": "<CRYSTALLIZE_TENANT_IDENTIFIER>",
"CRYSTALLIZE_ACCESS_TOKEN_ID": "<CRYSTALLIZE_ACCESS_TOKEN_ID>",
"CRYSTALLIZE_ACCESS_TOKEN_SECRET": "<CRYSTALLIZE_ACCESS_TOKEN_SECRET>",
"CRYSTALLIZE_STATIC_AUTH_TOKEN": "<CRYSTALLIZE_STATIC_AUTH_TOKEN>",
"CRYSTALLIZE_ACCESS_MODE": "<CRYSTALLIZE_ACCESS_MODE>"
}
}
}
}{
"mcpServers": {
"crystallize-mcp": {
"command": "npx",
"args": [
"-y",
"@hayodev/[email protected]"
],
"env": {
"CRYSTALLIZE_TENANT_IDENTIFIER": "<CRYSTALLIZE_TENANT_IDENTIFIER>",
"CRYSTALLIZE_ACCESS_TOKEN_ID": "<CRYSTALLIZE_ACCESS_TOKEN_ID>",
"CRYSTALLIZE_ACCESS_TOKEN_SECRET": "<CRYSTALLIZE_ACCESS_TOKEN_SECRET>",
"CRYSTALLIZE_STATIC_AUTH_TOKEN": "<CRYSTALLIZE_STATIC_AUTH_TOKEN>",
"CRYSTALLIZE_ACCESS_MODE": "<CRYSTALLIZE_ACCESS_MODE>"
}
}
}
}{
"servers": {
"crystallize-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@hayodev/[email protected]"
],
"env": {
"CRYSTALLIZE_TENANT_IDENTIFIER": "<CRYSTALLIZE_TENANT_IDENTIFIER>",
"CRYSTALLIZE_ACCESS_TOKEN_ID": "<CRYSTALLIZE_ACCESS_TOKEN_ID>",
"CRYSTALLIZE_ACCESS_TOKEN_SECRET": "<CRYSTALLIZE_ACCESS_TOKEN_SECRET>",
"CRYSTALLIZE_STATIC_AUTH_TOKEN": "<CRYSTALLIZE_STATIC_AUTH_TOKEN>",
"CRYSTALLIZE_ACCESS_MODE": "<CRYSTALLIZE_ACCESS_MODE>"
}
}
}
}Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
CRYSTALLIZE_TENANT_IDENTIFIEROptional | Your Crystallize tenant identifier (e.g. 'my-store'). Find it in your Crystallize dashboard URL: app.crystallize.com/{tenant} |
CRYSTALLIZE_ACCESS_TOKEN_IDOptional | Access Token ID for authenticated API access. Create one at Settings > Access Tokens in your Crystallize dashboard. Optional — public catalogue and Discovery API work without auth. |
CRYSTALLIZE_ACCESS_TOKEN_SECRETOptional | Access Token Secret (paired with Access Token ID). |
CRYSTALLIZE_STATIC_AUTH_TOKENOptional | Static auth token (alternative to token ID/secret pair). Read-only. |
CRYSTALLIZE_ACCESS_MODEOptional | Controls which tools are available: 'read' (default, safe), 'write' (can create/update items), 'admin' (full access including webhooks). |
Details
| Package | @hayodev/[email protected] (NPM, stdio) |
| First published | 10 Apr 2026 |
| Last updated | 10 Apr 2026 |
| Registry name | io.github.HayoDev/crystallize-mcp |
More ai and media servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.