Adding your own connector
Point the assistant at any MCP server — a platform's, a service's, or your own.
Connectors are data sources for the assistant. Anything that speaks MCP can plug in — a commerce platform's catalogue, a third-party service (a Notion MCP, a Stripe MCP, a Zendesk MCP, or any other hosted MCP), or an API you already run, wrapped as an MCP. There is no approved-integrations list: if a service publishes an MCP endpoint, you can connect it.
What people connect
Shopify's public catalog MCP
Product discovery for any Shopify store — no Maker account required. Disable Maker MCP and use this instead.
A third-party service's MCP
Any SaaS that ships a hosted MCP — for example Notion for docs, or Stripe for payments data — connects the same way.
A currency-conversion MCP
The reference storefront uses one (a forex MCP) so the assistant can convert prices on request.
Your own API, wrapped as an MCP
Example: a retailer with a size-guide API exposes it as an MCP, and the assistant can answer "will this fit me?" with real data.
Adding one
Choose which tools it may use
Select the connector to see its tools, sorted into write, read-only and other. Allow or disallow them per group, or one at a time — see Controlling tool access.
This is what makes it safe to connect an MCP you already run internally: expose only the tools a shopping assistant needs, and leave the rest unreachable.
Every allowed tool is a capability handed straight to the AI. Slow connectors make slow answers — the assistant waits on your server — so keep latency in mind, and disallow what you don't need.
Last updated
Was this helpful?