BeatDesign MCP
BeatDesign MCP connects an agent to a local video editor, with clips, images and captions visible in the browser during editing.
- 331 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- The agent modifies local projects and sends media to an external provider when generation is enabled.
Install
- Works in
Manual install
pnpm install
pnpm db:push
pnpm devFirst startup block from the downloaded repository root. Then select the documented MCP command for your agent.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The agent modifies local projects and sends media to an external provider when generation is enabled.
This is third-party code. Review the repository files before installing.
What it does
BeatDesign MCP connects an agent to a project where the user edits video and arranges images on a canvas. The agent finds assets, adds clips to the timeline and edits captions. It returns a workspace link so the user can open the result in a browser. MCP and the interface share project services and storage. Importing and editing local files need no key; BeatAPI supplies media generation and analysis. Projects retain imported and generated assets alongside their work history.
Who it is for. Short-video creators delegating timeline assembly to an agent while reviewing results visually.
Good fit when
- You are assembling local clips into a rough cut while watching the open editor.
- An SRT file is ready for the agent to import and style on the timeline.
- The project contains generated image variants for comparison.
- Before export, you are positioning a logo over the video.
Not a fit when
- The team needs hosted collaborative editing.
- Editing depends on advanced transitions, speed controls and waveforms.
- The workflow requires a packaged desktop application without running the local project.
Example request
Add these three clips to a new timeline, place the logo and import captions. Open the editor for review before exporting.MCP
- Transport
- stdio, http
- Authentication
- not required
Limitations
Source setup requires Node.js 22 or newer, pnpm 10 or newer and a current Chrome on macOS or Windows. MCP frame extraction requires ffmpeg; timeline rendering also needs ffprobe. Generation and analysis call BeatAPI using your key, while local import alone uploads nothing there. Current source and published-package features differ, so match instructions and available tools to the version you installed.
How to disable. Disable the MCP connection and stop BeatDesign processes. Preserve the local data directory if you want to resume those projects later.
FAQ
Does editing my own files require a key?
No. Importing, arranging and local export work without one. Add BeatAPI for generation and analysis only.
How do I start MCP alongside the UI?
When running from source, use `pnpm dev:agent`. Use `pnpm mcp` for a separate stdio process.
Does browser export require ffmpeg?
No. Browser export uses WebCodecs and Mediabunny. ffmpeg requirements apply to MCP operations.
Why are fewer tools available than on main?
Published packages can lag behind source. Check your release documentation and avoid relying on unreleased actions.
How does the user inspect agent changes?
Open the returned project workspace link. MCP and the UI share state, so edits appear in the editor.
Discussion
No questions or reviews yet.
Related
MCP serversVidMoat MCP
Vidmoat MCP
Remote MCP server of a cloud video editor: an agent imports footage, edits the timeline, checks frames and renders MP4
MCP server that drives local Adobe Premiere Pro projects from Claude, Codex and other MCP clients
CartCut MCP opens a fresh connection on the next call after an editor update and asks the client to refresh its tool list.
MCP for Adobe Premiere Pro: editing through an agent
MCP for Adobe Premiere Pro
A local MCP server that lets Claude, Cursor and Codex read a Premiere Pro project, edit the timeline and export the result
An MCP server for Ableton Live: the agent creates tracks, places clips and builds arrangements straight in the open project
An MCP server for video editing built into the free Concat editor: the agent cuts clips, adds titles and captions, sets keyframes and exports video
README in short
A local project can place audio on separate tracks and images over video clips. Those assets remain in the same project alongside its work history.