Media-Editor-MCP
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Media-Editor-MCPAdd a beat-synced transition to the first clip in my CapCut draft"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Media-Editor-MCP
A monorepo of MCP servers for AI-driven video editing, plus the shared media-analysis server they both rely on.
Packages
Package | Lang | What it is |
Python / uv | Edits CapCut drafts on disk (offline): clips, audio, text/captions, effects, filters, transitions. | |
TypeScript | MCP server that drives Adobe Premiere Pro via a UXP plugin bridge. | |
TypeScript | The UXP plugin loaded inside Premiere; the server talks to it over WebSocket. | |
TypeScript | Shared message/types contract between the Premiere server and plugin. | |
Python / uv | Editor-agnostic analysis: beat/energy detection, Whisper transcription, SRT, best-moments, stock fetch. Used by both editors. |
Related MCP server: Premiere-Pro-MCP
Layout & tooling
Polyglot monorepo — unified by git, Claude skills, and one MCP config, not a single build:
TypeScript (
premiere-*) uses npm workspaces (rootpackage.json). Build:npm install && npm run build.Python packages each keep their own uv venv — they are not a shared environment.
media-analysispulls Whisper/torch (heavy);capcut-mcpis light and must not inherit those deps.capcut-mcpdoes not importmedia-analysis; it calls it as a separate MCP server. The only coupling is registration in.mcp.json.
.
├─ packages/
│ ├─ capcut-mcp/ (python/uv) src/ccmcp
│ ├─ media-analysis/ (python/uv) src/media_analysis
│ ├─ premiere-server/ (ts) @ppmcp/server
│ ├─ premiere-uxp-plugin/ (ts) @ppmcp/uxp-plugin
│ └─ premiere-protocol/ (ts) @ppmcp/protocol
├─ .claude/skills/ cc-* (CapCut) and pp-* (Premiere) workflow skills
├─ .mcp.json.example sanitized server registrations (copy to .mcp.json, add keys)
├─ package.json npm-workspaces root (TS only)
└─ scripts/History & contribution model
capcut-mcp and the Premiere stack were each imported once via git subtree add
(then restructured into packages/). This monorepo is the single source of truth —
the full history of both originals is preserved here in main.
Work on
main. No subtrees, no submodules, no per-package branches.Do not run
git subtree pull/pushagainst the old standalone repos. The Premiere code was moved out of its original_pp/prefix, so the prefixes no longer align and a sync would corrupt the tree. Treat the original capcut/premiere repos as archived.New work in any package is a normal commit here; there is nothing to sync upstream.
Setup
# TypeScript (Premiere) deps + build
npm install
npm run build
# Python servers — independent venvs (run once each)
uv sync --directory packages/capcut-mcp
uv sync --directory packages/media-analysis
# MCP registration: copy the template, add your Pexels/Pixabay keys
cp .mcp.json.example .mcp.jsonOpen Claude Code at this repo root so the relative paths in .mcp.json resolve. .mcp.json is
gitignored (it holds API keys); share changes via .mcp.json.example.
Per-editor profiles (lighter context)
All three servers in .mcp.json load their tool schemas into every session (~12–18k tokens),
but you never edit in CapCut and Premiere at once. Two slimmer profiles each load just one
editor plus the shared media-analysis:
# CapCut session — skips Premiere's ~6–8k tokens of tool schemas
claude --strict-mcp-config --mcp-config .mcp.capcut.json
# Premiere session — skips CapCut's tool schemas
claude --strict-mcp-config --mcp-config .mcp.premiere.json--strict-mcp-config makes Claude Code use only the named file, ignoring the default
.mcp.json and user/global servers. Both profiles are gitignored (they hold API keys); copy
the .mcp.capcut.json.example / .mcp.premiere.json.example templates and add your keys. Use
plain .mcp.json (all servers) when you want everything loaded.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseBqualityDmaintenanceAn unofficial MCP-compatible server that enables advanced automation, querying, and remote control of Adobe Premiere Pro projects for power users, workflow automation, and AI integration.Last updated1514MIT
- Alicense-qualityBmaintenanceControls Adobe Premiere Pro via Claude, enabling automated beat-synced editing, timeline manipulation, and media analysis through two MCP servers (Node + Python).Last updated1,685MIT
- FlicenseAqualityCmaintenanceAn MCP server that enables AI assistants to automate CapCut Pro video editing, including creating drafts, adding media, text, effects, and keyframes, with support for both local and remote connections.Last updated11
- Flicense-qualityBmaintenanceLocal-first AI video editing engine controlled by MCP-compatible AI hosts, enabling AI to inspect footage, propose edits, modify multitrack projects, and render locally while keeping user control.Last updated
Related MCP Connectors
MCP server for ByteDance Seedance AI video generation
MCP server for Google Veo AI video generation
MCP server for Wan AI video generation
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/nguyenph88/Media-Editor-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server