commercetools MCP (Knowledge MCP + Commerce MCP)
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
Endpoint
Hosted endpoint · transport
Connect
This is a remote MCP server — point an MCP client at the endpoint URL. Clients with native remote support (Claude, Cursor, VS Code, …):
For stdio-only clients (older Claude Desktop, etc.), bridge with mcp-remote:
If the server requires authentication, add the provider's token/header (e.g. an X-API-Key) per its docs. A quick reachability check:
Tools
commercetools-documentation-search— 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 resourcommercetools-graphql-schemata— 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 icommercetools-graphql-validate— 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.commercetools-oas-schemata— 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 varicommercetools-documentation-by-id— 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.commercetools-rest-validate— 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 validcreate_applications—create_attribute_groups—create_bulk—create_business_units—create_cart_discounts—create_carts—create_categories—create_channels—create_custom_objects—create_customer_groups—create_customers—create_discount_codes—create_extensions—create_inventory—create_orders—create_payment_integrations—create_payment_methods—create_payments—create_product_discounts—create_product_selections—create_product_tailoring—create_product_types—create_products—create_quote_requests—create_quotes—create_recurring_orders—create_reviews—create_shipping_methods—create_shopping_lists—create_staged_quotes—create_standalone_prices—create_states—create_stores—create_subscriptions—create_tax_categories—create_transactions—create_types—create_zones—read_all—read_applications—read_attribute_groups—read_business_units—read_cart_discounts—read_carts—read_categories—read_channels—read_custom_objects—read_customer_groups—read_customer_search—read_customers—read_discount_codes—read_extensions—read_inventory—read_messages—read_orders—read_payment_integrations—read_payment_methods—read_payments—read_product_discounts—read_product_projections—read_product_search—read_product_selections—read_product_tailoring—read_product_types—read_products—read_project—read_quote_requests—read_quotes—read_recurring_orders—read_reviews—read_shipping_methods—read_shopping_lists—read_staged_quotes—read_standalone_prices—read_states—read_stores—read_subscriptions—read_tax_categories—read_transactions—read_types—read_zones—replicate_carts—update_applications—update_attribute_groups—update_bulk—update_business_units—update_cart_discounts—update_carts—update_categories—update_channels—update_custom_objects—update_customer_groups—update_customers—update_discount_codes—update_extensions—update_inventory—update_orders—update_payment_integrations—update_payment_intents—update_payment_methods—update_payments—update_product_discounts—update_product_selections—update_product_tailoring—update_product_types—update_products—update_project—update_quote_requests—update_quotes—update_recurring_orders—update_reviews—update_shipping_methods—update_shopping_lists—update_staged_quotes—update_standalone_prices—update_states—update_stores—update_subscriptions—update_tax_categories—update_types—update_zones—
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.
Work with this as data
Every MCP server here is available over the APIs.io API and to AI agents over MCP.