Kalpana Docs
Batch MCP

Kalpana Batch

Let your assistant fill Kalpana templates with rows of data, render them and collect the files.

Kalpana Batch fills your templates with data. Your assistant finds a template, reads the inputs it takes, turns your rows into a batch, and renders a file for every row once you approve the cost. It can also make a single file without a batch.

It does not design or change templates. That is Kalpana Designer.

https://mcp.kalpana.one/mcp/batch

In Claude, add Kalpana Batch from the Claude directory. Its name in the MCP Registry is one.kalpana/batch. Other clients: Clients.

How a batch runs

Find the template

search_templates finds templates by name or topic and shows their previews. The assistant shows you the one it picked.

Read its inputs

get_template_inputs lists every text and image input, with ready example modifications. A template with several pages has inputs per page, and a template with flows has inputs per video. Inputs a row leaves out keep the page's own value.

Bring the images

search_assets finds the workspace's images by file name or collection. upload_images adds yours: from files, from image links, or through a link where you drop them in.

Check the rows

validate_batch checks every row against the pages or flow it fills before anything is saved, and names what is wrong by row and field: an unknown input, a value of the wrong type, an image it cannot find. It also shows each row as the server read it, with the job count and credit cost.

Stage the batch

With your approval, create_batch saves the rows (up to 1,000) as a draft and returns the exact credit cost. Nothing renders yet, and nothing is charged.

Run it

The assistant tells you the cost and asks again. On your yes, run_batch starts rendering. get_batch follows progress, and get_batch_outputs gives a download link for each file.

For a few files, create_job saves up to 10 jobs, each a page or flow with its own values, and returns their cost; after your yes, run_job renders one and returns the file, or create_job with run renders them at once. See Single jobs.

Two confirmations

An assistant never stages and runs a batch in one step. It asks before create_batch, and asks again, with the exact credit cost, before run_batch. A single file follows the same rule before run_job.

You can ask it to stop a running batch at any time: cancel_batch and cancel_job stop unfinished jobs, which are not charged. Jobs already rendered keep their files.

Cost

Batches use the workspace's render credits, taken only for jobs that render successfully.

OutputCredits
An image (PNG, JPEG or WebP)1
A video (MP4, GIF or animated WebP)Its length in seconds, scaled up for sizes above 1920 × 1080

Every other call is free. See Output formats for how video is priced, and the pricing page for the credits each plan includes and the latest prices.

Who can use it

Owners and Managers can create and run batches. Other roles can connect and read templates, inputs and finished batches, but cannot stage or run one. The assistant acts as you, so it has the same limits.

Things worth knowing

  • Animated templates. As an image, each row shows one moment of the motion: the page's still moment, or the last frame. As a video, each row is the whole motion.
  • What a batch renders. Pass exactly one of pages (page ids, from any templates), templates (every page of each) or flow (one flow, rendered as a video). Each row gives its own modifications and output, and renders once per page.
  • Several pages. A plain key such as Headline fills every page that has that layer. <pageId>@Headline fills one page only.
  • Flows. Pass flow to render a flow as a video for every row. In a video, <pageId>@Headline fills one page and <pageId>#2@Headline fills a page's second visit.
  • Images in rows. A row names an image by its asset id or file name, or as { asset, fit, zoom, panX, panY } to frame it differently.
  • Styled text. A text layer with several styles takes tags per style: <s1>Masala chai, </s1><s2>₹49</s2>.
  • Download links expire. Save the files soon after a batch finishes.

For your own agent

If you build an agent on Kalpana Batch, give it rules like these in its system prompt:

You can fill Kalpana templates through the Kalpana Batch MCP server.
1. Call get_template_inputs before preparing rows.
2. Leave out inputs that should keep the template's value.
3. Check every row with validate_batch before creating a batch.
4. Never call create_batch, run_batch, create_job with run, or run_job without the user's approval in the chat.
5. Before run_batch or run_job, state the exact credit cost the server returned.
6. Never call cancel_batch or cancel_job without the user's confirmation; cancelled jobs cannot be resumed.
Was this page helpful?

Updated 9 Nov 2026

On this page