Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AI Edit Studio

NPM · AI-EDIT-STUDIO

Local-first video editor for AI agents: 59 tools for auto-edit, shorts, captions, music and QC.

Available components

63 Trust /100

Last scanned (9 hours ago)

Scores higher than 31% of npm servers

Category Design and Media

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability54
  • AI-judged instruction clarity (fair).Partial
  • Context-footprint check failed: tool/resource definitions use about 7380 tokens (~125/item across 59 items; 59 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 60 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Nov 26 62

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/ai-edit-studio@0.11.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 59 exposed · ~7,032 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
studio_storyboard ~106

One contact-sheet JPEG: the middle frame of every clip labelled with clip number and timeline second (max 48 tiles; long edits are sampled — use from/to to see a range), or evenly spaced frames of a finished export (exportId, optional from/to). Cheapest way to SEE the edit.

NameTypeReqDescription
countinteger––
exportIdstring––
fromnumber––
projectIdstringyes–
tonumber––

No output schema declared.

No examples provided.

studio_style ~100

Named styles shared by editor and agents (look, brand, mix, captions, export choices). action "list" (read), "save" (from a projectId or explicit options), "apply" (revision guarded; creates a revision).

NameTypeReqDescription
actionstringyes–
authorstring––
namestring––
optionsobject––
projectIdstring––
revisioninteger––

No output schema declared.

No examples provided.

studio_sync ~99

Audio-sync all recordings (cameras, separate audio recorder, screen capture) to a reference by cross-correlating their sound. Returns per source the offset (seconds it started after the reference) and confidence (≥1.5 reliable); stored for studio_multicam.

NameTypeReqDescription
maxOffsetnumber––
projectIdstringyes–
referenceinteger––
secondsnumber––
sourcesarray––

No output schema declared.

No examples provided.

studio_text_edit ~217

Edit video by editing text (needs a transcript). Remove word ranges (indices from studio_transcript), phrases, filler words (um/uh/eh…) and long pauses, or speed pauses up instead (speedPauses: {min, speed}; without a transcript the quiet stretches are sped up) — or "assemble" a paper edit: the timeline becomes the given word ranges in your order (best for talking heads, podcasts, interviews, clips). Revision guarded; dryRun previews. Captions follow automatically.

NameTypeReqDescription
assemblearray––
authorstring––
captionsboolean––
dryRunboolean––
projectIdstringyes–
removeFillersboolean––
removePauses–––
removeTextarray––
removeWordsarray––
revisionintegeryes–
smoothboolean––
sourceIndexinteger––
speedPauses–––
summarystring––

No output schema declared.

No examples provided.

studio_timeline ~108

Compact readable timeline: per clip id, source in/out, timeline in/out, energy 0-100, loudness, scene cuts, room to extend, captions, beat offset, plus sections and open comment count. Long edits: from/to (timeline s) and offset/limit paging; follow `next`.

NameTypeReqDescription
fromnumber––
limitinteger––
offsetinteger––
projectIdstringyes–
tonumber––

No output schema declared.

No examples provided.

studio_transcribe ~115

Local speech recognition (whisper.cpp or FFmpeg whisper, on this computer) → word-level transcript for one or all sources; by default also captions that follow the edit. Asynchronous: poll studio_get. If no engine is installed the error explains the one-time setup.

NameTypeReqDescription
authorstring––
captionsboolean––
languagestring––
modelstring––
projectIdstringyes–
revisioninteger––
sourceIndexinteger––

No output schema declared.

No examples provided.

studio_transcript ~154

Read a transcript (action "read": text with [mm:ss #wordIndex] stamps and/or words with inEdit flags, paged) or import one (action "import": SRT/VTT/whisper JSON file, or a words array from any ASR you ran yourself).

NameTypeReqDescription
actionstring––
authorstring––
captionsboolean––
filestring––
formatstring––
languagestring––
limitinteger––
offsetinteger––
projectIdstringyes–
revisioninteger––
sourceIndexinteger––
wordsarray––

No output schema declared.

No examples provided.

studio_update ~94

Update project with revision guard. Options merge with saved options; clips replace the whole edit. Prefer studio_edit for targeted changes. Captions use original SOURCE time and follow trims, reorder and speed. Never guess speech.

NameTypeReqDescription
authorstring––
clipsarray––
optionsobject––
projectIdstringyes–
revisionintegeryes–
summarystring––

No output schema declared.

No examples provided.

studio_wait ~84

Long-poll instead of polling: returns when the project is idle (nothing running or queued) or, with until:"revision", when its revision passes `revision`. Max 280 s per call; call again if timedOut.

NameTypeReqDescription
projectIdstringyes–
revisioninteger––
timeoutSecondsnumber––
untilstring––

No output schema declared.

No examples provided.

Install

How do I install the AI Edit Studio MCP server?

AI Edit Studio runs locally as an npm package, launched with npx -y ai-edit-studio. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · ai-edit-studio

# add to Claude Code
claude mcp add laaielichter-ai-edit-studio -- npx -y ai-edit-studio
Common questions

What is the AI Edit Studio MCP server?

AI Edit Studio is an MCP server listed in the public MCP registry as io.github.laaielichter/ai-edit-studio. Local-first video editor for AI agents: 59 tools for auto-edit, shorts, captions, music and QC. This page covers its npm package (ai-edit-studio).

Is the AI Edit Studio MCP server safe to use?

AI Edit Studio scores 63 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the AI Edit Studio MCP server expose?

AI Edit Studio exposes 59 tools: studio_schema, studio_list, studio_get, studio_timeline, studio_frame, and 54 more. Their descriptions and schemas cost roughly 7,032 tokens of context every time the server is loaded.

Is the AI Edit Studio MCP server still maintained?

AI Edit Studio is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the AI Edit Studio MCP server under?

AI Edit Studio declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.