Creatomate
Creatomate is an API for generating and managing automated videos, images, GIFs, and reusable media templates.
Verdict
Common use cases
- Generate personalized video thumbnails at scale
- Automate social media asset variants
- Render GIF previews from campaign templates
- Export branded video intros for webinars
- Batch-produce localized image ads
Integration
- Vendor
- Creatomate
- Category
- other
- Auth
- API_KEY
- Tools
- 7
- Composio slug
creatomate
Tools
- Create Render
Start one asynchronous image, video, or GIF render from either a template or a direct RenderScript. The call consumes render credits and returns the initial status; use Get Render to check completion.
- Create Template
Create a reusable project template from a RenderScript without starting a render, returning the saved template and any non-fatal warnings.
- Delete Templatedestructive
Permanently delete one project template. Existing renders created from the template are unaffected.
- Get Render
Return the current status and available output metadata for one asynchronous render; terminal statuses are succeeded and failed.
- Get Template
Return one project template including its complete RenderScript source.
- List Templates
Return metadata for every template in the connected project, optionally filtered by any of the supplied comma-separated tags; RenderScript source is not included.
- Update Template
Partially update a template's name, replacement tag list, or complete replacement RenderScript source; omitted fields remain unchanged.
Setup
Setup guide
- 11. Open your Switchy workspace settings and navigate to the Integrations tab. 2. Click Connect next to Creatomate and paste your API key from the Creatomate dashboard (found under Account → API Keys). 3. Switchy stores the key and confirms the connection with a green checkmark. 4. Inside any Project, type '@Creatomate list templates' to verify the integration works; you should see a list of your existing templates. 5. To render an asset, use '@Creatomate create render' with a template ID or inline RenderScript, then copy the render ID from the response. 6. Poll completion by calling '@Creatomate get render' with that ID until the status shows 'succeeded', at which point the response includes download URLs.
What teammates see: by default, memories from Creatomate are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List All Templates
@Creatomate list all my templates and show their IDs and names in a table.
Start Template Render
@Creatomate create a render using template ID abc123, replacing the 'headline' field with 'New Product Launch' and the 'logo' field with https://example.com/logo.png.
Check Render Status
@Creatomate get the status of render ID xyz789 and show me the download link if it's done.
Create New Template
@Creatomate create a new template named 'Instagram Story' with this RenderScript: { "width": 1080, "height": 1920, "elements": [{ "type": "text", "text": "Hello" }] }.Update Template Script
@Creatomate update template ID def456 to change the background color to #FF5733 in the RenderScript.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Creatomate list all templates tagged 'social-media' and show me their names and dimensions
Found 4 templates matching tag 'social-media': 'Instagram Story Promo' (1080×1920, video), 'Twitter Card' (1200×628, image), 'LinkedIn Carousel Slide' (1080×1080, image), and 'Facebook Ad 15s' (1080×1080, video). Each template includes modification timestamps and unique IDs. No RenderScript source is returned in list operations—use Get Template to retrieve the full composition definition for editing.
List Templates is a metadata-only call useful for discovery and inventory. The response excludes the actual RenderScript JSON, so you'll need a follow-up Get Template request to inspect or modify composition logic. Tags are user-defined during template creation and help organize large libraries.
@Creatomate render the 'Product Launch Video' template with title='New Feature' and launch_date='2025-06-15', then tell me the render ID
Render started successfully. ID: rnd_8x3k9mP2qL. Status: queued. The template accepts two text modifications: 'title' and 'launch_date', which have been applied. Rendering typically completes in 30–90 seconds for a 15-second video at 1080p. This operation consumed 1 render credit from your account balance. Use Get Render with this ID to poll for completion and retrieve the final MP4 URL.
Create Render is asynchronous and immediately returns a tracking ID. The call deducts credits before rendering finishes, so failed renders still consume quota. Always poll Get Render until status reaches 'succeeded' or 'failed'—intermediate statuses include 'queued', 'rendering', and 'processing'. Template modifications must match the template's defined input schema.
@Creatomate check render rnd_8x3k9mP2qL and if it succeeded, summarize the output file details in one sentence
Render rnd_8x3k9mP2qL succeeded. Output: MP4 video, 1920×1080 resolution, 14.8 seconds duration, 3.2 MB file size, available at https://cdn.creatomate.com/renders/rnd_8x3k9mP2qL.mp4 (CDN-hosted, permanent URL). The render completed in 47 seconds from submission. No errors or warnings were logged during processing.
Get Render is the polling mechanism for tracking asynchronous jobs. Once status is 'succeeded', the response includes the permanent CDN URL and technical metadata (codec, bitrate, frame count). Failed renders return an error message explaining the cause—common issues include invalid template modifications or insufficient credits. Poll interval recommendation: every 5–10 seconds for video, every 2–3 seconds for images.
Use-case deep-dives
When Creatomate wins for weekly campaign rollouts
A three-person marketing team ships five social variants every Monday morning—same copy, different aspect ratios and brand lockups. Creatomate's template system lets them store the master layout once, then call Create Render with new text and images in a single API hit. The asynchronous queue means the team kicks off all five renders in parallel and checks Get Render when Slack pings them two minutes later. This beats screen-recording Figma exports or paying a designer to resize by hand. The trade-off: if your variants need different animations or structural changes each week, you're better off with a design tool that has a proper versioning UI. Creatomate shines when the template is stable and the content slots rotate fast.
When this MCP handles SaaS welcome sequences
A six-person customer success team sends every new enterprise signup a personalized walkthrough video with the customer's logo, admin name, and three feature callouts pulled from their onboarding survey. They store one template in Creatomate, trigger Create Render from their CRM webhook, and embed the output URL in the welcome email fifteen seconds later. The async pattern means the render never blocks the signup flow, and Get Render status checks let them retry failed jobs without manual intervention. This works cleanly up to about 200 signups a day; beyond that, render-credit costs and queue depth start to matter, and you'll want to batch or cache aggressively. If your personalization is just text overlays, Creatomate is the right call—if you need conditional scene logic, look at a full video-editing API instead.
When Creatomate replaces manual screenshot workflows
A four-person analytics team publishes 30 client reports every Friday, each needing a branded cover image with the client name, date range, and top metric. They used to screenshot a Google Slides template and crop in Preview; now they call Create Render with three variables and get a PNG back in under ten seconds. The List Templates and Update Template tools let them tweak the layout once a quarter without touching code, and the API-key auth means any team member can trigger renders from a Slack command or internal dashboard. The constraint: Creatomate charges per render, so if your report count spikes above 500 a month, the credit burn adds up fast. For predictable, low-to-mid volume visual automation, this MCP cuts the busywork and keeps the design consistent without a designer in the loop.
Frequently asked
What does the Creatomate MCP let me do in Switchy?
It lets your AI agents create videos, images, and GIFs programmatically by calling Creatomate's render API. Agents can start renders from templates or raw RenderScript, check render status, and manage your template library—all without leaving the chat. Each render consumes credits from your Creatomate account.
Do I need a paid Creatomate plan to use this MCP?
Yes. You need an active Creatomate account with render credits and an API key. The MCP doesn't include free credits; every render your agents trigger counts against your Creatomate subscription. Grab your API key from your Creatomate project settings to connect it in Switchy.
Can the MCP edit video templates or only create new renders?
It can do both. Agents can update existing templates—changing the name, tags, or the entire RenderScript source—and they can create new templates from scratch. They can also delete templates you no longer need. The MCP doesn't let agents edit renders that are already queued or completed.
Why use this instead of Creatomate's web editor or API directly?
Use the web editor when you're designing templates by hand. Use this MCP when you want an AI agent to generate or modify templates on the fly, batch-render variations, or trigger renders based on data in your chat. The MCP wraps the same API your engineers would call.
Who on my team should connect the Creatomate API key?
Whoever owns your Creatomate project and has budget authority for render credits. The API key grants full read-write access to templates and the ability to start billable renders. Don't share the key across multiple Switchy workspaces unless you want every team burning the same credit pool.