Choose one of these two paths. You do not need to set up both. Your access to Claude or Codex is managed separately.
| Connect with MCP · recommended | Install the CLI · advanced | |
|---|---|---|
| Preparation | Add the URL and authorize EditorBrain | Install the package, authorize and prepare a folder |
| Editing instructions | The agent reads them with get_editing_guide | setup installs the skills in the project folder |
| Node.js / terminal | Not required to connect remote MCP | Node.js 22+ and terminal access |
| Render and storage | Your preferences and available capabilities are respected | Your preferences and available capabilities are respected |
Connecting MCP does not install skills on your computer. That does not stop you from reading the same instructions: the server delivers them in parts, when the agent needs them. With the CLI, skills are local files. Neither connection by itself guarantees an editing engine or access to your files: those depend on the environment and its permissions.
Connect with MCP
- Finish your workspace at EditorBrain.
- In Claude, open Connectors and add a custom web connector. In Codex, open MCP servers settings and add a remote HTTP server.
- Use EditorBrain as the name and
https://api.editorbrain.com/mcpas the URL. - Save, sign in and authorize the workspace. Turn the connector on in the chat, or reload the agent if it asks.
- Ask: "Check my EditorBrain connection and read the instructions for getting started." The agent should call
workspace_info, confirm the workspace and readget_editing_guide(SKILL.mdand only the guide for the current task). Copying the URL does not prove a connection.
Then tell it: "I want to edit this video with EditorBrain." If your agent cannot transfer an attachment, it can give you the project's upload link. A remote MCP connection does not get direct access to the folders on your computer.
You do not need to install EditorBrain, Node.js, Docker or local skills for this path. See MCP and agents for terminal setup, capabilities and troubleshooting. The client's connection options can vary by version, plan and permissions.
Install the CLI
This path requires Node.js 22 or later and an agent with a terminal (Claude Code or Codex). To develop this repository we use Node.js 24.
1. Prepare your workspace
Go to EditorBrain, finish onboarding and create a project in your brand. Keep the identifier that appears when you list projects. You do not have to repeat the brand setup for every video.
Choose a folder for that workspace on this computer, for example EditorBrain, and open it in Claude Code or Codex. Reuse the same folder for its later projects; another workspace needs another folder. In the command examples we call it my-videos; replace that path with the one you chose.
2. Install the CLI
This guide matches 0.53.0, published and verified on npm and the API. See Versions and availability and keep your agent's customized instructions when you update.
npm view editorbrain@0.53.0 version
npm install -g --ignore-scripts --no-audit --no-fund editorbrain@0.53.0
editorbrain version
editorbrain help
Without a global install, you can run a command with a pinned version:
npx --yes --ignore-scripts --package=editorbrain@0.53.0 editorbrain version
Installing or running with npm or npx does not organize other files on the disk. The new automatic per-project preparation requires the next compatible version, not the 0.53.0 package in this example. The agent should check the help of its own version.
3. Connect and choose the project
editorbrain login
editorbrain status
editorbrain brands list
editorbrain projects list
The browser asks for your authorization. Do not paste keys, cookies or codes into the chat. If it does not open automatically, use editorbrain login --no-browser and follow the link it returns.
From CLI 0.50.0 and the compatible service, a new login authorizes the account. editorbrain workspaces list shows the workspaces you can access; use --workspace ID for the job. A folder that is already synced keeps its workspace in .editorbrain/.sync.json. Older connections may need you to sign in again; updating the package does not widen their permissions. MCP consent stays independent.
4. Install the instructions for your agent
Replace my-project with the real ID, not the visible title:
editorbrain setup --dir ./my-videos --agent claude --project my-project --skip-mcp
For Codex, change --agent claude to --agent codex; both prepares both. --skip-mcp keeps this path independent. setup keeps existing configuration. If it returns PROJECT_SELECTION_REQUIRED, choose a real ID from projects list; if it returns action_required, finish the step it names without repeating what is already done.
Open the my-videos folder with your agent. The skill lands in .claude/skills/editorbrain/ or .agents/skills/editorbrain/, depending on the agent you chose. It should read those instructions before it edits.
Ask: "Set up my project with EditorBrain in this folder and keep my originals where they are." The agent reuses existing destinations and prepares the missing ones with the tools it has. It does not move or delete originals and it does not download media just to fill folders. First edit explains how to continue from here, including with MCP and no CLI, or without local access.
5. Check the connection
editorbrain doctor --dir ./my-videos --agent both
Check editorbrain status and run editorbrain validate --dir ./my-videos. You do not need to connect MCP to finish this path; an optional MCP warning does not force you to install it. A clean diagnosis does not guarantee a render engine or a ready external integration: review the capabilities it returns.
Then tell the agent: "I want to edit this video with EditorBrain." Using the CLI does not change your saved render or storage preferences.
Use both options
This is optional. MCP authorization and CLI authorization are independent. If you connect both, the agent should check that workspace_info and editorbrain status return the same workspace. Your brands and projects are not duplicated. Keep existing connections; do not copy tokens between applications.
If you already have MCP, install the CLI binary and use setup --skip-mcp to prepare the local skills without registering another connector. If a plugin already provides the skills, keep that install and download the project with pull --project; do not install the same instructions again. The plugin is optional.
When you work both ways, use the same workspace, brand and project. If two sessions change the same document, the agent should read and reconcile the revision conflict, not overwrite it by force. Do not repeat a write over the CLI because the MCP response was slow: first check whether it was already saved.
Without a connection or an account
You can prepare local files and instructions:
editorbrain init --dir ./local-try --brand my-brand --project demo --agent both
editorbrain doctor --dir ./local-try --offline
That does not create an account, does not authorize the private library and does not upload files. If you later connect that folder, review the sync changes so you do not mix brands.
Update later
Installing a new version with npm does not by itself rewrite the skills of your projects. On versions that include it, editorbrain update coordinates the CLI and the skills. After that, reload the skills or open a new chat: an open conversation can keep using old instructions.
See Update EditorBrain and its instructions for global installs, registered projects and customizations. Read Versions and availability before you use advanced updater options. For one project you can also install the skills explicitly with the CLI you chose:
editorbrain skill install --dir ./my-videos --agent both
editorbrain skill list
Customized instructions are kept and conflicts are reported; do not resolve them by deleting your folder.
Next in developersHTTP API →