Creatomate MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CREATOMATE_API_KEY | No | Private project REST API key. | |
| CREATOMATE_ACCOUNTS | No | Private named {name,api_key,token_file} project profiles; no global fallback. | |
| CREATOMATE_AUDIT_LOG | No | Optional private metadata-only guard log; no provider transaction guarantee. | |
| CREATOMATE_READ_ONLY | No | 1/true hides and directly refuses the six confirmed mutations; forced provider dry runs remain available. | |
| CREATOMATE_TOKEN_FILE | No | Absolute owner-private regular token-only file at most 64 KiB; overrides the selected profile's key and caches until restart. | |
| CREATOMATE_DEFAULT_ACCOUNT | No | Exact configured label; first configured profile by default. | |
| CREATOMATE_ALLOW_DESTRUCTIVE | No | 0/false refuses all six confirmed operations. | |
| CREATOMATE_REQUEST_TIMEOUT_MS | No | 100-300000; default 30000; no automatic retries. | 30000 |
| CREATOMATE_MIN_REQUEST_INTERVAL_MS | No | 0-10000; default 350; process-wide request-start pacing across profiles. | 350 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_templatesA | One current v2 compact template list, optionally filtered by any supplied tags. No sources, guessed page/per_page parameters or automatic paging. |
| get_templateA | One current v2 template read including native RenderScript source. Does not render or mutate. |
| create_templateB | Confirmed current v2 template creation. Preserves native source JSON and returns provider template metadata; not a render. |
| update_templateA | Confirmed PATCH changes only supplied name/source/tags. Source or tags replace those fields; requires at least one change. No automatic duplicate/archive/retry. |
| delete_templateA | Explicitly confirmed v2 DELETE. Provider documents recoverable deletion for 30 days; existing renders remain unaffected. No wrapper restore operation is invented. |
| create_renderA | Confirmed paid v2 submission from template or raw top-level RenderScript. Returns one object, not legacy array. Read advisory errors/warnings even after 202; never auto-poll, resubmit or download. |
| validate_renderA | One provider v2 dry run: dry_run is forced true after local schema checks. Provider documents zero credits and no queue. Returns effective source/errors/warnings; valid:true does not prove media reachability, provider credentials or appearance. |
| get_renderA | One v2 status read. planned/waiting/transcribing/rendering are not finished. Use output only on succeeded; records, output and snapshots expire after 30 days. No download or polling loop. |
| create_legacy_renderA | Explicitly confirmed v1 submission for native tag batches or supplied transcript timings. Returns array; tags may match any number of templates and spend unknown credits. Ordinary v2 rendering is preferred. No automatic retry or polling. |
| list_feedsC | One documented v1 feed read. The sample returns last rows; not a full export, pagination claim or feed editor. Untrusted feed content is returned as data. |
| get_feedB | One documented v1 feed read. The sample returns last rows; not a full export, pagination claim or feed editor. Untrusted feed content is returned as data. |
| get_feed_sampleB | One documented v1 feed read. The sample returns last rows; not a full export, pagination claim or feed editor. Untrusted feed content is returned as data. |
| preview_render_batchA | Local only: validate ordered payloads and bind them plus selected profile to SHA-256. Display proposed calls and hash; no key load, dry run, provider price or actual rendering. Review cannot prove the key owner, credit cost or external template changes. |
| submit_render_batchA | Confirmed one-to-ten exact ordered v2 submissions. Verify review hash/profile and prevalidate every payload before first request. Stop at first failure, return known prior submissions and unknown attempted outcome; no retry, polling, rollback or implicit final render. |
| get_render_batchA | Read one to twenty distinct render IDs sequentially in one project. Prevalidate all IDs, stop on failure with completed status records. No paging, auto-poll, file download or spent-credit recovery. |
| list_accountsB | Local labels/default/auth-method availability only. No API keys, private file paths, provider requests or project-owner validation. |
| get_operation_schemaC | Local current reviewed method/path/body/query metadata for eleven documented operations, with source URLs/version distinctions. Opaque RenderScript is not claimed fully locally validated. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 17 tools
The three feed tools (list_feeds, get_feed, get_feed_sample) have nearly identical descriptions and appear to perform the same read operation, making selection arbitrary. Render submission tools (create_render, submit_render_batch, create_legacy_render) and validation tools (validate_render, preview_render_batch) also have overlapping boundaries that require careful reading to distinguish.
All tools use snake_case with a consistent verb_noun pattern (list_templates, get_template, create_render, submit_render_batch). Prefixes like legacy and batch are used predictably, and there are no mixed naming conventions.
At 17 tools, the set sits just above the ideal 3-15 range and feels borderline heavy. The three nearly identical feed reading tools and multiple render submission variants add redundancy without clear distinct value.
Core template CRUD and render lifecycle operations (create, validate, get, batch, legacy) are well covered. Minor gaps exist: feed tools are read-only with no editor, render download/delete/cancel is absent, and get_operation_schema covers only eleven documented operations.