Skip to content
Sequence

SEQUENCE / MCP DOCUMENTATION

MCP video editor setup and tool reference.

Connect Claude Code, Codex, Cursor, or another AI agent to Sequence’s free browser video editor through MCP. Explore the tools, their exact parameters, and examples generated from the server’s own definitions.

Before you begin

Requires Node.js 24+, a local MCP client, and desktop Chrome or Edge. Keep the approved editor tab open while your agent works.

1. Add Sequence to your AI app

Choose your app, set media access, then copy its configuration. Your app starts the local companion automatically. Use a local session on the same computer as your browser; cloud-only agents cannot reach this companion.

Set up Codex

Official setup guide ↗

Create this file in your project, or use ~/.codex/config.toml for all projects. Project configuration loads only in trusted projects. The local app, CLI, and IDE extension use Codex configuration.

Keep your existing settings and other servers; add or replace only thesequence entry below.

Media access

Agent imports can read only these folders and their subfolders. Repeat the flag for each folder.

.codex/config.toml
[mcp_servers.sequence]
command = "npx"
args = [
  "--yes",
  "https://alamkanak.github.io/sequence/mcp/sequence-mcp-0.2.1.tgz",
  "--allow-media",
  "/absolute/path/to/assets",
]
startup_timeout_sec = 60

TOML · --allow-media

Restart the Codex MCP connection or start a new session. In the CLI, use /mcp to check that sequence is connected.

After changing media permissions, restart the MCP connection and pair again. The editor’s MCP toolbar button shows the active permissions.

Another local MCP client?

Choose local / stdio transport and use the executable and argument list from any JSON example above. Some apps use a mcpServers wrapper; use the format documented by your client. The GitHub Pages URL downloads the package; it is not a remote MCP HTTP endpoint.

2. Connect your project

  1. Refresh your AI app’s MCP connection and ask it to call connect_editor.
  2. Open the pairing link. Approve Connect AI agent and any browser local-network permission prompt.
  3. Keep one connected editor tab open. Ask the agent to inspect the project before editing.

3. Bring your media

The setup panel above includes media permissions directly in your configuration. --allow-media limits agent imports to the selected folders and their subfolders; repeat it for additional folders. --allow-media-anywhere allows any readable directory. Without either flag, agent file imports are disabled; browser imports still work. Ask the agent to import using absolute file paths. Binary transfers have no fixed file-size limit.

Your browser owns the project

Project data and requested preview images are shared with your connected AI client. Original media, rendering and completed exports stay in the browser. Pairing requires a local companion on the same computer as your browser.
Follow the editing workflow

Explore the tools

connect_editor

Connect editor · Connection

inspect_project

Inspect project · Connection

manage_assets

Manage assets · Editing

apply_edits

Apply edits · Editing

preview_frame

Preview frame · Rendering

export_video

Export video · Rendering

manage_jobs

Manage jobs · Rendering