Build an AI-first webshop

An AI-first webshop treats AI as core infrastructure rather than a bolt-on widget. With Cartwright you scaffold one in a single command and get an AI-native admin (draft copy, generate SEO, answer support), a storefront assistant, and an MCP server that exposes your shop’s operations as typed tools agents can call. Because you own the codebase, you decide exactly what the AI can see and do.

Who it’s for

Founders and developers who want AI woven through admin, storefront, and APIs — not a chatbot stapled on at the end.

AI-native admin

Product copy, SEO metadata, and answers drafted in the admin; every AI write goes through the same tool registry + audit log as a human.

Storefront assistant

A customer-facing assistant that can search, add to cart, and complete orders within the scopes you grant.

MCP server

A public /api/mcp endpoint with a typed tool catalogue — external agents act on your shop natively, no scraping.

You own it

MIT source on your infra; swap AI providers (Anthropic, Gemini, local Ollama) in one file.

Frequently asked

What does “AI-first” actually mean here?
The admin, storefront, and API surfaces are all built around AI from the start: an AI-native admin, a storefront assistant, and an MCP tool registry — not a single chatbot feature.
Can I control what the AI is allowed to do?
Yes. Every AI action runs through a typed tool registry with scopes and an audit log, so you grant exactly the capabilities you want and can revert any change.
Do I have to use a specific AI provider?
No — Anthropic and Gemini are wired in, and local Ollama is supported. Providers swap in one file.

Start in one command

npx create-cartwright@latest my-shop

See the docs or compare Cartwright.