Angeo MCP Checkout turns a Magento 2 / Adobe Commerce store into a conversational storefront. An AI assistant can search your catalogue, build a cart, calculate real shipping rates, and place an order — all in natural language, and always with the shopper’s explicit confirmation.

It is built on the Model Context Protocol (MCP), an open standard. The same endpoint works with Claude, ChatGPT, Perplexity, Grok, and Mistral Le Chat.

On this page

What it does
Available tools
Connecting your AI assistant
Using it — example prompts
Installing on your store
Safety & how orders are protected
Privacy
Troubleshooting

What it does

Once connected, the assistant can carry out a complete shopping journey against your live store:

browse categories and understand what the store sells;
search the catalogue and compare products with live prices and stock;
build a guest cart;
calculate real shipping quotes for a delivery address;
place the order and return an order number and a payment link.

Nothing is cached, mocked, or synthesised — every figure comes from the store in real time.

Available tools

Ten MCP tools are exposed. Each carries standard MCP annotations, so the assistant knows which ones are safe to call freely and which need your confirmation.

Tool	What it does	Behaviour
`get_store_info`	Store name, currency, countries shipped to, policies	read-only
`list_categories`	The active category tree	read-only
`search_products`	Keyword search with category and price filters	read-only
`get_product`	Full product card: description, attributes, price, stock	read-only
`get_cart`	Current cart contents and totals	read-only
`get_shipping_methods`	Shipping options and costs for a destination	read-only
`create_cart`	Creates a new guest cart	writes
`add_to_cart`	Adds a product by SKU	writes
`set_shipping_information`	Sets address, contact details, and shipping method	writes
`place_order`	Places the order	destructive — always asks you to confirm

Connecting your AI assistant

Your store’s MCP endpoint looks like this:

https://your-store.com/mcp

Claude

Works on Claude Free, Pro, Max, Team, and Enterprise.

Open Settings → Connectors
Click Add custom connector
Name it (e.g. your store name) and paste your endpoint URL
Complete the OAuth consent flow if your endpoint requires authentication
Start a chat and try: “Find me a backpack and help me check out.”

ChatGPT

Requires Plus, Pro, Business, Enterprise, or Edu with Developer Mode enabled. MCP is not available on the free tier.

Since December 2025, OpenAI calls connectors apps. In the UI, look for custom apps.

In Settings, enable Developer Mode
Go to Apps & Connectors → Add custom app (or Import MCP server)
Enter your endpoint URL and complete the OAuth flow if prompted
In a conversation, open the tools menu and toggle the app on for that session

ChatGPT requires manual confirmation before any write action — which matches how this module is designed.

Perplexity

Works on Pro, Max, and Enterprise.

Open Settings → Connectors
Add a custom remote connector and enter your HTTPS endpoint
Scope it as Individual (private) or Organization (shared)

Grok and Mistral Le Chat

Both support remote MCP servers — Grok on paid accounts, Mistral Le Chat on all plans. Find the connectors or integrations section in settings, add a custom remote MCP server, and enter your HTTPS endpoint.

Using it — example prompts

These follow a natural shopping journey and exercise every tool.

Browsing

What do you have in stock?

Show me backpacks under 100.

Tell me more about the second one.

Building a cart

Add it to my cart.

What's in my cart right now?

Shipping and checkout

Ship it to Test User, Teststraat 1, 1234 AB Amsterdam, Netherlands.
Email test@example.com, phone +31 6 00000000.
What are my shipping options?

Use the cheapest one and place the order.

Before placing the order, the assistant will summarise it and ask you to confirm. Once confirmed, you receive an order number and a payment link.

Installing on your store

Merchants install two MIT-licensed modules via Composer:

composer require angeo/module-mcp-server angeo/module-mcp-checkout
bin/magento module:enable Angeo_McpServer Angeo_McpCheckout
bin/magento setup:upgrade
bin/magento setup:di:compile
bin/magento cache:flush

