commercetools Knowledge MCP Server

What is commercetools Knowledge MCP Server?

commercetools Knowledge MCP Server is the official, free commercetools MCP server for developer docs and API specs: AI agents can search the documentation, fetch GraphQL and OpenAPI schemas, and validate queries and REST requests, with no authentication.

commercetools offers two MCP servers. Commerce MCP acts on resources such as Carts and Orders in your Project and needs API client credentials. Knowledge MCP, covered here, is a stateless server that serves only public documentation and API schema content, so you can use it without access to any commercetools Project. It is meant to reduce ramp-up time and help AI coding assistants write correct commercetools code instead of guessing field names.

How to use commercetools Knowledge MCP Server?

The server is available over Streamable HTTP only (no local stdio, no SSE) at:

https://docs.commercetools.com/apis/mcp

No API key, sign-in or Project is needed. commercetools suggests commercetools-knowledge as the local server name.

Claude Code

claude mcp add --transport http commercetools-knowledge https://docs.commercetools.com/apis/mcp

Claude Desktop and claude.ai

Go to Customize > Connectors > Add custom connector, set the name to commercetools-knowledge and the remote MCP server URL to https://docs.commercetools.com/apis/mcp.

Cursor

In Cursor Settings > Tools & MCP > New MCP Server, add:

{
  "mcpServers": {
    "commercetools-knowledge": {
      "type": "http",
      "url": "https://docs.commercetools.com/apis/mcp"
    }
  }
}

VS Code

Add it to your user mcp.json or a workspace .vscode/mcp.json:

{
  "servers": {
    "commercetools-knowledge": {
      "type": "http",
      "url": "https://docs.commercetools.com/apis/mcp"
    }
  }
}

For clients that only support local stdio servers, commercetools documents wrapping the endpoint with mcp-remote:

"commercetools-knowledge": {
  "command": "npx",
  "args": ["-y", "mcp-remote", "https://docs.commercetools.com/apis/mcp"]
}

JetBrains IDEs can connect through an MCP-capable plugin such as AI Assistant.

Key features of commercetools Knowledge MCP Server

• Semantic documentation search across commercetools docs, filterable by content type and by product (Composable Commerce, Frontend, Checkout, Connect, InStore).
• Per-resource GraphQL schemas with stubbed types you can expand on demand, so the agent loads only what it needs.
• Per-resource OpenAPI specs in read, write or unified variants for building REST requests or clients.
• Offline validation of GraphQL queries/mutations and REST requests against the public commercetools schemas, before anything touches a Project.
• A commercetools-developer-tips prompt that loads conventions such as key vs id, centAmount minor units, LocalizedString, query predicates, sorting and common pitfalls.
• Free and anonymous: no authentication, limited to 100 requests per 15 minutes per IP address.

commercetools Knowledge MCP Server tools

The server exposes six tools in three groups.

• Documentation: commercetools-documentation-search returns documentation chunks semantically similar to your question; commercetools-documentation-by-id fetches one full entry when you already have its content ID (for example ctp:api:type:ProductProjection).
• Schemas: commercetools-graphql-schemata returns a partial GraphQL schema for a resource such as Cart; commercetools-oas-schemata returns a self-contained OpenAPI spec for a resource such as api-Customer-write.
• Validation: commercetools-graphql-validate checks a query or mutation and returns errors with line and column; commercetools-rest-validate checks method, path and body, including update-action discriminators. Both are read-only and validate against the public schema, not your Project's configuration.

The documented workflow is search, then fetch the schema, then validate, then generate code or execute the call.

Use cases of commercetools Knowledge MCP Server

• Implementing a GraphQL feature: "How do I create a cart with an initial product? Write and validate the mutation."
• Building a REST call: "Find the endpoint to update customer details and validate a changeEmail update action."
• Concept lookups: "What is the difference between a Product and a ProductProjection?"
• Project scaffolding: "How do I set up Checkout? List the resources involved and their schemas."
• Catching hallucinated fields: have the agent validate every generated query before it lands in your codebase.

Troubleshooting commercetools Knowledge MCP Server

• 429 Too Many Requests: you hit the 100 requests per 15 minutes per IP limit (shared with the Knowledge REST API). Wait for the time in the Retry-After header.
• Empty search results: rephrase the input more broadly or more specifically, and loosen contentTypes or products filters.
• Invalid resource name: check the spelling; MCP clients can see the allowed resourceName values in the tool schema.
• Slow responses: the server runs in europe-west1, so other regions may see higher latency.