Log inSubmit server
Levea MCP Server logo

Levea MCP Server

Prompt-driven video editing over MCP with captions, reframing, brand kits, async jobs, and MP4 exports.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Levea MCP Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "levea-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "levea-mcp-server"
      ],
      "env": {
        "LEVEA_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

levea-mcp-server connects AI clients to Levea’s hosted video production engine for natural-language editing, structured projects, and cloud-rendered exports. Its tools cover autonomous edits, caption templates, brand kits, projects, asset uploads, transcription, and job polling. Use it for tasks such as creating short clips, applying captions, reframing footage, or exporting MP4 files without running the production workload locally. Long-running work can stream progress or run asynchronously through task and job queues.

Use cases

  • Generate short viral clips with captions
  • Reframe source footage for vertical formats
  • Apply reusable caption styles to scenes
  • Manage project brand kits and media assets
  • Queue long video renders and monitor progress

Key features

  • Natural-language autonomous video editing
  • Streaming and asynchronous render workflows
  • Caption template management
  • Brand kit and project management
  • Signed media uploads and transcription
  • Cloud-rendered MP4 export

Tools25

What Levea MCP Server lets your agent do. Expand a tool for its parameters.

Verified live~3.8k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

11/11 checks healthy over the last 49d

What it can do

From the 25 tools this server returned when we ran it.

Runs commands · 2Can delete or modify data · 4Makes network requests · 5Read-only tools · 19
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age156 days
Maintainers1

Observed 2026-10-21 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · levea-mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars4Stargazers on the source repository.
npm downloads1.8kPackage downloads in the last 30 days.
Last commit2d agoMost recent push to the default branch.
Tools exposed25Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Levea MCP Server works

What levea-mcp-server does

Levea turns natural-language editing instructions into structured video projects and rendered outputs through MCP. An agent can submit a short request or a detailed creative brief for operations such as cutting viral clips, adding captions, reframing footage, applying chroma key effects, and exporting MP4 video.

The server also exposes project and media-management functions. Agents can create and inspect projects, upload source files through signed URLs, list or delete assets, and request transcription with word-level timing. Caption templates and brand kits can be created, reused, updated, or removed independently of a full autonomous edit.

How it works

The local MCP wrapper sends editing requests to Levea’s hosted production engine using an API key. Levea separates creative planning from media execution: a planning layer interprets the prompt, source media, transcripts, and timeline requirements, then produces typed editing operations for the production harness.

Projects are represented as structured scene data containing timelines, tracks, layers, assets, text, masks, audio, effects, and brand settings. The hosted engine performs the media work on cloud GPU infrastructure, including transcription, speaker-aware reframing, caption rendering, motion graphics, audio processing, and MP4 export. Edits can return a final result synchronously, emit progress events through the streaming tool, or run as queued tasks for longer renders.

Use check_job_status for export jobs, check_task_status for queued edit tasks, and get_active_task to reconnect to an edit already running for a project.

Setup and configuration

Create a Levea API key through Livecore and provide it to the MCP client configuration. The server is intended for MCP-compatible editors, including Claude Desktop, Claude Code, Cursor, Cline, and Windsurf.

Claude Code can install the associated plugin with:

text
/plugin install levea-video-editor --marketplace brajendrak00068/agentic-ai-video-production

After installation, select levea from /mcp and authenticate in the browser. For direct MCP use, register the levea-mcp-server stdio wrapper in the client and supply the API key. Local media can be uploaded by first requesting a signed URL with asset_upload_url, sending the file bytes to that URL, and passing the returned file URL to an edit request.

Tools and capabilities

  • Submit autonomous editing briefs synchronously or through streamed progress notifications.
  • Queue long-running edits and poll task or export status.
  • List, apply, save, snapshot, and delete caption templates.
  • Create and manage brand kits with palettes, fonts, logos, tone, grading bias, and enforcement settings.
  • Create, inspect, list, and delete projects and their uploaded assets.
  • Request signed uploads and transcribe existing media with timed transcript words.
  • Run an unauthenticated connectivity check against the configured Levea API endpoint.

Limitations and notes

The MCP wrapper is open source under the MIT license, while video production runs through Levea’s hosted service. An API key is required for authenticated editing operations. Heavy rendering, transcription, tracking, motion graphics, and export execute remotely rather than on the client machine.

Synchronous autonomous edits return the final MP4 URL when an export is queued, but longer work may outlast an MCP request timeout. In those cases, use queue_edit, the streaming variant, or the task and job status tools. The health diagnostic does not require authentication.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Levea MCP Server

levea-mcp-server is an MCP server that connects AI clients to Levea’s hosted video production engine. Its main tools submit natural-language edits, stream or queue rendering jobs, manage projects, captions, brand kits, and assets, transcribe media, and retrieve exported MP4 results.

Install or register the stdio MCP wrapper in an MCP-compatible client and provide a Levea API key. Claude Code also supports the Levea plugin installation command, after which you select the server from `/mcp` and sign in through the browser.

Use `asset_upload_url` to obtain a signed upload URL and file URL, upload the file bytes to the signed URL, then pass the returned file URL as `video_url` or in the assets list for `autonomous_edit`.

Use `queue_edit` for an immediate task ID, then poll with `check_task_status`; use `check_job_status` for an export job. `autonomous_edit_streaming` can instead return terminal results while emitting per-step progress notifications when the client supports them.

Yes. Cursor is named as a supported MCP client for the Levea stdio wrapper. Configure the server in Cursor and provide the required Levea API key before submitting editing requests.

Related MCP servers

All in Knowledge & Memory All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewLevea MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/levea-mcp-server?style=directory)](https://allmcps.com/mcp/levea-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/levea-mcp-server"><img src="https://allmcps.com/api/badge/levea-mcp-server?style=directory" alt="Levea MCP Server on AllMCPs" /></a>