INTEGRATIONS · AGENT PROTOCOLS
MCP — Model Context Protocol
The connection Claude and other agents call directly.
Status
Live
Connection method
Hosted MCP server
Time to live
Same day on Shopify, days elsewhere
How it connects
MCP is the open standard for exposing data and actions as tools an AI can call. We deploy and host an MCP server over your catalog, so agents can query products, compare them, and complete an order — one deployment serving every MCP-speaking client.
What goes live
- Hosted, monitored MCP server on your catalog
- Product, availability, and pricing tools
- Checkout action wired to your commerce backend
- Usage and query analytics
How setup runs
Connect the catalog
We point the server at your commerce backend through whichever platform connector applies.
Define the tools
Product search, product detail, availability, and the order action — shaped so an agent can compare accurately rather than guess.
Host and monitor
We run the server, keep it in sync as your catalog changes, and monitor query volume and errors.
Distribute
The endpoint is registered where agents look for it, so one deployment serves every MCP-speaking client.
What we read
- Whatever your catalog exposes — products, availability, pricing, and the checkout action
Scope
MCP gets an agent to your catalog. It does not by itself make a model recommend you — that is discovery work, and it runs in parallel.
Questions
Is MCP only for Claude?
No. It is an open protocol adopted well beyond Anthropic, which is why one deployment reaches many clients. Claude is simply the surface where a connection is mandatory rather than optional.
Do we host it or do you?
We host and monitor it by default. Self-hosting is possible for teams with that requirement.
What happens when our catalog changes?
The server stays in sync with your commerce backend, so price, availability and new products are reflected without a redeploy.