Skip to content
commercetools Commerce MCP

commercetools Commerce MCP

by commercetools
Released
v3.0.1
MIT
Repository Docs npm
Payments & Commerce

Summary

Official commercetools MCP server exposing products, carts, orders, customers and the rest of the Composable Commerce API as scoped, selectable agent tools.

Features

  • Read and write products, carts, orders and customers via the Composable Commerce API
  • Per-tool scoping with --tools, including an all.read read-only mode
  • Dynamic tool loading threshold to keep large projects manageable
  • Client-credentials or pre-issued access-token authentication
  • Ships a commerce agent alongside the MCP server for agent frameworks

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it.
  3. Restart the agent — the "commercetools Commerce MCP" tools will be available.
{
  "mcpServers": {
    "commercetools-commerce-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@commercetools/commerce-mcp@latest",
        "--tools=all",
        "--clientId=CLIENT_ID",
        "--clientSecret=CLIENT_SECRET",
        "--authUrl=AUTH_URL",
        "--projectKey=PROJECT_KEY",
        "--apiUrl=API_URL",
        "--dynamicToolLoadingThreshold=30"
      ]
    }
  }
}

Description

commercetools Commerce MCP connects an MCP client — Claude Desktop, Cursor, VS Code or an agent framework — to a commercetools project, so an agent can read and modify catalogue and order data through the Composable Commerce API. The repository ships both the MCP server and a commerce agent for use inside agent frameworks.

Scope control is the point

Rather than handing an agent every endpoint, tools are selected explicitly with the --tools flag: all for the full surface, all.read for a read-only server, or a precise list such as products.read,products.create. On large projects a --dynamicToolLoadingThreshold keeps the exposed tool list manageable instead of flooding the client's context. Running production credentials against all.read is a realistic way to let an agent investigate a catalogue without any risk of writes.

Authentication

Two modes are supported. client_credentials (the default) takes --clientId and --clientSecret from an API client you create in the Merchant Center. auth_token takes a pre-existing --accessToken, with client id and secret optional. Both also need --projectKey, --authUrl and --apiUrl for your region.

Who it is for

Teams already on commercetools Composable Commerce who want agents doing catalogue maintenance, order lookups, price and promotion checks or customer-service investigation against real project data — with the blast radius set by which tools were enabled at launch.

Published as @commercetools/commerce-mcp under the MIT licence.

Related MCP Servers

MCP: Shippo

by Shippo

Shippo's official MCP server for multi-carrier shipping — compare rates, buy labels, track parcels and validate addresses, with reads free and purchases gated.

Payments & Commerce

MCP: Adyen MCP Server

by Adyen

Adyen's official MCP server (alpha) — create checkout sessions and payment links, refund or cancel payments, and manage merchant accounts and terminals.

Payments & Commerce

MCP: Square

by Square

Square's official MCP server — manage catalog, orders, payments, customers, and inventory from an AI client.

Payments & Commerce
Browse all MCP servers →