MCP server Rubik Combined Listings Swatch
The MCP server lets AI assistants like Claude work with your combined listings. Once connected, you can simply ask your assistant to do things like "combine my three Aurora hoodies into one listing with color swatches" or "hide out-of-stock swatches storewide", and it happens in your store, using the same reliable operations as the app itself.
MCP (Model Context Protocol) is an open standard supported by Claude and a growing number of AI tools. Rubik Combined Listings Swatch ships a built-in MCP server, so there is nothing to install: you create a connection token in the app and add it to your assistant.
What a connected assistant can do
| Capability | Details |
|---|---|
| Look up your setup | Your plan, how many product group slots are used and remaining, and shop-wide settings. |
| Search products | Find products in your store by title, vendor, tag, or status to use in groups. |
| Manage product groups | List, inspect, create, edit, and delete combined listing groups, including option values, swatch colors, and per-group visual settings. |
| Change app settings | Any setting from the app's Settings page: where swatches appear, out-of-stock behavior, sorting, image sizes, and more. |
Everything a full-access assistant changes goes live on your storefront immediately, exactly as if you had made the change in the app.
Create a connection
1Open the MCP server page
In the app, open MCP server from the navigation menu, then select Create connection.
2Name it and choose the access level
Give the connection a name you will recognize later (for example "Claude on my laptop"). Then pick the access level:
- Read-only: the assistant can look at your groups, settings, and products, but can never change anything. A safe way to start.
- Full access: the assistant can also create, edit, and delete product groups and change app settings.
3Copy your token
The token is shown only once, right after you create the connection. Copy it and store it somewhere safe. If you lose it, revoke the connection and create a new one.
Connect your assistant
Claude Code (terminal)
Paste the ready-made command from the app, or build it yourself:
Claude Desktop
Claude Desktop connects to HTTP MCP servers through a small local proxy. Add this to your claude_desktop_config.json (Settings → Developer → Edit config), then restart Claude Desktop:
The token is passed via the env value (note: no space around the colon in the --header argument). This form avoids a known Claude Desktop on Windows bug where spaces inside arguments get mangled.
claude.ai custom connectors
claude.ai custom connectors currently authenticate with OAuth only, so they cannot use these bearer tokens yet. OAuth support for one-click setup is planned. For now, use Claude Code or any MCP client that accepts a custom header (below).
Other MCP clients
Any client that supports MCP over Streamable HTTP with a custom Authorization header works. Use the server URL https://rubikswatch.com/mcp and send Authorization: Bearer YOUR_TOKEN with each request.
Tip: once connected, start by asking your assistant something like "What can you do with my combined listings?" or "How many product groups do I have?" to confirm everything works.
Security
- Per-store tokens. A token only ever gives access to the store it was created in.
- Shown once, stored hashed. We keep only a cryptographic hash of your token; nobody (including us) can read it back.
- Read-only by default. Full access is an explicit choice when you create a connection.
- Revoke anytime. Revoking a connection takes effect immediately; assistants using that token stop working on the spot.
- Deletion is confirmed. Assistants must confirm with you before permanently deleting a product group.
- Rate limits. Connections are rate limited per store, so a misbehaving assistant cannot overload your setup.
- Uninstall safety. If you uninstall the app, every connection stops working automatically.
Troubleshooting
- Authentication errors: the token was mistyped, expired, or revoked. Create a new connection and update your assistant with the new token.
- "Rate limit exceeded" messages: the assistant is calling faster than the per-store limits allow. It should wait the indicated number of seconds and retry; no action needed from you.
- "Plan limit reached" when creating groups: your plan's product group limit is used up. The message includes a link to upgrade.
- Shopify API errors right after a long break: open the app once in your Shopify admin, then try again.
Questions or ideas for new assistant capabilities? Contact support, we would love to hear how you use it.