Skip to content
AtomCut
Documentation ▾

AI

Claude Code & external agents

AtomCut speaks MCP, the Model Context Protocol. Any agent app that does — Claude Code, Codex, Gemini CLI, Cursor, VS Code, Claude Desktop, your own — with any model it runs — can drive your open editor headlessly: every command the built-in agent has, the same eyes, the same skill. Script a whole edit from your terminal and watch it happen on the canvas.

Connect Claude Code

claude mcp add -s user atomcut -- npx -y @atomcut/mcp@latest
  1. In AtomCut: Agents ▸ Use your agent app ▸ Link. The tab stays linked and reconnects whenever Claude Code starts a session.
  2. Ask Claude Code: "In AtomCut, cut the pauses out of the interview, caption it, and make a 30-second vertical cut with a title card."

Other clients

ClientHow
Codexcodex mcp add atomcut -- npx -y @atomcut/mcp@latest
Gemini CLIgemini mcp add -s user atomcut npx -y @atomcut/mcp@latest
Cursor · VS CodeOne click from Agents ▸ Use your agent app — or add a stdio server with command "npx" and args ["-y", "@atomcut/mcp@latest"].
Claude Desktop · WindsurfSettings ▸ Developer ▸ Edit config: a server named atomcut with the same command and args.
Your own agentAny MCP client library: spawn npx -y @atomcut/mcp@latest over stdio, list tools, call them.

What the agent gets

  • Every editor command as a tool — about seventy: create and style layers, keyframes, effects, grading, auto layout, timeline edits (cut ranges with ripple, J-cuts), captions, and every AI media job your connections can do. Each has a live JSON schema.
  • Eyes — view_render and view_frames return real renders, so it checks its own work.
  • The AtomCut skill as MCP resources (atomcut://skill/SKILL.md and its references) plus the default design system — how to work well in the app, the same knowledge the built-in agent reads.
  • Self-description — api_describe, layer_properties and catalog_list read the live schemas, so nothing it learns is out of date.

Safe by construction

  • The bridge listens on 127.0.0.1 only — nothing off your computer can connect — and links only to AtomCut itself: the web app, the desktop app, or a tab holding the pairing token it prints.
  • Its changes appear live and land in the Undo menu under your agent's name, one step per request; it can only undo its own steps.
  • The layer it is working on shimmers, the same as with the built-in agent.

Built-in agent or external?

Use the built-in agent to work inside the app with any model. Use an external agent when you already live in Claude Code or Cursor, want to automate AtomCut from scripts, or combine it with your other tools — files, repos, the web — in one agent.