jbd-mcp.exe, next to jbd.exe. An MCP client starts it as a local program and talks to it over stdio. It works in two modes:
Nothing leaves your computer. The bridge only accepts connections from
127.0.0.1.
Set up the bridge
1
Allow AI apps in JBD
Open Settings ▸ Connections and tick Let AI apps control JBD. The page shows “On: listening on 127.0.0.1:9876”. JBD remembers the choice and starts the bridge at every launch.
2
Copy the command for your client
The same page shows a ready-to-copy command and config with the full path to
jbd-mcp.exe on your computer. Use those; the examples below assume the jabrod.com installer’s path.3
Ask your client to edit
For example: “Look at the active sequence in JBD and cut the first 3 seconds.”
Client configuration
- Claude Code
- Claude Desktop
- Cursor
- Other clients
Run once in a terminal:
Headless mode
Headless mode needs no JBD window. Use it for batch work and scripts.
The
ui_* tools need the bridge and return an error in headless mode.
Authentication
None. The server runs as you, on your computer, and only reaches the JBD window through127.0.0.1. It does not use your Jabrod account and spends no AI credits.
Tools
All times are in seconds unless a field says ticks. 254,016,000,000 ticks are one second.Commands
Every menu item, shortcut and timeline gesture in JBD is a command with an id. These tools run them.Example: split at 3.5 seconds
Project and sequence
Rendering
Window (bridge mode only)
A typical loop
sequence_inspectto get clip ids and times.command_runto make the edit.render_frameorui_screenshotto look at the result.command_runwithedit.undoif it is wrong.

