Submit Log in

commercetools Commerce MCP

by commercetools

1 views

v3.0.1

MIT

Repository Docs npm

Payments & Commerce

ecommercecommercecatalogorderscomposable-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.

Open your agent's MCP configuration file.
Merge the snippet below into it.
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"
      ]
    }
  }
}

Claude Code

Add the server with a single CLI command.

claude mcp add commercetools-commerce-mcp -- npx -y @commercetools/commerce-mcp@latest --tools=all --clientId=CLIENT_ID --clientSecret=CLIENT_SECRET --authUrl=AUTH_URL --projectKey=PROJECT_KEY --apiUrl=API_URL --dynamicToolLoadingThreshold=30

Claude Desktop

Add the server to claude_desktop_config.json (Settings → Developer → Edit Config).

{
  "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"
      ]
    }
  }
}

Cursor

{
  "command": "npx",
  "args": [
    "-y",
    "@commercetools/commerce-mcp@latest",
    "--tools=all.read",
    "--clientId=CLIENT_ID",
    "--clientSecret=CLIENT_SECRET",
    "--authUrl=AUTH_URL",
    "--projectKey=PROJECT_KEY",
    "--apiUrl=API_URL"
  ]
}

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.