Then configure in the Magento admin under Stores → Configuration → Angeo → MCP Server:

enable the MCP server and the checkout tools;
require a bearer token (see the note below);
set order guardrails — maximum order value and item count;
set the rate limit for order placement.

The module protects you here. If checkout tools are enabled but the endpoint does not require authentication, the checkout tools hide themselves and a critical notice appears in your admin. An unauthenticated checkout endpoint would let anyone on the internet place orders on your store anonymously — so rather than trust you to notice, the module refuses to expose those tools at all. The read-only catalogue tools keep working.

Giving shoppers a one-click connect button

Under Stores → Configuration → Angeo → MCP Server → Claude Connector, enter:

Connector URL — the OAuth-capable HTTPS endpoint issued to your store. This is not your store’s own /mcp path: that endpoint authenticates with a bearer token and has no OAuth, so it cannot be added to an AI assistant directly.
Connector Name — what shoppers see in their connector list.
Landing Page Path — recommended; see below.

Then place the button from Content → Widgets → Add Widget → Add to Claude Button, choosing where it appears (footer, sidebar, a CMS page). No code, no HTML to paste.

Why a landing page. A shopper who does not yet have a Claude account and clicks straight through is bounced to signup — and the prefilled connector details do not survive that redirect. They end up in an empty Claude with no connector and no idea why. So point the button at a page on your own store carrying the Claude Connector Landing Page widget: it explains what will happen, tells account-less shoppers to sign up and come back, and seeds example prompts. Create a CMS page (e.g. shop-with-claude), drop the widget on it, and set that path as the Landing Page Path.

Safety & how orders are protected

Explicit confirmation. place_order is annotated as destructive, so assistants ask the shopper to confirm before it runs. It is never invoked autonomously.
Honest tool annotations. Every tool declares what it actually does — read-only, state-changing, or destructive. Assistants use these hints to decide how much ceremony a call deserves, which is why a catalogue search runs freely while placing an order stops and asks.
The endpoint cannot be left open. Checkout tools refuse to appear unless the MCP endpoint requires authentication. There is no configuration in which an anonymous visitor can place an order.
Guest checkout only. The connector never touches customer accounts, order history, or stored payment methods. Each cart is a fresh guest cart addressed by an unguessable 128-bit masked ID.
No card data, ever. The module does not collect, request, or process payment card details. After the order is created, payment is completed through your store’s own PCI-compliant gateway or a payment link — entirely outside the assistant.
Order guardrails. Configurable caps on order value and item count, plus per-IP rate limiting on order placement.
Authenticated. Requests are authenticated with a bearer token or OAuth; unauthenticated requests are rejected.

Custom MCP servers are third-party services and are not verified by the AI provider. Only connect to endpoints you trust.

Privacy

See the MCP Privacy Policy for full detail. In short: checkout data is passed through to the merchant’s Magento store to place your order; the connector keeps no copy of your personal data, records only minimal technical logs (which tool ran, when, and whether it succeeded — never the contents), and never handles card data.

Troubleshooting

The assistant can’t connect

The endpoint must be served over HTTPS with a valid certificate — plain HTTP is rejected by every client. On a corporate network, a VPN or firewall may block the outbound connection; try disabling it temporarily.

The tools aren’t being called

On ChatGPT, confirm Developer Mode is on and the app is toggled on for the current chat. You may need to ask explicitly: “Use the store tools to find…”

Authentication errors

Check that the endpoint’s OAuth configuration is reachable and the redirect URL is correct. If you require a bearer token, confirm the token is valid and has not been revoked in the Magento admin.

“Tool not found”

Run bin/magento setup:di:compile and flush the cache — new tools are registered through dependency injection and need a recompile.

Part of the open-source angeo.dev Agentic Readiness Suite for Magento 2 / Adobe Commerce. MIT-licensed. Questions: info@angeo.dev