Creatomate vs PostNitro

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.

PostNitro

A hosted MCP server and REST API let an agent turn a topic, article or own slides into a branded carousel, image or slide video and schedule it, with OAuth, numbered rate limits and Markdown docs. No status page, security contact or idempotency key was found, and the privacy policy contradicts the vendor's no-training statement.

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

PostNitro

1. Call postnitro_set_defaults once with a template, brand and AI preset, or every generate call must carry those IDs
2. Pass the designId from postnitro_get_output to scheduling, never the embedPostId, or the call fails with Design not found
3. For a LinkedIn PDF post, set linkedinPostSettings.postType to document with a 5 to 90 character postTitle
4. Ask for the DESIGN output or save as DRAFT when a person must approve before anything publishes
5. Keep to 5 create calls a minute per key and wait for Retry-After on a 429