Crystallize MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add crystallize-mcp -- npx -y @hayodev/crystallize-mcp

{
  "mcpServers": {
    "crystallize-mcp": {
      "args": [
        "-y",
        "@hayodev/crystallize-mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.crystallize-mcp]
command = "npx"
args = ["-y", "@hayodev/crystallize-mcp"]

{
  "mcpServers": {
    "crystallize-mcp": {
      "args": [
        "-y",
        "@hayodev/crystallize-mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "crystallize-mcp": {
      "args": [
        "-y",
        "@hayodev/crystallize-mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: CRYSTALLIZE_TENANT_IDENTIFIER (Your Crystallize tenant identifier (e.g. 'my-store'). Find it in your Crystallize dashboard URL: app.crystallize.com/{tenant}), CRYSTALLIZE_ACCESS_TOKEN_ID (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_SECRET (Access Token Secret (paired with Access Token ID).), CRYSTALLIZE_STATIC_AUTH_TOKEN (Static auth token (alternative to token ID/secret pair). Read-only.), CRYSTALLIZE_ACCESS_MODE (Controls which tools are available: 'read' (default, safe), 'write' (can create/update items), 'admin' (full access including webhooks).). The author declared them in the registry entry; get the values from the project itself.