INTEGRATIONS
MCP
Drive renders from Cursor, Claude Desktop, VS Code, and other MCP clients.
Agents can call jsontoimg without hand-rolled HTTP clients.
Setup
- Create an API key under Integrations → API keys.
- Open Integrations → MCP in the dashboard for copy-paste server config.
- Point the client at the MCP endpoint with your API key.
HTTP transport: https://app.jsontoimg.com/mcp (API key only — sessions are not accepted).
Tools
| Tool | Purpose |
|---|---|
list_templates | List a page of templates (name + description). Pass offset when hasMore is true. |
get_template_schema | Named layers and attributes for a template |
create_render | Queue a render (layers and optional variables match the Render API body) |
wait_for_render | Long-poll until done or failed |
get_render | Fetch job status |
get_render_asset_url | Signed origin download URL (?sig=; works in <img> without a key) |
create_batch | Queue up to 50 jobs |
get_batch | Batch status and child jobs |
sign_image_url | Mint a signed CMS / OG GET /api/v1/img/{template} URL |
sign_image_urls | Mint up to 50 signed URLs (does not queue renders) |
get_signed_image | Fetch a signed image URL and return image bytes |
Typical agent flow: list_templates → pick the template that matches the user prompt → get_template_schema → fill layers and optional variables → create_render. For <img> / Open Graph links, use sign_image_url (or sign_image_urls). create_batch still queues renders.
These tools use the same /api/v1 contract as the API reference.