Skip to content
Agentmart
Submit a tool

Crystallize MCP

Crystallize headless commerce tools for AI agents.

Connector by HayoDev · GitHub account verified by the MCP Registry

IndexedMITLocal (stdio)
Write a review

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/hayodev-crystallize-mcp

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Crystallize headless commerce tools for AI agents via Model Context Protocol

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools
18 read · 2 write · 0 delete
Secrets
2 (API keys, tokens or passwords)
Install scripts
Not scanned yet
Runs as
Node.js package

Tools by what they do 20

Read from the source code; the running server may list different tools.

Read 18 · Look things up without changing anything.

  • browse_catalogue
  • browse_shape
  • fetch_catalogue_schema
  • fetch_core_schema
  • fetch_discovery_schema
  • fetch_shop_cart_schema
  • get_customer
  • get_item
  • get_order
  • get_product_variants
  • get_shape
  • get_shape_fields
Show 6 more tools
  • get_tenant_info
  • list_customers
  • list_discovery_shapes
  • list_orders
  • list_shapes
  • search_catalogue

Write 2 · Create, change, send or run things.

  • create_item
  • update_component

Secrets and settings it asks for

Secrets: values you paste in that let it act as you.

  • CRYSTALLIZE_ACCESS_TOKEN_SECRET
  • CRYSTALLIZE_STATIC_AUTH_TOKEN

Other settings (environment variables or headers).

  • CRYSTALLIZE_ACCESS_MODE
  • CRYSTALLIZE_ACCESS_TOKEN_ID
  • CRYSTALLIZE_TENANT_IDENTIFIER

Files it touches

  • Any path the agent passes to its tools

Tools (20)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • browse_catalogue

    Browse the catalogue tree by path. Returns child items (folders, products, documents) with names, paths, and types. Start with "/" to see the root.

  • browse_shape

    Browse items of a specific shape using the Discovery API. Supports pagination, search terms, and selecting specific fields. Use list_discovery_shapes first to see available shapes and fields.

  • create_item

    Create a new item (product, document, or folder) in the catalogue. The item type is determined by the shape. Use get_shape first to understand available components. Respects CRYSTALLIZE_DRY_RUN — when enabled, returns a preview without creating.

  • fetch_catalogue_schema

    Fetch the GraphQL schema of the Crystallize Catalogue API. The Catalogue API is a storefront API for fetching items, products, and content — it provides path-based reads with strong consistency and union types for components. Use this to understand available queries, types, and fields before writing catalogue queries.

  • fetch_core_schema

    Fetch the GraphQL schema of the Crystallize Core API (admin API). The Core API is large, so provide a domain to filter the schema (e.g. "order", "customer", "item"). Common domains: order, customer, subscription, subscriptionPlan, pricelist, pipeline, flow, app, user, webhook, stockLocation. Omit domain to get a summary of available types.

  • fetch_discovery_schema

    Fetch the GraphQL schema of the Crystallize Discovery API. The Discovery API is a storefront API for searching, browsing, filtering, and faceting items. It uses a shape-typed schema where each shape in the tenant becomes a GraphQL type. Use this to understand the tenant-specific types and available browse/search queries.

  • fetch_shop_cart_schema

    Fetch the GraphQL schema of the Crystallize Shop Cart API. The Shop Cart API handles cart and wishlist operations — creating carts, adding/removing items, applying discounts, and reading cart state. Use this to understand available cart queries and types.

  • get_customer

    Get full profile for a customer by their identifier (UUID from list_customers). Returns name, email, addresses, meta, and external references.

  • get_item

    Get a catalogue item by path with its full component data. Returns name, type, shape, components, and a deep link to the Crystallize UI.

  • get_order

    Get full details for an order by ID. Returns cart items, customer info, totals, payment provider, and a deep link to the Crystallize UI.

  • get_product_variants

    Get all variants for a product by path. Returns SKUs, names, pricing, stock, and attributes.

  • get_shape

    Get the full component definition for a shape. Shows all components with their types, descriptions, and configuration. Useful for understanding what data a shape expects.

  • get_shape_fields

    Get detailed field information for a specific shape in the Discovery API. Shows all scalar and object fields with their types.

  • get_tenant_info

    Get tenant configuration including name, identifier, available languages, and default language.

  • list_customers

    List customers in the tenant with pagination. Returned fields depend on CRYSTALLIZE_PII_MODE: full (default) returns name, identifier, email, company, and phone; masked returns name, identifier, company, and masked email/phone; none returns identifiers only.

Show 5 more tools
  • list_discovery_shapes

    List all shapes available in the Discovery API with their queryable fields. Use this to understand what shapes exist and what data you can query before calling browse_shape.

  • list_orders

    List orders across the tenant, optionally filtered by customerIdentifier. Returns order IDs, dates, totals, and deep links to the Crystallize UI. Supports pagination.

  • list_shapes

    List all shapes defined in the tenant. Returns shape names, identifiers, types, and component counts with deep links to the Crystallize UI.

  • search_catalogue

    Search across the catalogue for products, documents, and folders. Supports filtering by type (PRODUCT, DOCUMENT, FOLDER). Returns names, paths, types, and deep links.

  • update_component

    Update a single component on a catalogue item. Supports nested components inside content chunks using dot notation (e.g. "image-and-title.title"). For repeating content chunks, use rowIndex to target a specific row (0 = first row). Use get_item to see current values and get_shape to understand component types. Respects CRYSTALLIZE_DRY_RUN — when enabled, returns a before/after preview without changing anything.

Signals

Stars
0
Forks
0
Open issues
0
Weekly downloads
26
Last commit
Apr 10, 2026 (6 months ago)
Last release
Apr 10, 2026 (6 months ago)
Last package publish
Apr 10, 2026 (6 months ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name
io.github.HayoDev/crystallize-mcp
Version
0.2.0
Auth
No auth
Packages
npm @hayodev/crystallize-mcp
License
MIT
Repository
github.com/HayoDev/crystallize-mcp
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
Official MCP Registrygithub-graphql

More from HayoDev

Cite this page

Crystallize MCP. Agent Mart. https://agentmart.dev/connectors/hayodev-crystallize-mcp (last updated 2026-10-24)