Pimcore's integration model is build on the platform. Partners and in-house teams connect it to other systems with Symfony bundles, Datahub endpoints (GraphQL, REST, file export, webhooks), the Data Importer and the PHP API S61 S32. Pimcore itself ships only a few packaged third-party connectors. Because DAM, PIM and CMS share one repository, a link between a product and its images is internal and needs no connector S95. See DAM vs PIM, MAM and CMS.
Marketplace / app directory
- Technology Connectors page: 19 technology partners in three groups (technology partners, data management, experience management). Listings link to partner sites, and the page does not say who built or supports each integration S83.
- Pimcore Store (store.pimcore.com): sells the Professional edition and Learning Hub access S14 S84. A browsable extension marketplace with third-party bundles: Not public (none found).
- How extensions are built: Symfony bundles distributed through Composer (
pimcore/*packages; Enterprise packages come from a private repository, repo.pimcore.com) S3 S16. Studio UI plugins use the Studio SDK and plugin slots S60 S11. Under POCL, any distribution of derivatives must follow the Pimcore Contributor License Agreement S4. - Many community bundles are published on Packagist and GitHub by agencies. They are not vetted by Pimcore and are not listed here.
Native connectors
"Built by" is what the cited source states. Modules marked Pimcore are official bundles from the editions table S2.
| Category | Target | Built by (vendor / partner) | Notes |
|---|---|---|---|
| Creative | Desktop applications (Photoshop, Office…) via Direct Edit | Pimcore (Enterprise) | Opens the asset in the locally associated app and re-uploads changes; not an Adobe CC panel S49 S50 |
| Creative | Adobe Creative Cloud, Figma, Canva | — | Not public: no official connector found S83 |
| CMS / DXP | Pimcore Documents (built-in CMS), Headless Documents | Pimcore (core / Enterprise) | Same repository; Headless Documents expose content through Datahub S95 S3 |
| CMS / DXP | WordPress, Contentful, Sitecore, AEM Sites | — | Not public: no official connector found S83 |
| PIM / e-commerce | Pimcore PIM/MDM data objects, E-Commerce Framework | Pimcore (core / Enterprise) | Native, shared data model S95 S2 |
| PIM / e-commerce | Productsup (syndication to marketplaces and channels) | Pimcore bundle (Enterprise) + technology partner | Datahub Productsup adapter S81 S83 |
| PIM / e-commerce | Shopware | Technology partner | Listed as a partner; connector builder not stated S83 |
| PIM / e-commerce | Shopify, Adobe Commerce, Salesforce Commerce Cloud, Akeneo | — | Not public: no official connector (third-party agency connectors exist, not vendor-listed) S83 |
| Print / publishing | priint:suite (WERK II), PIM2Print (Active Publishing), InBetween, PDFreactor (RealObjects) | Technology partners | Catalogue and print publishing S83. Pimcore's own Web-to-Print module is Enterprise S3 |
| Translation | DeepL, translations.com (TransPerfect GlobalLink) | Pimcore bundle (Enterprise) + partners | Translation Provider Interfaces, including asset metadata S80 S83 |
| Office & collaboration | Microsoft Teams, Slack | — | The DAM page mentions workflow "integration with third-party tools like Teams and Slack" S1; no connector is documented Unverified (marketing claim only) |
| Marketing automation / social | trbo, Personify XP (personalisation) | Technology partners | S83 |
| Storage / identity | Amazon S3 and other Flysystem adapters | Pimcore (core) + Flysystem adapters | Asset, thumbnail and version storage S33 |
| Storage / identity | OpenID Connect providers (e.g. Okta, OneLogin) | Pimcore (Enterprise) | SSO for Studio and portals S78 S44 |
| CDN | Fastly (built-in invalidation), CloudFront (frontend prefix) | Pimcore (core) | S10 S33 |
| Hosting | Upsun | Technology partner | Platform behind Pimcore PaaS S16 S83 |
AI & agent ecosystem
- MCP servers (experimental, self-hosted on each instance; none hosted by Pimcore):
- Datahub Simple REST MCP (Enterprise):
https://{host}/pimcore-datahub-webservices/simplerest-mcp, switched on per configuration. Tools:pimcore_datahub_list_configs,pimcore_datahub_get_config_schema,pimcore_datahub_search,pimcore_datahub_tree_items,pimcore_datahub_get_by_id,pimcore_datahub_get_query_syntax, plus asset resource templates for binaries. Read-only, authenticated by API key or OAuth token S72 S70. Experimental MCP support was first announced in 2025.4 S8. - Pimcore Agent MCP tool groups at
/pimcore-mcp/agent/<group>, e.g.pimcore-assets-read(get, list, search and stage assets),pimcore-assets-write(metadata proposals with human approval) andpimcore-assets-direct-write(upload/update). Also groups for data objects, documents and tags. External clients such as Claude Desktop or Cursor connect with a personal access token, and Pimcore permissions apply S55 S56. The Agent bundle is installed asdev-mainfrom a non-public repository; edition and support level Unknown S54 S90. - Copilot MCP tools: four handlers to list, run, follow and cancel Copilot automation actions, for wiring into an MCP server (Enterprise) S82.
- OAuth 2.1 with discovery metadata lets standards-based MCP clients sign in as a Pimcore user S57.
- Datahub Simple REST MCP (Enterprise):
- Pimcore Copilot (Enterprise): automation and interaction actions using Hugging Face models and OpenAI-compatible APIs S51 S52. Hugging Face and OpenAI are listed as technology partners S83.
- Pimcore Agent: chat agents in Studio. The default inference path is GitHub Copilot (Claude Haiku 4.5) and other providers are configurable S54.
- Embeddings: semantic and image search with any OpenAI-compatible or custom embedding provider (Enterprise, experimental) S41.
- llms.txt: none on pimcore.com or docs.pimcore.com (HTTP 404) S93. Docs MCP server for the documentation: Not public (none found).
- Claude / ChatGPT directory connectors: Not public (none found).
Integration platforms
- n8n: listed as a technology partner S83. The Enterprise Workflow Automation Integration bundle exports n8n workflow blueprints from Datahub GraphQL and webhook configurations S79. No Pimcore page exists in n8n's integrations directory (HTTP 404) S96.
- iPaaS.com: listed as a technology partner S83.
- Zapier, Power Automate: named on the DAM page as automation tools Pimcore integrates with S1. No official Zapier app was found (HTTP 404) S96 Unverified (connection would go through webhooks or HTTP calls; inference).
- Make, Workato, MuleSoft: Not public (no listing found).
- Generic path for any iPaaS: Datahub GraphQL or Simple REST in, Datahub Webhooks out S62 S73.
Partners
- Solution partner programme, tiers Global, Strategic, Platinum, Gold, Silver. Silver partners may specialise in a single domain such as DAM. Benefits include the Pimcore Space Center, the Pimcore Stars Program, training, webinars and co-marketing. Requirements and fees are in a gated Partner Guide (Not public) S85.
- Partner count: "170+" or "over 180" solution partners, both figures on the same about page S20; about 150 certified partners in 2022 S18.
- Technology alliances: the 19 partners above S83.
- Partner directory: Find a solution partner.
Native integrations (summary)
None documented No connector to a tool of the wiki’s tracked list is documented as official in the sources checked (verified 2026-10-29).