jsontoimg

For agents

Your coding agent already has a render API .

MCP image generation from templates you already approved. Add the server once; your agent lists them, fills the named layers, and hands back a PNG or PDF.

For agencies · startups · in-house brand teams

  • Render from templates you already approved
  • PNG, JPG, WebP, AVIF, and PDF from your data
  • Same named layers as the REST API
  • Batch up to 50 jobs in one call
  • No Puppeteer cluster to own
Full docs
  • CursorCursor
  • ClaudeClaude
  • CodexCodex
  • VS CodeVS Code
  • WindsurfWindsurf
  • OpenCodeOpenCode
  • OpenClawOpenClaw
  • HermesHermes
  • AntigravityAntigravity
  • ClineCline
  • TraeTrae
  • Gemini CLIGemini CLI

One URL, no image infra

Render from any agent

Add the MCP server once. Your agent fills named layers on templates you already approved. The file stays on-brand.

Cursor Settings → Tools & MCP. Merge this into your config.

mcp.json
{
  "mcpServers": {
    "jsontoimg": {
      "url": "https://app.jsontoimg.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Replace YOUR_API_KEY with a key from API Keys.

The same named layers as curl

list_templates, get_template_schema, create_render. The payload your agent sends is the payload your API already accepts, so the AI agent render API and the REST API are one surface.

Never off-brand

The agent fills layers you named. It cannot move them or invent a layout. Fonts, colors, and logos stay in the template.

Batch, no babysitting

Point the agent at a list of rows. It queues up to 50 renders in one call. Same credits as a single render, counted per file.

Nothing to maintain

No headless Chrome. No OG-image service. One hosted MCP URL and a workspace key.

How it works

Connect once. Render from a prompt.

MCP setup to a signed file URL in one flow. Prompts, templates, and output stay in the workspace that issued the key.

  1. 1

    Add the MCP server

    Paste the URL and a workspace API key into Cursor, Claude, or any MCP client. The Cursor MCP server entry is the same JSON as every other client.

  2. 2

    Agent reads the schema

    It calls list_templates, then get_template_schema. Named layers, not a guess at your design.

  3. 3

    Render or batch

    create_render for one file. create_batch for up to 50. Credits come from the same balance as the REST API.

In the chat

One prompt, a finished file.

Your agent picks the template, fills the layers, and returns a signed URL you can drop into code, CI, or a CDN.

ClaudeClaudeAsk your agent

Every tool

Eight tools on connection.

No SDK to install. Your agent discovers these when it connects. The API key scopes them to one workspace.

Find and read templates

Ask for a template by name. The agent lists Studio and reads the named layers before it fills anything.

  • list_templates
  • get_template_schema

Render a file

Queue a render, wait for it, then take the signed origin URL. Works in an <img> without sending the key.

  • create_render
  • wait_for_render
  • get_render
  • get_render_asset_url

Render many at once

One template, many rows. Up to 50 jobs per batch, then poll until they finish.

  • create_batch
  • get_batch

Security

A scoped API key. Nothing else touched.

Bearer token in the client

The key lives in your MCP config. The server does not store it beyond the request.

Scoped to render and MCP

Keys can call the render API and the MCP endpoint. They cannot open the dashboard or other workspaces.

Tool calls only

The server receives tool names and their inputs. It never reads your conversation, files, or memory.

Disconnect any time

Remove the server from the client, or revoke the key in API Keys. Either ends access.

FAQ

Using a design MCP server with your agent

A template to image MCP: Cursor, Claude, and any other MCP client use the same hosted URL.

Stop owning image infra. Ship the campaign.

Prompt in. On-brand PNG or PDF out.

Design one template. Let the API do the rest. 25 images free — no card. Packs from $5, or $29/mo.