01 · Records and state owned
Projects, products, categories, inventory, customers, carts, orders, discounts, subscriptions, business units, applications, import containers, MCP server configurations, tool customizations, and usage telemetry.
commercetools
commercetools
Included because its project-scoped Commerce MCP combines catalog, cart, order, and customer operations with centrally enforced tool and field controls for composable commerce interfaces.
Commerce & paymentsSystem of recordBYO-UI-ready platform
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
02 · Data you can retrieve
Read enabled Project resources through resource-specific tools; managed configurations can filter tools, returned fields, parameters, and JSON output before commerce data reaches an agent.
03 · Actions and write paths
Create and update enabled commerce resources, including carts and orders; the reviewed Commerce MCP catalog exposes read, create, and update families rather than delete tools.
04 · Authentication and permissions
Managed servers use API Clients for machine actors or Early Access Identity Accounts for human-in-loop access. Self-hosted Commerce MCP accepts client credentials or existing bearer tokens.
05 · Monitoring, approval, and recovery
Managed configurations centrally enforce tool selection, parameter overrides, field redaction, output formatting, and version pins. Platform Insights tracks each server’s usage; self-hosted enforcement remains locally controlled.
06 · Limits and caveats
Production use requires licensing, and Identity Account authentication remains Early Access. Major versions are pinned but can be automatically advanced after an old version is retired.
First-party access
Documented surfaces
commercetools GraphQL API ↗commercetools exposes GraphQL queries and mutations over commerce resources. Project scopes, API-client permissions, expansion behavior, complexity, and mutation consequences apply.Source: GraphQL APIMCP / agent surface ↗Verified first-party provider MCPAPI ↗Developer accessDeveloper docs ↗SDKs and platform guidanceEvents / extensions ↗Webhooks, apps, or extensionsProduct ↗Native platform experience
Agent access
MCP support
Official MCP serverOfficial Commerce MCP plus separate Knowledge MCPManaged MCP Servers generally available since July 16, 2026; self-hosted Commerce MCP also supports production use
Support: Official MCP server
Read scope: Project-scoped product, cart, order, customer and other Commerce API resources with configurable tool allowlists and API-client scopes for read-only or read/write access
Write scope: Commerce MCP supports explicitly selected create and update tools across documented commerce resources; read-only or read/write behavior is controlled by tool allowlists and API Client scopes. Delete tools were not listed in the reviewed catalog.
Authentication: Machine connections use a scoped commercetools API Client and bearer-token flow. Managed human-in-loop sessions may instead use an Identity Account, currently in Early Access on managed servers.
Approval boundary: Show the Project, actor, resource, proposed create or update payload, and affected price, inventory, customer, cart, or order state in advance before committing consequential commerce changes.
Protocol does not erase product boundaries.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Data access4
Action access4
Event access4
Identity4
Governance4
Agent access4
UI extensibility3
Portability4
Observability3
Documentation5
Proposed customer-shaped experiences
What customers could create on top.
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that commercetools ships them.
Single-platform patterns
- Composable catalog and commerce operations workbench
- Revenue reconciliation console
- Commerce operations cockpit
- Customer-resolution workbench
Multi-platform compositions
- commercetools + CRM or support system: revenue reconciliation console
- commercetools + lifecycle platform + analytics or finance system: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
6 recorded sources
MCP / agent-role validationRepresentative source
https://docs.commercetools.com/dev-tooling/mcp/commerce-mcp ↗Commerce MCP became available for production projects in June 2026 and can run locally or remotely. Distinguish it from the documentation-focused Knowledge MCP and note that implementation details remain subject to…
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Targeted first-party MCP/agent-role review; broader API inventory retained
APISource inventory
https://docs.commercetools.com/api/ ↗First-party API reference or API overview recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
Developer docsSource inventory
https://docs.commercetools.com/ ↗First-party developer documentation or platform overview.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Developer docsSource inventory
https://docs.commercetools.com/api/graphql ↗Reverified the named access facet exactly as bounded by the reviewed first-party record.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
HomepageSource inventory
https://commercetools.com/ ↗First-party product homepage used to confirm product identity and current positioning.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Webhooks / extensionsSource inventory
https://docs.commercetools.com/api/events ↗First-party webhook, event, SDK, embedded-app, or extension documentation.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Verified fact
Tied to cited first-party evidence reviewed for this profile.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.