Connect Customizer to Claude, ChatGPT, Claude Code, or another compatible AI assistant to explore analytics, inspect catalog configuration, troubleshoot differences between workspaces, and make supported changes from a conversation.
Overview
What is MCP?
Model Context Protocol (MCP) is an open standard that allows AI assistants to connect to external tools and data.
When you connect an assistant to Customizer, the assistant does not receive unrestricted access to Customizer or its data. Instead, the Customizer MCP server exposes a specific set of tools that the assistant can use, such as:
-
Running analytics reports
-
Looking up products and options
-
Checking product and option availability
-
Comparing configuration between workspaces
-
Creating or editing options
-
Updating product metadata
-
Previewing and applying promotions between workspaces
You sign in with your Customizer account and choose which permissions to share. Customizer applies those permissions when the assistant uses a tool.
This means you can work with Customizer using normal questions and instructions instead of navigating through reports or manually looking up configuration.
For example:
-
"Which workspace am I in?"
-
"What can I do with this connection?"
-
"Why is option ORANGE available in staging but not production?"
-
"Show the ten most frequently selected colors in orders last month."
-
"Preview promoting product ABC-123 from staging to production."
Connect your assistant
Use the Customizer MCP server URL when adding the connection to your assistant.
General parameters
-
Use
https://customizer.drivecommerce.com/mcpwhen configuring connections to Customizer MCP. -
Use Customizer as the connection name. This makes prompts and examples easier to recognize.
-
A suggested description is:
Run Customizer analytics, inspect catalog configuration, edit supported products and options, check availability, and promote products or options between workspaces.
If the assistant accepts an icon, use the Customizer icon in PNG format at 256×256, found at https://cdn.drrv.co/drive/customizer/mcp/Customizer-Glass-Cube.png
Claude
-
Open Settings → Connectors.
-
Click Add custom connector.
-
Name the connector Customizer and paste the server URL (
https://customizer.drivecommerce.com/mcp). -
Continue using the detected authentication settings.
-
Click Connect.
-
Sign in to Customizer.
-
Choose the permissions you want to share and click Allow.
-
Enable Customizer from Claude's tools or connectors menu when you want to use it in a conversation.
For Team and Enterprise organizations, an organization owner may need to add or approve the connector before members can connect their own Customizer accounts.
See the Claude custom connector documentation for current setup and plan requirements.
ChatGPT
Custom MCP connections are added as apps in ChatGPT. The exact menus available depend on your plan and workspace policy.
-
On ChatGPT web, open Workspace Settings → Apps.
-
Enable developer mode if your workspace requires it for custom MCP apps.
-
Choose Create or Create custom app.
-
Name the app Customizer and add the description and icon above.
-
Enter the Customizer MCP server URL (
https://customizer.drivecommerce.com/mcp). -
Select OAuth authentication. Customizer publishes the OAuth configuration required by the client.
-
Complete the connection setup.
-
Sign in to Customizer, choose the permissions to share, and click Allow.
-
Select Customizer from ChatGPT's tools or apps when you want a message to use it.
-
If using the Business Plan, publish the app to the workspace to make it available to members.
Managed ChatGPT workspaces may require an administrator to enable, approve, or publish the app before other members can use it.
See the ChatGPT MCP app documentation for current setup and plan requirements.
Claude Code
With Claude Code installed, run:
claude mcp add --transport http customizer https://customizer.drivecommerce.com/mcp
Start Claude Code and enter:
/mcp
Select Customizer and follow the browser sign-in flow.
After authentication, Customizer tools can be used from Claude Code conversations.
How to: Start with analytics
For reporting, Customizer MCP can analyze saved designs and configurator activity directly from a conversation.
You can report on:
-
Products and components selected in saved designs
-
Designs associated with orders
-
Activity by product, site, or date
-
Configurator funnels and drop-off
-
Time taken to save a design
-
Other configurator interaction activity
For example:
-
"Which 10 sleeve components appeared most often in saved designs last month? Break it down by site."
-
"How many designs were saved each day last month?"
-
"What share of saved designs were linked to an order last month, by product?"
-
"Where did customers drop off before saving a design last month?"
-
"How long did customers take to save a design last month, by site?"
You can continue the conversation to refine a report:
-
"Show only the online site."
-
"Group that by week."
-
"Now show only designs linked to orders."
Include a date range when it matters. If you do not specify one, analytics reports use the last 30 days.
Each report returns up to 500 rows. For larger datasets, ask for totals, counts, rankings, or grouped results instead of individual records.
If you only need reporting, select View Analytics when connecting and clear the configuration permissions.
How to: Catalog automation
If you share configuration permissions, the assistant can also inspect and modify supported parts of the Customizer catalog.
|
Task |
What you can ask for |
|---|---|
|
Look up catalog configuration |
Find products, placements, option definitions, options, and sites. Check product status, availability, active versions, site assignments, packages, and rules where supported. |
|
Find options |
Search by definition, code, partial code, tag, or custom attribute. |
|
Create options |
Create new options under an existing option definition, including names, descriptions, tags, attributes, ordering, and availability. |
|
Edit options |
Update names, descriptions, tags, custom attributes, ordering, and availability. |
|
Schedule options |
Activate or deactivate options globally or for individual sites, immediately or on a scheduled date. |
|
Edit products |
Update product names, descriptions, tags, and custom attributes. |
|
Troubleshoot workspaces |
Compare products, options, availability, packages, and rules between workspaces such as staging and production. |
|
Promote products |
Preview copying a product and its configuration into another workspace, then apply the promotion after review. |
|
Promote options |
Preview and copy selected options and their definitions into another workspace. |
|
Shared notes |
Record short catalog facts and conventions that are useful to other colleagues using the Customizer connection. |
|
Workspaces |
Check the current workspace, list available workspaces, and switch between them. |
|
Caches |
Clear Customizer caches after configuration changes made outside the MCP tools. |
For example:
-
"Find options whose code contains RED and show their tags."
-
"Tag options X, Y, and Z as clearance."
-
"Create a Color option CORAL named Coral using the same tags and attributes as RED."
-
"Is product ABC-123 currently available on the US site?"
-
"Compare option X between staging and production. Is it configured the same way in both?"
-
"Why does MagSafe Orange work in staging but not production?"
-
"Switch to staging and preview promoting product ABC-123 to production."
Choose what your assistant can access
When you connect, Customizer shows the permissions your account is allowed to share.
Clear any permissions that the assistant does not need.
|
Permission |
Allows your assistant to |
|---|---|
|
View Analytics |
Run reports against saved designs and configurator activity and answer follow-up questions about the results. |
|
View Configuration |
Look up products, placements, option definitions, options, sites, availability, packages, and other supported configuration data. |
|
MCP Manage Configuration |
Create and edit options, edit supported product metadata, change option availability, record shared notes, clear caches, and promote products and options between workspaces. |
MCP Manage Configuration is only available to share when your Customizer account has the corresponding configuration management permission.
For reporting-only access, share View Analytics and clear the configuration permissions.
Tips
Check the workspace before making changes
The Customizer connection remembers its current workspace.
If you have access to multiple production, staging, development, or client workspaces, ask:
-
"Which workspace am I in?"
before making changes or pasting configuration intended for another workspace.
You can also ask:
-
"Show my available workspaces."
or:
-
"Switch to staging."
OAuth connections can switch between workspaces available to your Customizer account. API keys are restricted to the workspace where the key was created.
Review option changes
Option changes use exact option definitions and codes.
A single operation can modify up to 200 options. If an option or definition cannot be resolved, the operation is rejected instead of partially applying the remaining changes.
For larger changes, first ask the assistant to find the options and show exactly which records will be affected.
Creating a new option does not automatically enable it on a product. Product packages still determine where an option can be selected.
Preview promotions (copy options and products)
Product and option promotions begin with a preview.
For example:
-
"Preview promoting product ABC-123 from staging to production."
The preview identifies what the promotion contains, what already exists in the target workspace, and what will be created or overwritten.
Review the preview and warnings before asking the assistant to apply it.
Promotions may include shared configuration such as placements, option definitions, and options used by the product, so pay particular attention to shared items that already exist in the target workspace.
Expect confirmations
The assistant may ask for confirmation before configuration changes.
There can be more than one confirmation step:
-
The Customizer tool may require the assistant to show you the proposed change first.
-
Your AI assistant may independently ask you to approve a write action.
The exact confirmation behavior depends on the assistant and its settings.
Keep shared notes catalog-specific
Your assistant may detect useful shared knowledge and suggest to save memories as Shared Notes. Shared notes are visible to colleagues using the Customizer connection for the same client.
Good shared notes describe catalog conventions, for example:
-
"Seasonal products use the seasonal tag."
-
"Product Red options are maintained in the staging workspace before promotion."
You can also prompt the assistant to save notes explicitly. Do not store personal information, conversation history, credentials, or other sensitive information in shared notes.
Cache clearing is usually unnecessary
Changes made through the MCP configuration tools automatically refresh the relevant Customizer caches.
Use cache clearing primarily after changes made directly in Customizer Admin or through another integration when the storefront is still using cached configuration.
Changes that still require Customizer Admin
For security and data consistency purpuses, MCP intentionally exposes a limited set of configuration changes.
Use Customizer Admin or the appropriate integration to perform operations that are not exposed through MCP, including:
-
Creating or deleting products
-
Creating option definitions
-
Creating placements
-
Editing product packages
-
Editing rules
-
Changing product status
-
Creating or changing product versions
-
Changing product site assignments
-
Deleting options
-
Managing views
-
Managing orders
-
Managing users and permissions
You can still use the assistant to inspect related configuration and help identify what needs to be changed.
Disconnect
To stop using Customizer with an assistant, remove or disconnect Customizer from the assistant's connector or app settings.
You can also ask a connected assistant:
-
"Sign out of Customizer."
Signing out revokes the current Customizer login and requires authentication again before the connection can be used.