Connectors
Connect Shopify, commercetools, BigCommerce, Adobe Commerce, or any remote MCP server so your agents can call its tools during a conversation, and control which tools are available.
A connector links your organization to a Model Context Protocol (MCP) server. Once a connector is linked to an agent, the agent can call that server's tools while it talks to a shopper, for example to look something up in your store.
AISA connects to your e-commerce platform's catalog and cart via MCP. Open Connectors in the dashboard sidebar, or go to /dashboard/connectors.
Editing connectors requires a permission
Viewing connectors requires the Connectors: View permission; creating, editing, or removing a connector (including its credentials) requires Connectors: Edit. Both built-in roles, Admin and Member, have this by default. See Roles to check or grant it on a custom role.
Supported platforms
| Platform | Status | Setup |
|---|---|---|
| Shopify | GA | Point at your store by its domain (the MCP endpoint is derived automatically). |
| commercetools | Beta | Paste your deployed Commerce MCP endpoint URL and a pre-issued bearer token. |
| BigCommerce | Early access | Paste the store-specific MCP URL from your BigCommerce control panel. |
| Adobe Commerce | Early access | Paste the Storefront MCP URL and the request headers Adobe gave you. |
| Custom | — | Point at any remote MCP server by its URL, with an optional bearer token. |
Running a platform that isn't Shopify, commercetools, BigCommerce, or Adobe Commerce? See Connect a platform with no native connector below for a Custom-connector recipe.
A connector on its own does nothing. It starts working when you link it to an agent's configuration version (see Link a connector to an agent).
Create a Shopify connector
You may already have one
When you created the site, onboarding tried to confirm the platform from your storefront address. If it confirmed Shopify, a connector already exists and is already linked to the site's first agent. See Catalog connection.
Give the connector a name (up to 200 characters) and enter your store domain. That's the only thing you provide: the connector wires itself to your store from the domain.
Save. You land on the connector's detail page, where you can load and manage its tools.
The store domain is all the setup a Shopify connector needs. Once it's saved, the agent can use your store's cart and shop-policy/FAQ tools and search your product catalog. Both come from the same connector, with no second step and no endpoint to choose.
Catalog search and cart need a live (preview or production) agent
Product catalog search and the shopper's cart both rely on Shopify's Universal Commerce Protocol, which needs to reach a small profile we publish at our own public address. They work once your assistant is deployed to a preview or production environment, not against a local development setup. The shop-policy/FAQ tool is unaffected, since Shopify serves it directly with no profile handshake involved. UCP is new and still evolving, so the exact catalog and cart tools can change over time.
To also send your Shopify orders, refunds and cancellations to AISA, see Set up Shopify order webhooks.
Create a commercetools connector
Beta upstream
commercetools' own docs describe Commerce MCP as "currently under development and may be subject to changes" (docs.commercetools.com/sdk/mcp/commerce-mcp). This platform's official MCP server is not yet generally available: its endpoint, authentication, or available tools may change without notice.
Unlike Shopify and BigCommerce, commercetools' Commerce MCP server is something you deploy and operate yourself: there's no platform-hosted endpoint to point at. Before creating the connector you'll need:
- The endpoint URL of your deployed Commerce MCP server.
- A pre-issued bearer access token for a commercetools API client that can reach it.
Give the connector a name, then enter your deployed Commerce MCP server's endpoint URL.
Enter the bearer token. It's required for this type: commercetools' Commerce MCP has no anonymous mode. Scope its API client narrowly rather than granting full project access.
Scope the API client narrowly
commercetools' Commerce MCP surface spans the full commerce back office, not just catalog and cart, but payments, business units, and approval flows too. A leaked token for a broadly-scoped API client can reach far more than a typical connector's token can. commercetools lets you control which API client Commerce MCP uses. Scope it to what your shopping assistant actually needs, not full project access.
Because of that broad surface, a commercetools connector doesn't start with everything switched on: only a curated set of product and category search/read tools and the shopper's own cart read/mutate tools are enabled by default. Every other tool (including one commercetools adds after you created the connector) stays disabled until you explicitly turn it on from the connector's detail page. See Manage the tools a connector exposes below.
Your token is stored encrypted and never shown back
The bearer token is stored encrypted. The dashboard never displays it again. It can't be cleared without replacing it. Enter a new token to rotate it.
Create a BigCommerce connector
Beta upstream
BigCommerce's own docs state "The BigCommerce MCP server is currently in beta" (docs.bigcommerce.com/developer/api-reference/mcp/overview), gated behind Early Access in the control panel. This platform's official MCP server is not yet generally available: its endpoint, authentication, or available tools may change without notice.
BigCommerce's Storefront MCP endpoint is store-specific and isn't derived from your store domain. You copy it from your BigCommerce control panel.
In your BigCommerce control panel, go to Settings → Early access → MCP Integration and enable it. It can take up to 10 minutes to become available after enabling.
Give the connector a name and paste the MCP URL. No token is needed today: BigCommerce's Storefront MCP supports guest shopping only; authenticated shopping isn't released yet.
Request headers
Some MCP servers read extra HTTP headers, for example to know which store they are serving. Every connector type except Shopify has a Request headers section on its form. Each header is sent with every request to the server, when the agent talks to it and when you refresh its tools.
Each row has a name, a value and a Secret switch:
- Secret on: the value is stored encrypted and the dashboard never shows it again. On a saved connector the row says the value is saved. Leave the value blank to keep it, or type a new one to replace it.
- Secret off: the value is stored as typed and shown back when you edit the connector. Use this for values that are not sensitive, such as a store code.
Rules:
- At most 20 headers per connector, and no two with the same name (names are not case sensitive).
- A name must be a valid HTTP header name. A value must be visible ASCII, up to 2048 characters.
- Reserved names are refused, because the connection sets them itself:
Host,Authorization,Content-Type,Content-Length,Accept,Cookie,Connection,Mcp-Session-IdandMcp-Protocol-Version, plus a few other transport headers and anything starting withProxy-orSec-. For authentication, use the connector's bearer token field. - Shopify connectors do not accept headers.
Replacing the list
Saving the form replaces the whole header list. A header you remove from the form is removed from the connector.
Create an Adobe Commerce connector
Early access upstream
Adobe labels its Commerce MCP server "Coming Soon" and "subject to change" on Experience League (checked 2 October 2026). Its endpoint, headers, or tools may change without notice.
Onboarding does not detect Adobe Commerce sites, so no connector is created for you. Add it by hand. You need the Storefront MCP URL and the header values from your Adobe Commerce setup.
Under Request headers, fill in the values Adobe gave you. The form lists
five headers: X-Catalog-Endpoint, X-Environment-Id, X-Store-Code,
X-Store-View-Code and X-Website-Code. All are optional, and a header left
empty is not sent. The catalog needs at least X-Catalog-Endpoint and
X-Store-View-Code to find your products.
Under Product display, check the settings below, then save and use Refresh tools on the detail page.
A bearer token is optional here too, as for a Custom connector.
Product display settings
Adobe's search results don't carry a usable product link or image, so the assistant builds them from these settings.
- Product URL template: how a product link is built. Placeholders:
{siteUrl},{urlKey}and{sku}. Default:{siteUrl}/products/{urlKey}/{sku}. A link Adobe returns on its own is used instead when there is one. The template must produce anhttpsURL. - Image attribute: the product attribute that holds image URLs when Adobe returns no image, for example
dam_image_urls. Optional. - Cart URL template: optional. Placeholders:
{siteUrl}and{cartId}. When set, the agent can link the shopper to their cart.
{siteUrl} is the origin of the site's URL in AISA. If the site has no URL, a link that needs {siteUrl} can't be built and the product is shown without a card, so set the site URL before you rely on the default template. A link with any other missing value is not built either.
Default tools
Only the catalog tools (product search and data, categories, variants, recommendations, facets) and the four cart tools (add, read, update, remove) are on by default. The checkout tools (guest email, shipping and billing address, shipping and payment method, place order), the order lookup and the identity tools are off by default: they would have the assistant collect personal data and place orders in the chat, and placing an order can't be undone. A tool Adobe adds later also starts off. Turn any of them on from the connector's detail page (see Manage the tools a connector exposes).
Create a Custom connector
Use a Custom connector for any MCP server you run or have access to, including a platform that doesn't have a native connector type yet (see below).
Give the connector a name, then enter the server URL. The URL must be HTTPS. Plain HTTP and internal/private addresses are rejected.
Optionally enter a bearer token. If set, it's sent as an Authorization
header on every request to the server. Leave it blank for a server that allows
anonymous access.
Your token is stored encrypted and never shown back
The bearer token is stored encrypted. The dashboard never displays it again: on a saved connector the token field shows it as configured rather than revealing the value. To change it, type a new token; to remove it, use Remove token. Leaving the field blank keeps the existing token.
Connect a platform with no native connector
We looked into official, shopper-facing MCP servers across the most-used e-commerce platforms. These platforms don't have one you can wrap in a native connector today. Here's a Custom-connector recipe for each, pointing at that platform's own API instead.
WooCommerce
WooCommerce core ships a native MCP, but it's an explicit Developer Preview ("implementation details... may change"), and its tools are shaped for merchant/admin operations (product CRUD, order status) rather than shopper catalog search and cart. Use a Custom connector against the WooCommerce REST API v3 (consumer key/secret).
Salesforce Commerce Cloud
Salesforce's only official MCP, the "B2C DX MCP Server," is Developer Preview IDE tooling (SCAPI schema exploration, cartridge deployment), not something a runtime shopping assistant calls. Use a Custom connector against SCAPI's Shopper REST APIs.
PrestaShop
No official MCP exists yet. Use a Custom connector against PrestaShop's Webservice API: authenticate with your API key as the username over Basic Auth, with no password.
SAP Commerce Cloud
No official MCP exists yet. Use a Custom connector against the OCC API.
Wix
Wix has an official MCP, but it's general site-development tooling, not a commerce-shopper MCP. You can still point a Custom connector at it if you want to try it, but keep in mind it wasn't built for shopper catalog and cart use cases.
Manage the tools a connector exposes
A connector's detail page lists the tools its MCP server provides and lets you switch each one on or off.
- Enabled tools are offered to any agent linked to this connector. Disabled tools are never offered to the agent.
- Toggling a tool saves immediately.
For Shopify and Custom connectors, a tool you don't switch off stays enabled, so a new tool the server adds later defaults to on. Shopify has one standing exception: cancel_cart defaults to off on every Shopify connector, because it empties a shopper's cart outright and nothing in the assistant's flow uses it today. Switch it on from the connector's detail page if you need it.
commercetools and Adobe Commerce connectors default new tools to off
A commercetools connector inverts that rule: only the curated product/category search/read and cart read/mutate tools are enabled by default. Any other tool, be it present today or added by commercetools later, stays disabled until you explicitly enable it, because commercetools' full tool surface includes back-office writes (payments, business units, approval flows) that have no place in a shopping assistant's default toolset. An Adobe Commerce connector works the same way, with its own default set (see Default tools).
Refresh tools
The tool list is a cached snapshot. Use Refresh tools to connect to the live server and re-discover what it currently exposes. Do this after you first create a connector (the list starts empty until you refresh) and whenever the server's tools change. If the server can't be reached, the refresh reports a failure and the existing list is kept.
The live server is always authoritative at runtime
The cached tool list drives the on/off switches in the dashboard. At conversation time the agent talks to the live server, so the tools actually available are whatever the server exposes right then, minus the ones you've disabled.
Link a connector to an agent
Connectors are attached to an agent through its configuration version. A version pins which connectors the agent uses.
Open the agent and go to the Capabilities tab. The editor opens on the agent's most recent version. To work on another one, pick it in the agent's name menu, or open All versions there and choose it on the versions page.
In the Connectors card, tick the connectors this version should use. The list starts with the connectors the version already links.
Need a connector that doesn't exist yet? Choose New connector under the list to create one in a dialog. It's ticked as soon as it's created.
Open Save in the header. On V2, for example, Save on V2 adds the new selection to V2, and Save as a new version puts it in V3 and leaves V2 as it is. See Save.
The linked set is saved with the version
Which connectors a version uses is part of each saved state, like its instructions. On a locked version, Save on V2 is disabled, so a new selection goes into a new version. Saving never puts anything live: shoppers get the new set once that version goes live. The connectors themselves stay live: editing a connector's URL, token, or enabled tools takes effect immediately for every version that links it, with no new save needed.
A version's read-only page shows the same Connectors card, ticked and disabled, so you can see what that version has access to.
Where tool usage shows up
When an agent calls a connector's tool, the call and its result are part of the conversation and are visible in two places:
- The Playground: as you chat with a version in the playground, tool calls appear inline in the thread.
- The conversation transcript: opening a saved conversation under Conversations shows the same tool calls in the read-only transcript, so the audit view matches what happened during the chat.
Because the record of what an agent actually did lives in the transcript, you can always see which tools were called and what they returned, even for an older version whose linked connectors have since changed.
Check that a connector answers
A connector's detail page has a Connection card. It shows Last check, when AISA last called the connector, and Last answer, when the connector last answered. Both read "Never" until the first check.
While a live agent uses a connector, AISA calls it every hour. The check connects to the connector's endpoints and lists their tools. For a Shopify or Adobe Commerce connector it also makes one catalog request. If the connector fails two checks in a row, a critical Connector not answering alert opens, a red banner appears on the site's Overview, Widgets and Agents pages, and your admins get an email. The first successful check closes it.
Check now calls the connector once and tells you whether it answered. It works on any connector, including one no live agent uses, but only a connector a live agent uses can open an alert. The button needs the Connectors: Edit permission, and a connector can be checked once a minute. The check changes no setting. Deleting a connector closes its open alert.
The same check is available on the REST API and in the MCP server.
Delete a connector
Delete a connector from the row menu in the Connectors table. It's a soft delete: the connector disappears from the list and the runtime stops offering its tools, but it isn't fully erased, so the historical versions that linked it stay intact. The deletion can't be undone from the dashboard.
Sites
A site is the workspace for one storefront. Create one per store, each with its own agents, conversations, and connectors.
Set up Shopify order webhooks
Send your Shopify orders, refunds and cancellations to AISA by creating three webhooks in Shopify, so sales can be tied to conversations. How they combine with the Shopify pixel's orders.