produce_ad_flow
From brief to on-brand piece, in one call.
MCP · for builders
Connect Cursor or Claude to Trakto's MCP and ask for the campaign in plain language. Every response returns an editable document with a direct link to the editor — never a dead JPG. Available on the Pro, Studio, and Teams plans, using the plan's credits.
The flow above isn't an illustration: the tools exist under these exact names, and this piece came from a real call — always with an editorUrl back.
// Cursor · Claude — paste and go
{
"mcpServers": {
"trakto": { "url": "https://beta.trakto.studio/mcp" }
}
}
// REST /v1 — same power, no MCP
POST /v1/ads/produce
Authorization: Bearer <PAT>
{ "brief": "summer launch", "brand": "solara",
"formats": ["1080x1080", "1080x1920"] }
→ { "editorUrl": "…/editor/doc_8f3k", "pages": 3 }
beta.trakto.studio/mcp endpoint with OAuth ready for Cursor and Claude — or the REST /v1 API.
produce_ad_flow, produce_campaign_kit, generate_visual, adapt_design_to_formats, export_document…
Every response brings the editorUrl. The agent handles volume; the human closes out the pixel.
Who it's for
For creative technologists, growth engineers, and anyone who lives in Cursor or Claude: automate production without giving up final control — the output is a document, not an image.
What's actually real
~22 tools in the core, documented in the developer portal.
From brief to on-brand piece, in one call.

The whole multi-format campaign via agent.

Image and video with the same models as the canvas.
One design, N sizes.
PNG, PDF, MP4, or HTML5, programmatically.
Publishes the page and reads the metrics.
apply_brand_kit and brand asset search.
Cursor and Claude via OAuth; REST /v1 for everything else.
Questions that reach us
Yes. Connect the MCP (beta.trakto.studio/mcp) via OAuth, ask in plain language, and get the document open in the editor.
Always. Every tool returns an editorUrl — the document opens in the editor with layers, not as a final image.
~22 in the core: produce_ad_flow, produce_campaign_kit, generate_visual, adapt_design_to_formats, export_document, publish_link, get_link_stats, and more — documented in the portal.
Pro and Studio (personal access) and Teams (team access). No separate charge: generations via MCP consume the plan's AI credits, just like in the editor.
Yes, /v1 with the same capabilities, plus a developer portal at beta.trakto.studio/dashboard/developer.