commercetools Knowledge MCP

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Free, no-auth MCP server that lets AI agents search commercetools docs, fetch GraphQL and OpenAPI schemas, and validate API calls.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "commercetools Knowledge MCP": {
      "url": "https://docs.commercetools.com/apis/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (6)

• commercetools-documentation-search read-only

  Retrieves documentation content chunks that are semantically similar to the input. Use this tool to find domain concepts, business behavior explanations, and reference material from the commercetools documentation. Inline links in the content use markdown format [text](url). The URL usually points to the commercetools documentation portal but can also point to API reference docs or external resources. Relative links resolve against "https://docs.commercetools.com". Appending ".md" to a documentation URL fetches the markdown source of that page. Example: a relative link "./api/predicates/query" resolves to "https://docs.commercetools.com/api/predicates/query.md" If you are requesting only one specific content type, pass the same value for crowding and limit. The mean size of a documentation chunk returned is in the range of 500-600 tokens.

  Parameters:

  • query (required) — string — The text to find semantically similar content to. Full sentences describing the context of the situation or problem yield better results than just keywords.
  • limit — number — The maximum number of results to return across all content types.
  • crowding — number — The maximum number of results to return per document type. Avoids over-representation of certain content types.
  • products — array — return only content about the given products. For example, if your application uses commercetools Frontend, add "Frontend" to the defaults, or, if you are not using the OOTB Checkout UI, remove "Checkout"
  • contentTypes — array — return only the given content types to focus or expand the defaults. "apiType" and "apiEndpoint" return natural language descriptions of the REST API surface. "guidedDocs" includes best practice guides, tutorials, and learning content. "referenceDocs" covers reference material. "userDocs" is end-user-facing documentation. "otherDocsPage" covers content that does not fit the other categories. "Skill" includes reference content linked from agent skills.
  • excludeProducts — array — exclude the given products from the results.
  • excludeContentTypes — array — exclude the given content types from the results.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• commercetools-graphql-schemata read-only

  Fetches a partial commercetools GraphQL schema for a given resource. Use this tool to retrieve the GraphQL type definitions needed to construct queries or mutations against commercetools. Each resource name is prefixed with the GraphQL SDL it belongs to (e.g. `gql-sphere-Product` for sphere API, `gql-il-Cart` for integration layer API), reflected in the "resourceName" enum. For each stubbed type in the schema, the full schema for that type can be fetched by invoking the tool again with the resource name specified in the comment related to the stubbed type. The comment looks like this: Stub of the `{nameOfStubbedResource}` resource. fetch the full subschema via the MCP resource name `{nameOfTheResource}`. The returned schema contains descriptions but no "implements" Interface information and no deprecated query types. Conventions and predicate examples for commercetools GraphQL are available in the `commercetools-developer-tips` MCP prompt.

  Parameters:

  • resourceName (required) — string — Name of a commercetools API resource, prefixed with its GraphQL SDL (e.g. gql-sphere-Product, gql-il-Cart). The full set of available resources is provided by the parameter enum.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• commercetools-graphql-validate read-only

  Validates a GraphQL query or mutation against the official commercetools public schema, returning syntax and schema errors with line/column locations. Doesn't validate project-specific schema.

  Parameters:

  • query (required) — string — The GraphQL query or mutation document to validate.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• commercetools-oas-schemata read-only

  Fetches a partial commercetools OpenAPI spec for a given commercetools resource. Use this tool when you need the detailed REST schema of a resource to construct requests or generate a REST client. The returned spec is self-contained and valid for everything regarding that resource. It contains descriptions but they are not comprehensive. Each resource may be available as a read variant, write variant, or unified spec, reflected in the "resourceName" enum. Conventions and predicate examples for commercetools REST APIs are available in the `commercetools-developer-tips` MCP prompt.

  Parameters:

  • resourceName (required) — string — Name of the commercetools resource you would like to get a OAS schema for.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• commercetools-documentation-by-id read-only

  Fetches a single documentation content entry from the commercetools documentation content API by its ID. Use this tool when you already have a content ID (for example, one returned by `commercetools-documentation-search`) and want to retrieve the raw content as a string.

  Parameters:

  • id (required) — string — The ID of the documentation entry to fetch. Typically the identifier returned by the documentation search tool.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• commercetools-rest-validate read-only

  Validates REST API requests (method + path + body) against commercetools OpenAPI specifications offline. Returns detailed errors with suggestions for invalid requests. This tool checks: - Path exists in the API - HTTP method is allowed for that path - Request body matches the expected schema (types, required fields, enums, etc.) - Discriminator fields (like 'action' in update requests) are valid Use this before making actual API calls to catch errors early.

  Parameters:

  • method (required) — string — HTTP method for the request.
  • path (required) — string — Request path (e.g., /my-project/products). Include the project key as the first segment.
  • apiKey (required) — string — API identifier. Use API names (api, import, checkout, etc.) or resource keys (api-Product-read). The base API key will be extracted automatically.
  • body — string — Request body as a JSON string (optional, required for POST/PATCH/PUT requests that expect a body).

  Hints: read-only yes · destructive no · idempotent yes · open-world no

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.