Trakto

MCP · for builders

Your agent creates the ad.
You open it in the editor.

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.

Create 3 1080×1080 ads for the summer line launch, with Solara's brand applied, and publish a product page.
produce_ad_flow · brand: solara · formats: [1080x1080] · variations: 3
publish_link · slug: solara-verao
Done. 3 variations created with Solara's Brand DNA, and the page is published:
→ editorUrl: beta.trakto.studio/editor/doc_8f3k…
→ trakto.link/solara-verao
Solara piece created via produce_ad_flow — editorial photo with glasses reflecting a sunset
produce_ad_flowreal piece created by this exact flow — fictional Solara brand, open in the editor with Flow and Motion ready

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 }

How it works

  1. 1

    Connect

    beta.trakto.studio/mcp endpoint with OAuth ready for Cursor and Claude — or the REST /v1 API.

  2. 2

    Ask for the work

    produce_ad_flow, produce_campaign_kit, generate_visual, adapt_design_to_formats, export_document…

  3. 3

    Open and finish

    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

A creation API, not an image generator.

~22 tools in the core, documented in the developer portal.

produce_ad_flow

From brief to on-brand piece, in one call.

produce_campaign_kit

The whole multi-format campaign via agent.

generate_visual

Image and video with the same models as the canvas.

adapt_design_to_formats

One design, N sizes.

export_document

PNG, PDF, MP4, or HTML5, programmatically.

publish_link + get_link_stats

Publishes the page and reads the metrics.

Brand in the loop

apply_brand_kit and brand asset search.

OAuth + REST

Cursor and Claude via OAuth; REST /v1 for everything else.

Questions that reach us

FAQ — MCP and API

Can I create an ad through Cursor?

Yes. Connect the MCP (beta.trakto.studio/mcp) via OAuth, ask in plain language, and get the document open in the editor.

Is the result editable?

Always. Every tool returns an editorUrl — the document opens in the editor with layers, not as a final image.

What tools does the MCP expose?

~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.

Which plans include MCP? Is it billed separately?

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.

Is there a REST API besides MCP?

Yes, /v1 with the same capabilities, plus a developer portal at beta.trakto.studio/dashboard/developer.

Connect your agent in five minutes.

Start free No credit card · full editor