Integration

Imagior integration

Imagior generates images from design templates you create in its editor, for social posts, banners and certificates. An agent can list the templates of the account, read a template's elements (all properties, or only the main text, image source and fill), generate an image from a template while overriding element properties such as text, image URLs or colors, and check the remaining credits. Each generated image costs 1 credit; the read routes cost none but are rate limited. Designing or editing templates stays in the Imagior editor. Authentication is an API key from the Imagior Developers page, sent as a Bearer token in the Authorization header.

Connect Imagior How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Imagior

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.

Template element, 2 operations

list_template_basic_elementsList template basic elementsGETLists every element of a template with only its main property: src for images, text for text, fill for paths. Lighter than list_template_elements when only those matter.
list_template_elementsList template elementsGETLists every element of a template, keyed by element name, with all its properties (text, src, fill, size, position, style). The names are the keys of elements in generate_image.

Account, 1 operation

get_accountGet accountGETGets the account's name, email and remaining credits (1 image costs 1 credit). Check it before a batch of generate_image calls. Costs no credit.

Image, 1 operation

generate_imageGenerate imagePOSTRenders an image from a design template with optional element overrides and returns its imageURL and remaining credits. Costs 1 credit per image. Get templateId from list_templates, element names from list_template_elements.

Template, 1 operation

list_templatesList templatesGETLists every design template of the account with its id, name and creation and update dates, newest update first by default. The id is the templateId of the other tools.

Use Imagior from Claude Code, Cursor or Codex

Connect Imagior in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Imagior 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 Imagior

Create your workspace
Sign up free. Nothing to install.
Connect Imagior once
Add your Imagior 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.