commercetools Partner ConnectorConnect commercetools Without Constraints
IntelliPaaS seamlessly connects commercetools with your core business systems, enabling no-code integration for composable commerce, order orchestration and catalogue management across cloud, on-prem and hybrid environments.
commercetools has the most developed permission model of any commerce MCP server we have assessed, and its managed servers reached general availability in July 2026. You create a server against a project and the endpoint URL comes back in the response, with the tool list declared explicitly in the configuration rather than exposed wholesale — tools are named by verb and resource, so a read-only server is simply the read preset or a hand-picked list. On top of that sit field filtering and redaction, customisable tool descriptions, a pinned major version and an enabled or disabled state. Three authentication paths are supported: a static bearer token, OAuth client credentials with automatic discovery, or commercetools Identity where end users sign in individually. A self-hosted package offers the same tools for local and embedded use, and a separate knowledge server covers documentation search.
commercetools integration capabilities
- Read products, categories, orders, carts, customers and payments across 40 or more resource groups.
- Create and update resources where the configuration allows it.
- Restrict a server to a named tool list, or to the read-only preset.
- Apply field filtering and redaction so sensitive attributes never leave the platform.
- Pin a major version and enable or disable a server without deleting it.
- Search documentation and API reference through the separate knowledge server.
These capabilities let a composable commerce backend be driven by the systems around it, with exactly the tool surface you choose to expose. IntelliPaaS handles field mapping, pagination and data type transformation automatically.
Common integration scenarios
- Sync product, price and inventory data from the ERP or PIM into commercetools.
- Push orders into NetSuite, Business Central or SAP and write fulfilment status back.
- Reconcile payments and refunds against Stripe, Adyen or PayPal records.
- Keep customer records aligned between commercetools and the CRM.
- Load order and catalogue performance into Power BI or Snowflake.
These scenarios address the most common friction in composable commerce — catalogue and order data spread across services with bespoke glue between each — by automating the flows between commercetools and the platforms around it.
Deployment & security
Flexible deployment is essential for organisations operating in regulated industries or jurisdictions with strict data residency requirements. IntelliPaaS supports private cloud and on-premise deployments with full regional data sovereignty, and because a managed commercetools server is issued per project, residency follows the region that project already runs in. All deployment modes receive the same feature set, connector library and support tier, with no capability trade-offs based on deployment choice.
Why IntelliPaaS
- No-code to pro-code flexibility for all integration needs.
- End-to-end security with explicit per-tool allowlists plus field filtering and redaction.
- Three authentication paths, including per-user sign-in with no shared API client.
- Enterprise-grade observability with monitoring, alerting and audit logging.
Frequently connected apps
Shopify
BigCommerce
Adobe Commerce
SAP Commerce Cloud (Hybris)
WooCommerce
Stripe
PayPal
NetSuite
Microsoft Business Central
ShipStationFrequently asked questions
What authentication does the connector use?
Three options on managed servers: a static bearer token you fetch yourself, OAuth 2.0 client credentials with automatic discovery, or commercetools Identity where end users sign in individually and no API client is needed. Token validity is capped at thirty days.
How do I keep it read-only?
Either apply the read-only permission preset, or declare exactly the tools the server exposes in its configuration — they are named by verb and resource, so the allowlist is explicit. commercetools recommends enabling only what a workflow needs rather than everything.
Is there a self-hosted option?
Yes. An executable package runs locally or embedded in an agent framework and exposes the same tools and field filtering as the managed servers. A separate knowledge server covers documentation and API search and needs no project access.
Can I deploy on-premise or in a private cloud?
Yes. Cloud (SaaS), private cloud in your own VPC, and fully on-premise or air-gapped deployments are all supported, with full feature parity across every mode.
Is my data secure?
Data is encrypted in transit and at rest, and IntelliPaaS is GDPR-ready. Per-tool allowlists, field filtering and redaction limit what ever leaves the platform, and on-prem modes keep commerce data inside your own infrastructure boundary.