Levea MCP Server vs MCP for Adobe Premiere Pro
A side-by-side look at the Levea MCP Server and MCP for Adobe Premiere Pro MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Levea MCP Server for multimedia process work as a local process; choose MCP for Adobe Premiere Pro for multimedia process as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Levea MCP Server when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
LEVEA_API_URL, LEVEA_API_KEY. - You want tools like
autonomous_edit, autonomous_edit_streaming, queue_edit.
Choose MCP for Adobe Premiere Pro when
- You need dedicated capabilities in the Multimedia Process domain.
- You prefer a local stdio subprocess transport.
- You want tools like
get_project_info, list_project_items, list_sequences.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Multimedia Process | Multimedia Process |
| Quality signal | 61/100 · Good | 71/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | LEVEA_API_URLLEVEA_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 414 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 25 | 432 |
| Full listing | View Levea MCP Server | View MCP for Adobe Premiere Pro |
Tools & capabilities
Levea MCP Server tools 25
autonomous_editPRIMARY EDIT TOOL. Run a natural-language video edit end-to-end. The backend agent plans, executes, verifies, and exports. Accepts anything from a one-liner ("generate 3 viral clips with captions and export") to a multi-paragraph creative brief. Returns the final mp4 URL synchronously when an export is queued. For long renders you may prefer queue_edit + check_job_status.autonomous_edit_streamingSame as autonomous_edit but consumes the SSE event stream from the backend. Returns the final terminal result; per-step events (status, thinking, tool_call, tool_result, background_job_completed) are emitted as MCP progress notifications when the client supports them. Use for long-running briefs where users expect live progress.queue_editFire-and-forget async path. Returns immediately with a `taskId`. Use when the edit may exceed the MCP request timeout (long viral-clip generation, multi-format export). Poll with check_task_status or get_active_task.check_job_statusPoll an export / async job by jobId (numeric). Supports wait:true to block until terminal.check_task_statusPoll a queued edit task by taskId (returned by queue_edit). Separate from job_id (exports).get_active_taskFor a given project, return the currently-running edit task (if any). Useful for reconnecting MCP clients.list_caption_templatesList the user's caption templates (builtin + saved). Returns slugs, display names, and style summaries.apply_caption_templateApply a caption template to a scene synchronously (without going through autonomous_edit).save_caption_templateSave a new caption template definition the user can re-apply later.save_current_caption_templateSnapshot the caption styling currently applied to a project / scene as a reusable template.delete_caption_templateDelete a user-saved caption template by id.list_brand_kitsList the user's brand profiles (palette, fonts, logo, voice, gradeBias). Returns ids you pass to autonomous_edit's brandId / projectBrandId.- +13 more on the listing page
MCP for Adobe Premiere Pro tools 432
get_project_infoGet information about the currently open Premiere Pro projectlist_project_itemsList all items in the project panel (clips, bins, sequences)list_sequencesList all sequences in the projectget_active_sequenceGet bounded, paged information about the currently active sequence (50 clips by default). Follow pagination.nextOffset for morelist_sequence_tracksList all tracks (video and audio) in a sequenceget_clip_propertiesGet detailed properties of a specific clip by its node IDfind_project_item_by_nameFind a project item by name (searches recursively through bins)get_sequence_settingsGet the settings (resolution, frame rate, etc.) of a sequenceget_selected_clipsGet the currently selected clips in the active sequenceget_clip_at_positionGet the clip at a specific time position on a tracksave_projectSave the current Premiere Pro project to its existing path. Fails when the project has never been saved (use save_project_as) or when Premiere writes no non-empty file. Fresh disk metadata verifies a save; unchanged or unreadable metadata reports committed_unverified.save_project_asSave the current project to a new .prproj path. Premiere then has the NEW copy open and closes the original, so later edits go to the copy; the result reports both paths. Fails when Premiere writes no file or leaves a pre-existing path unchanged. Use open_project to return to the original.- +420 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Levea MCP Server
{
"mcpServers": {
"levea-mcp-server-2": {
"command": "npx",
"args": [
"-y",
"levea-mcp-server"
],
"env": {
"LEVEA_API_URL": "YOUR_LEVEA_API_URL_HERE",
"LEVEA_API_KEY": "YOUR_LEVEA_API_KEY_HERE"
}
}
}
}
MCP for Adobe Premiere Pro
{
"mcpServers": {
"mcp-for-adobe-premiere-pro": {
"command": "npx",
"args": [
"-y",
"premiere-pro-mcp@1.24.0"
]
}
}
}
Frequently asked questions
Levea MCP Server is categorized under Multimedia Process and uses a local stdio subprocess. MCP for Adobe Premiere Pro belongs to Multimedia Process and uses a local stdio subprocess. Pick Levea MCP Server for multimedia process work and MCP for Adobe Premiere Pro for multimedia process.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Levea MCP Server has no declared pricing — check the project's own site. MCP for Adobe Premiere Pro has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add levea-mcp-server-2 and mcp-for-adobe-premiere-pro as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Levea MCP Server has a quality signal of 61/100 (Good) with 1 views, 0 installs and 2 GitHub stars. MCP for Adobe Premiere Pro has 71/100 (Great) with 3 views, 0 installs and 414 GitHub stars.