Creatomate vs Templated API + MCP

Creatomate

A hosted MCP server with eight tools, OAuth with PKCE and per-project connections sits beside a small REST API whose errors carry a hint and a documentation link, and dry_run validates a render at no cost. No status page, changelog, OpenAPI file or security contact was found, and the terms and privacy policy date from June 2022.

Templated API + MCP

MIT-licensed MCP server with 25 tools, every one annotated with readOnlyHint and destructiveHint. One API key with full account access, and the MCP docs offer it as ?apiKey= in the URL.

Creatomate

1. Send "dry_run": true to POST /v2/renders before a paid render. It returns valid, errors, warnings and the effective source
2. Read warnings on every render response. A modification keyed to an unknown element or property name is ignored without an error
3. Keep under 30 requests per 10 seconds across the whole account, and wait for Retry-After on a 429
4. Download each file when the webhook fires. Renders, their URLs and their status records are deleted after 30 days
5. Use render_scale 0.5 for draft videos, about a quarter of the credits, and remember MCP create_render spends credits without a confirmation step from the server

Templated API + MCP

1. Call get_template_layers before create_render so the keys in layers match the template
2. Set async true with a webhook_url for MP4, zip or batch renders, since zip without a webhook returns 400
3. Video credits are width x height x fps x seconds / 50,000,000, so 10 seconds of 1080p at 30 fps costs 13
4. Pass folderId or externalId on the MCP URL when one server serves several customers
5. Back off on your own schedule after a 429, since the docs give no retry guidance