Levea MCP Server

by brajendrak00068 Your server? Claim it

answering

Levea MCP Server is answering right now. Last checked moments ago. 1 324 installs a week from npm. It exposes 25 tools. Last commit 6 Nov 2026.

Autonomous AI video editor over MCP: viral clips, captions, reframe, chroma key, MP4 export

Installs per day peak 196 · avg 15 · +462% w/w

a month agotoday

Uptime history 12 days of history · worst day 73%

12 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

703 ms

Response time

average over 24h

1 324

Installs / week

npm and PyPI

What the code does

We read the source, 1 d ago · tools taken from the live server · rules 995398eba69f

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Package points at a different repository brajendrak00068/agentic-ai-video-production

пакет levea-mcp-server ссылается на brajendrak00068/openclaw-ai-video-editor

Runs an external command mcp-server/mcp-publish-sync.js:12

    const out = execSync(cmd, { cwd: dir, encoding: 'utf-8', stdio: 'inherit' });

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add levea-mcp-server --transport http https://api.livecore.ai/api/v1/misc/mcp

Settings → Connectors → Add custom connector, then paste this address

https://api.livecore.ai/api/v1/misc/mcp

~/.codex/config.toml

[mcp_servers.levea-mcp-server]
url = "https://api.livecore.ai/api/v1/misc/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "levea-mcp-server": {
      "url": "https://api.livecore.ai/api/v1/misc/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "levea-mcp-server": {
      "type": "http",
      "url": "https://api.livecore.ai/api/v1/misc/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Available tools 25

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

brand

create_brand_kit

Create a brand profile. Fields: name, palette {primary,secondary,accent,neutral,extras[]}, fonts {primary,secondary}, gradeBias (warm/cool/neutral/vivid/muted), forbiddenColors[], logoAssetUrl, voiceTone, enforcement (soft|hard).

delete_brand_kit

Delete a brand profile.

get_brand_kit

Fetch one brand profile by id.

list_brand_kits

List the user's brand profiles (palette, fonts, logo, voice, gradeBias). Returns ids you pass to autonomous_edit's brandId / projectBrandId.

update_brand_kit

Update an existing brand profile by id. Body has the same shape as create_brand_kit.

project

create_project

Create a new project. Optional initial brandId.

delete_project

Delete a project.

get_project

Fetch one project by id.

asset

asset_upload_url

Get a signed upload URL for a local file (so users do not have to host video / image / audio elsewhere before passing video_url to autonomous_edit). Body: { fileName, fileType?, contentType?, projectId? }. Returns { uploadUrl, fileUrl }; PUT the file bytes to uploadUrl, then pass fileUrl to autonomous_edit as video_url / in assets[].

delete_asset

Delete an asset by file name (the path returned by asset_upload_url).

autonomous

autonomous_edit

PRIMARY 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_streaming

Same 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.

caption

delete_caption_template

Delete a user-saved caption template by id.

list_caption_templates

List the user's caption templates (builtin + saved). Returns slugs, display names, and style summaries.

save

save_caption_template

Save a new caption template definition the user can re-apply later.

save_current_caption_template

Snapshot the caption styling currently applied to a project / scene as a reusable template.

active

get_active_task

For a given project, return the currently-running edit task (if any). Useful for reconnecting MCP clients.

apply

apply_caption_template

Apply a caption template to a scene synchronously (without going through autonomous_edit).

assets

list_assets

List the user's uploaded assets. Optional projectId filter.

editor

editor_health

Connectivity diagnostic against LEVEA_API_URL. Unauthenticated.

job

check_job_status

Poll an export / async job by jobId (numeric). Supports wait:true to block until terminal.

projects

list_projects

List the user's projects.

queue

queue_edit

Fire-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.

task

check_task_status

Poll a queued edit task by taskId (returned by queue_edit). Separate from job_id (exports).

transcribe

transcribe_asset

Force transcription of an existing asset. Returns transcript words + timing.

Endpoints

URL	Transport	State	Latency	Checked
https://api.livecore.ai/api/v1/misc/mcp	streamable-http	sign-in	759 ms	0 min ago

Alternatives to Levea MCP Server

same job, measured the same way

Vecmo

by chibataku0815

Vector motion editor MCP: 26 typed tools to observe, validate and edit documents, then export code.

local only

Houyidb MCP

by houyidb-community

MCP server exposing HouyiDB vector search, collection status, and opt-in writes.

91 installs/wk local only

AI Wave

by elopstudio-aiwave

AI model releases, price changes and deprecations in one feed: chat, embedding, speech, video.

69 installs/wk 8 tools answering

Inkbolt vector and raster editor

by skulitom

Local vector and raster editing engine for agents: layered documents, saved sessions and exports.

local only

MCP Openai

by acedatacloud

MCP server for OpenAI API (chat completions, image generation, embeddings) via AceDataCloud

5 189 installs/wk answering

RAG MCP

by jaimenbell

Minimal RAG-over-a-corpus MCP retrieval: search_knowledge returns cited chunks. Local embeddings.

108 installs/wk local only

GPT Chat

by codechap

MCP server for the OpenAI ChatGPT API — chat, vision, and embeddings

local only

MLP Vector Club

by mlp-vectorclub

Search and edit the MLP Vector Club color guide: appearances, tags, shows and reservations.

answering

Levea MCP Server — questions

Answers built from our own checks of this server.

What can Levea MCP Server do?

It exposes 25 tools, read directly from the server on our last check. Among them: apply_caption_template, asset_upload_url, autonomous_edit, autonomous_edit_streaming, check_job_status, check_task_status and 19 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Levea MCP Server mostly used for?

Its tools cluster around brand, project and asset. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Levea MCP Server working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 703 ms. The bar chart above shows every period we have measured.

How do I connect Levea MCP Server?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to Levea MCP Server?

No API key is involved. Levea MCP Server answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is Levea MCP Server?

It answers our handshake in 703 ms on average, which is faster than 12% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.

How many people use Levea MCP Server?

The npm package levea-mcp-server was installed 1 324 times in the last week. Week over week that is +462%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.

Is Levea MCP Server open source?

The code is open source: it is published under the MIT licence, written in TypeScript and 4 stars on GitHub. The licence covers the code in the repository, not the hosted service at api.livecore.ai, which runs on its operator's own terms.