Skip to main content
Glama
unitedtaps2

VEGAS Pro MCP

by unitedtaps2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to VEGAS Pro MCP

No user-submitted related servers found.

    Related Servers

    • CutPilot

      Hellotravisss
      F
      license
      Not graded
      quality
      D
      maintenance
      Local-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.
      -

    • YoloCut

      Hhz0823
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents and MCP clients to programmatically edit video projects on a local desktop editor, with 119 tools for multitrack editing, effects, captions, audio, and batch auto-editing, producing reviewable and reversible real timeline edits.
      AGPL 3.0

    • reaper-mcp-bridge

      Echo722
      A
      license
      B
      quality
      C
      maintenance
      Enables MCP-capable AI agents to control REAPER through typed tools and a Lua escape hatch for project creation, track management, recording and editing, MIDI writing, mixing, rendering, and batch operations.
      50
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 9 tools

    Disambiguation4/5

    Tools are cleanly partitioned by domain (project, timeline, audio, effects, media, motion, render), and descriptions make the entry point (timeline.inspect) explicit. There is mild overlap risk since timeline, audio, effects, and motion all mutate events, but the descriptions steer by sub-domain, so an agent can generally distinguish them.

    Naming Consistency5/5

    All nine tools follow a strict vegas_<noun> snake_case convention (vegas_capabilities, vegas_status, vegas_project, vegas_timeline, etc.). No mixing of camelCase or verb styles, and the prefix makes the server boundary obvious.

    Tool Count5/5

    Nine tools is well within the sweet spot and each maps to a distinct functional area of the VEGAS editing workflow. No redundant or trivial tools padding the surface.

    Completeness4/5

    The surface covers capability discovery, instance status, project lifecycle, timeline editing, audio, effects, media, motion, and rendering — a broad and coherent lifecycle for a video editor. Minor gaps exist (e.g. no dedicated encoding/export-preset management beyond render), but core workflows are covered with no obvious dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources