The integration
What is the Dreem MCP?
Dreem is a product-photography engine built for apparel and wearables. The Dreem MCP exposes that engine through an MCP server — the Model Context Protocol, the open standard that lets AI assistants like Claude call external tools directly. Connect the server once at https://mcp.dreem.ai/mcp, and your assistant can generate Dreem shots for you without you ever leaving the conversation.
It means there's no separate app to switch to and no UI to learn. You describe the shot you want the way you'd describe it to a teammate, and the work happens on your Dreem account behind the scenes.
Why generate from your assistant
Most product-photo workflows make you leave whatever you're doing, open a tool, upload, configure, export, and come back. With the MCP, the generation lives where you're already working. Drafting a product description in Claude? Ask for the matching on-model shot in the same thread. Iterating on a launch? Generate the ghost-mannequin image and the packshot side by side without context-switching.
And because it's the same Dreem engine underneath, everything it produces — on-model shots, ghost-mannequin images, packshots, short video — comes back consistent with the rest of your catalog.
What it's good at — and what to know
The honest version, because overselling helps no one.
Strong today
- One-time connect, then plain-language requests — no code
- The full Dreem kit from a single product photo
- Consistent output that matches shots made anywhere else in Dreem
Good to know
- Built for apparel and wearables — things people wear
- You need a Dreem account; generations use your plan's credits
- Setup shown here uses Claude's custom connector; other MCP clients use the same URL