Use case · Channels and architecture
Headless commerce AI tools.
22 tools, 18 apps and 4 MCP servers, assigned to this use case by a written definition. 18 of them are built mainly for this job. Filter by type, the platforms they work with and pricing.
- tools listed
- 22
- built mainly for this job
- 18
- apps
- 18
- MCP servers
- 4
Active filters
3 tools match your filters
Showing 1 to 3 of 3, ordered by main purpose first
How results are ordered
Tools whose main purpose is this job come first, then tools where it is a documented feature. Alphabetical within each. This is not a ranking of quality.
There are no paid placements on use-case pages, and no ratings.
Contentful
AppHeadless content platform for building and personalising websites and storefront content, with AI features for content workflows and a composable commerce use case.
Main purposeHeadless, API-first CMS backbone documented for delivering content to headless storefronts and channels via GraphQL APIs.
- Pricing
- Paid
- Price
- Not recorded
- Free plan
- No
- Free trial
- No
Medusa
AppOpen-source commerce platform and managed cloud hosting for developers building custom storefronts, B2B portals and marketplaces, with built-in search, emails and agent tooling.
Main purposeOpen-source headless commerce backend handling carts, orders, inventory and pricing for custom storefronts.
- Pricing
- Paid
- Price
- From $29 a month
- Free plan
- No
- Free trial
- No
VTEX
AppEnterprise commerce platform providing storefronts, order management, marketplace, retail media advertising and customer experience tools for retailers and B2B brands.
Main purposeDocuments headless storefront deployment via FastStore React framework and GraphQL APIs on an API-first commerce platform.
- Pricing
- Paid
- Price
- Not recorded
- Free plan
- No
- Free trial
- No
From the ecommerceguide dataset
Headless and composable tools in numbers
Calculated from all 22 tools on this page's list. Percentages are of the group named.
How tools are assigned to a use case
What this page includes
Commerce platforms and services built for headless or composable (API-first, MACH) stacks, where the listing documents headless or API-first use, and MCP servers for headless commerce platforms such as commercetools, Saleor, Medusa or Commerce Layer.
Not included: Tools that merely have an API. Monolithic platform apps.
How the assignment is made
Each use case has a written definition of what qualifies and what does not. A language model (Claude) reads each tool's listing, its summary and, for MCP servers, the verified integrations and tasks, and assigns it only where the definition fits. It sees no earlier assignments. 670 tools were classified, most recently in Sept 2026.
Main purpose or a feature
“Main purpose” means doing this job is what the tool is for. “A documented feature” means a named feature does the job but the tool's main purpose is something else. Anything weaker is left out. A tool can appear in at most three use cases.
What has to be true first
A tool appears here only once it is listed in its own section: MCP servers after their repository or documentation is verified, apps after their site and listing are reviewed. A use case gets its own page only with at least 10 such tools.
What the facts show
For apps, the pricing model and free plan or trial as recorded from the app's pricing page. For MCP servers, how they run, how they authenticate and who maintains them. “Works with” for apps comes from the listing's own text and is not a tested integration.
Order and corrections
Main-purpose tools first, then alphabetical. No paid placements and no ratings. Corrections: hello@ecommerceguide.com.