Skip to content
ecommerceguide.
Explore ecommerceguide.

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

4 tools match your filters

Showing 1 to 4 of 4, 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.

  1. Commerce Engine Skills

    MCP server

    by Commerce Engine

    Agent skills and Claude Code/Cursor plugins that guide AI coding agents to build storefronts on Commerce Engine, covering setup, auth, catalog, cart, orders, SEO and webhooks.

    Main purposeProvides agent skills and plugins for building storefronts on the API-first Commerce Engine platform, covering auth, catalog, cart, orders and webhooks.

    Runs
    Not recorded
    Auth
    API key
    Maintainer
    Official
    View profile for Commerce Engine Skills

  2. commercetools MCP Essentials

    MCP server

    by commercetools

    Official commercetools MCP server and agent toolkit giving AI clients read and write access to products, categories, carts, orders, customers, inventory and payments.

    Main purposeOfficial MCP server for commercetools, an API-first headless commerce platform, exposing its catalogue, cart and order APIs to agents.

    • commercetools logocommercetools
    Runs
    Local · stdio, HTTP
    Auth
    API key, Token
    Maintainer
    Official
    View profile for commercetools MCP Essentials

  3. Saleor MCP

    MCP server

    by Saleor Commerce

    Read-only MCP server for Saleor Commerce that lets AI clients fetch products, customers, orders, channels and stock data from a Saleor GraphQL API.

    Main purposeMCP server for the Saleor headless commerce platform, querying its GraphQL API for products, orders and customers.

    • Saleor logoSaleor
    Runs
    Local or hosted · HTTP
    Auth
    API key
    Maintainer
    Official
    View profile for Saleor MCP

  4. Unchained Engine

    MCP server

    by Unchained Commerce

    Open-source headless Node.js ecommerce engine whose GraphQL API package includes an MCP server, letting AI clients work with products, orders and users.

    Main purposeIt is an open-source headless, GraphQL-API-first commerce engine positioned as an alternative to commercetools or Medusa.

    Runs
    Not recorded
    Auth
    Not recorded
    Maintainer
    Official
    View profile for Unchained Engine

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.

Tools listed
22
Built mainly for this job
18 82%
Apps
18 82%
MCP servers
4 18%
Apps with a free plan
0 0%
MCP servers published by the platform itself
4

Type

Works with

Where a listing names the platform. A count of listings, not of usage.

App pricing model

Percentages are of apps.

Further reading

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.