Your shop, inside the conversation your customers are already having.

What a shopper can do

The tools follow your audit, but a catalogue with orders usually maps to this. Each line is something a shopper says, and what happens:

• “Find a desk lamp under $60 that ships this week.” → catalogue search, filtered, with stock and delivery read from your API; the assistant says when there are more results.
• “Compare the two oak tables.” → product details for each, summarised so the assistant can answer without pasting raw records.
• “Add the matte black one to my basket.” → cart write, idempotent, on the shopper’s own account.
• “Place the order.” → the assistant shows items, total and delivery, asks for a yes, then calls the order tool once.
• “Where is my order from last week?” → order lookup, scoped to the shopper.
• “Cancel it.” → the guarded tool shows what would be cancelled and refuses until the shopper confirms.

See it work in two minutes

Our open-source sample shop runs publicly at https://demo.apitoagents.com/mcp: ten products, orders, cancellations. Add it to Claude as a custom connector or to ChatGPT as a remote MCP server and ask for a lamp. The confirmation before the order and the refusal to cancel without a yes are exactly what your shop would get. In-memory data, no account needed.

What stays under your control

• Pricing, stock, promotions, tax and shipping come from your shop API on every call. The assistant reads them; it does not decide them.
• Checkout and payment stay where they are. The order tool creates the order in your system; collecting payment follows your existing flow, whether that is a hosted checkout link or a stored method with your rules.
• Account scoping: a shopper sees only their own cart and orders. Authentication uses what your shop supports (API key in the base scope; OAuth as a priced option so each shopper acts as themselves).
• Your brand on the URL: the server lives at a subdomain such as mcp.yourshop.com.

What it takes from your side

A documented shop API. Shopify, WooCommerce, Magento, commercetools, Saleor, Medusa and custom platforms all expose one; the free audit reads the documentation you give it and tells you how ready it is. If documentation is partial, the quote includes a line item for documenting it together. No API keys or customer data are requested before payment. See how the audit works.

What it costs

Setup is one-time, from $499: one shop API, up to three read tools, API-key authentication, one revision round. Write tools such as add-to-cart and place-order are $120 each; a guarded action with a confirmation step adds $200; OAuth adds $300. A typical “search, details, add to cart, place order with confirmation” scope lands under $1,000, and the exact figure comes from your audit. Hosting is $29.99 or $99.99 per month, starting only when the integration is live. Every line item is on the pricing page.

On-site assistant or in-assistant shop?

An AI assistant on your own storefront helps the shoppers who have already arrived. An MCP server reaches the shoppers who ask ChatGPT or Claude first and may never open a browser tab. They are different channels and a shop can run both; this page is about the second one.

For the design behind it, read make your ecommerce shop available in ChatGPT and Claude, and for how retries and cancellations stay safe, idempotency for agent actions.