Kagelot MCP — for any AI agent

Your tools. Our squad.
Direct from anywhere.

Connect Kagelot to your own AI coding agent (Claude Code, Codex, Gemini CLI, Cursor) via MCP. The squad writes screenplays, clip packages, and cinematic prompts inside your tool — the agents' brains never leave our server, you receive only finished work.

Watch: install in Claude Code & Codex

1 credit

direct_clip

Raw plain-language direction → finished 4-layer clip package: direction, camera angles, image prompts, video prompt. The core engine — you direct, it translates.

1 credit

write_screenplay

A plain-language brief → screenplay scenes in the locked Kagelot format. Story first, prompts after.

Free

list_styles

Browse the visual style blueprints and apply one to everything the squad writes. Master formulas stay hidden on our server.

Activate MCP in the studio

Open the Connect tab inside Kagelot, hit Activate, and copy your personal API key. Keys are revocable anytime.

Connect your agent

Add the server URL + key to your client's MCP config — or grab the starter kit below and everything is preconfigured.

Direct from your own tool

Ask your agent to direct a clip or write a scene. The squad answers with finished work — credits deduct only on success.

Kagelot Agent Starter Kit

Download and drop into any project: lightweight agent instructions, the project scaffold, and a preconfigured MCP connection. Works with Claude Code, Cursor, Antigravity — any MCP client.

Download on GitHub

How to install the Kagelot MCP server

Claude Code or Codex, about 2 minutes. Use your own key where it says <your-key>.

1. Get your key
Open Kagelot, go to the Connect tab and click "Activate MCP access". Your first key is created instantly and shown once. Copy it and keep it safe. MCP works on any paid plan.
2. Claude Code: add the server
Paste this single line in your terminal, with your own key in place of <your-key>. Then restart Claude Code and type /mcp: kagelot shows as connected. Add -s user right after "mcp add" to turn it on in every folder.
```
claude mcp add --transport http kagelot https://kagelot.com/api/mcp --header "Authorization: Bearer <your-key>"
```
3. Codex: add the server
Codex has no --header flag, so add this block to ~/.codex/config.toml instead, save, start a new Codex session and type /mcp. Needs Codex 0.44.0 or newer.
```
[mcp_servers.kagelot]
url = "https://kagelot.com/api/mcp"
http_headers = { "Authorization" = "Bearer <your-key>" }
```
4. Load a project and direct
In Kagelot, open your Projects, click ⋮ on a project and choose "Copy board link". In your terminal, type "load this project" and paste the link. The agent reads the story, characters and locked style, then you direct in plain words.
Other MCP clients (Gemini CLI, Kimi Code, Cursor, Antigravity)
Add an HTTP MCP server with this config. Gemini CLI and Kimi Code also have a one-line command on the Connect page.
```
{
  "mcpServers": {
    "kagelot": {
      "url": "https://kagelot.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <your-key>"
      }
    }
  }
}
```

Live in your Kagelot project

Everything the agent does from your terminal shows up in the project while it happens. Every file it writes is logged in the project chat and appears on the canvas, where an open tab updates by itself. When a clip needs images or video, the agent leaves pending Generate and Render cards in the chat. You click them in the app, and the results land on the clip's bar on the canvas.

All 12 tools

Failed calls are free. Images and video are generated in the app with your normal credits.

get_kagelot_brainThe operating guide: how a Kagelot project is laid out, plus the craft docs and style slugs you can pull on demand.Free

list_projectsYour Kagelot projects.Free

get_projectOpen a project from its link or id: file tree and memory.md.Free

read_project_fileRead a screenplay, clip prompt file or note.Free

write_project_fileCreate or update a text file. Every write is checked and logged in the project chat.Free

post_chat_messageLog your instruction and the agent's summary in the project chat.Free

create_settings_cardPropose an image or video render as a pending card in the chat. You click Generate or Render in the app.Free

direct_clipPlain-language direction in, a finished clip package out: direction, camera, image prompts, video prompt.1 credit

write_screenplayA plain-language brief in, screenplay scenes in the Kagelot format out.1 credit

list_stylesThe visual style blueprints (names and previews; master prompts stay on our server).Free

read_styleRead one style blueprint to apply it.Free

read_knowledge_docRead one Kagelot craft doc, such as the Seedance prompt rules.Free

Questions

What is the Kagelot MCP server?

An MCP (Model Context Protocol) server at https://kagelot.com/api/mcp. It connects AI coding agents like Claude Code and Codex to your Kagelot film projects, so the agent can read and write screenplays, clip prompts and notes, and call Kagelot's filmmaking agents. The agents' own instructions stay on Kagelot's server; your tool receives only finished work.

Which AI tools can connect?

Claude Code, Codex (0.44.0 or newer), Gemini CLI and Kimi Code have a one-line or config-file install on the Connect page. Any other MCP client that supports an HTTP server with an Authorization header, such as Cursor or Antigravity, works with the JSON config.

Does it cost credits?

direct_clip and write_screenplay cost 1 credit each, and failed calls are free. Reading and writing project files, styles, chat logging and proposing render cards are free. Images and videos are generated in the Kagelot app and use your normal credits there.

Which plan do I need?

Any paid Kagelot plan. MCP access can't be activated on the Free plan.

Does the MCP server generate images or videos?

No. The agent proposes a render as a pending card in your Kagelot chat, and you click Generate or Render in the app. Nothing is spent without your click.

Do changes from my terminal show up in Kagelot?

Yes. Files the agent writes appear on the project canvas, every write is logged in the project chat, and an open browser tab on the project updates by itself.

Is my API key safe?

Your key is shown once and never stored in readable form. You can revoke any key instantly from the Connect page, and a revoked key stops working on the next call.

Video transcript

Your AI terminal can direct films now. Here's how to plug Kagelot in.

One connection gives Claude Code or Codex Kagelot's whole film crew as tools.

Open Kagelot, go to the Connect tab, hit Activate, and copy your key. It's shown once, so keep it safe.

In Claude Code, paste one line: claude MCP add, the Kagelot address, and your key as the header.

Restart Claude Code and type slash MCP. Kagelot shows connected. Add dash S user to have it in every folder.

Codex has no header flag, so open the config file instead, dot codex, slash config dot toml, and paste this block: the address and your key.

Save, start a new Codex session, and type slash MCP. You need Codex zero point forty-four or newer.

Now go to your projects. Pick one, and copy its board link.

Back in your terminal, type load this project, and paste the link.

It reads the whole project: the story, the characters, the style. Then it asks what's next.

Say yes, and it directs your next clip, right from your terminal.

And it's all live in Kagelot. The chat shows the same conversation, and the new clip appears on your canvas.

Click generate, and the images land right in place.

Then hit render. Your clip is ready.

Full guide at kagelot dot com, slash MCP.

Your tools. Our squad.Direct from anywhere.