Best-fit use cases
Implementation
A reliable four-step workflow
Define the tool
Use a clear tool name such as generate_branded_image with a strict input schema.
Map templates
Let the agent select only from approved template identifiers and documented layer names.
Call Duply
The MCP tool validates inputs and sends a normal request to the Duply image API.
Return evidence
Send the final image URL, template used, and input summary back to the agent for review.
- trigger
- An agent prepares a campaign brief
- inputs
- Template ID, headline, photo URL, CTA
- output
- A deterministic branded image
- destination
- Approval step or campaign workflow
Frequently asked questions
Does MCP replace the image API?
No. MCP is the agent-facing tool layer; the underlying generation request can still use Duply's image API.
Should an agent be allowed to edit every layer?
Usually no. Expose only approved templates and dynamic fields so the agent cannot change locked brand elements.
Continue the workflow
Build one production-shaped example
Start with one approved template, realistic data, and the exact trigger your team intends to use.
Start free