Integration

Templated integration

Templated creative automation API: render a designed template into an image, a PDF or a video by overriding its named layers, read a render back with its status, list past renders, manage templates and their layers, and upload the pictures a template pulls in. Renders can be waited for or queued, in which case they start as pending and become completed or failed. Requests authenticate with a bearer token.

Connect Templated How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Templated.Built from the 10 Templated tools below, on the connection you add once.

Common Templated use cases

finding a render produced earlier
provisioning a template from code
cleaning up renders after delivery
producing a social image per article
finding a logo that was uploaded earlier
finding the identifier of a template by name
discovering the override keys before rendering
checking the size of a template before rendering
waiting for a queued render before publishing it
uploading a product photo before rendering a card

What you can do with Templated

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Render, 4 operations

create_renderCreate renderPOSTRenders a Templated template with the layer overrides you supply.
delete_renderDelete renderDELETEDeletes a Templated render.
get_renderGet renderGETReads the status and the link of a Templated render.
list_rendersList rendersGETLists the renders produced by the account.

Template, 3 operations

create_templateCreate templatePOSTCreates a Templated template from layers or from pages.
get_templateGet templateGETReads one Templated template and optionally its layers.
list_templatesList templatesGETLists Templated templates with optional name, size and tag filters.

Upload, 2 operations

list_uploadsList uploadsGETLists the images uploaded to Templated.
upload_imageUpload imagePOSTUploads an image to Templated so a render can point at it.

Layer, 1 operation

list_template_layersList template layersGETLists the layers of a template, which are the keys a render payload has to use.

Use Templated from Claude Code, Cursor or Codex

Connect Templated in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Templated operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Templated

Create your workspace
Sign up free. Nothing to install.
Connect Templated once
Add your Templated connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Templated integration FAQ

What can you do with the Templated integration?

LiveContext exposes 10 operations on Templated, covering render, template, upload and layer. Common uses include finding a render produced earlier, provisioning a template from code and cleaning up renders after delivery.