For the complete documentation index, see llms.txt. This page is also available as Markdown.

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

Connector
What it unlocks

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 a connector, and where it lands in the order

Adding one

1

Give it an endpoint

The MCP server URL, for example:

2

Set authentication

Bearer auth is supported — supply a token when your server requires one.

3

Place it in the order

Higher wins on tool-name collisions — put yours above Maker MCP to override a tool.

4

Revalidate

The refresh button beside Add connector confirms the server responds and its tools are picked up.

5

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.

Last updated

Was this helpful?