Integration

Wafrow integration

Wafrow renders personalised images and PDFs from templates built in its visual editor. Render a template now with per-layer overrides (text, colours, image sources, opacity) and get the file back, save a set of overrides as a reusable preset, and render a saved preset. Templates are designed in the Wafrow dashboard and their ids are copied from there (the REST API has no template listing); the countdown-timer and Open Graph helper routes, the push-style render endpoint for third-party webhooks and the Shopify GDPR webhooks are not exposed. Each generated image counts against the plan's monthly allowance (Free 1,000 images, Lifetime License 10,000) or costs $0.01 on pay-as-you-go. Authentication is a Bearer API token created in the Wafrow dashboard under Settings, API Tokens.

Connect Wafrow How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Wafrow

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.

Image, 1 operation

render_imageRender imagePOSTRenders an image template now with optional layer overrides and returns the file (WebP image or PDF). Every call is one billed render (counted in the plan's monthly image allowance, or $0.01 on pay-as-you-go).

Preset, 1 operation

create_presetCreate presetPOSTSaves a set of layer overrides for a template as a reusable preset and returns its id in campaign. Render it with render_preset_image without resending the overrides.

Preset image, 1 operation

render_preset_imageRender preset imageGETRenders a saved preset of a template and returns the image file. Rendered (and counted as one generated image) on the first request, then cached, so repeated calls for one preset return the same image. Rate limit: 40 requests per minute per IP.

Use Wafrow from Claude Code, Cursor or Codex

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

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