VEGAS Pro MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VEGAS_MCP_TOKEN_FILE | No | Selects a different token-file path. Its contents must match the extension's installed token. Never put a token value in client configuration. | |
| VEGAS_MCP_INSTALL_ROOT | No | The installation directory of the VEGAS MCP extension, if it was deliberately installed elsewhere using -InstallRoot. Should be set to the same directory as the installer result. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vegas_capabilitiesB | List the installed VEGAS connector actions and their safety contract. |
| vegas_statusA | List live VEGAS Pro 2026 connector instances or inspect one instance. Pass vegas_pid only when multiple copies of VEGAS are open. |
| vegas_projectB | Inspect, back up, save, undo/redo, control transport, set the cursor, or save a preview snapshot. Mutating actions require params.project_path exactly as returned by inspect. |
| vegas_timelineB | Perform guarded timeline inspection and editing. Inspect first. Existing-event mutations require event_id, expected_start_seconds, expected_length_seconds, and exact project_path. |
| vegas_audioB | Perform guarded native VEGAS audio operations. Event mutations require exact event identity and prior start/length values from timeline.inspect. |
| vegas_effectsC | Inspect or change VEGAS/OFX event effects. Effect mutations require exact event identity and create a project backup plus an undo step. |
| vegas_mediaC | Inspect and manage project media, bins, image sequences, event takes, and guarded media replacement. |
| vegas_motionC | Inspect and change guarded event pan/crop motion and video-track motion keyframes. |
| vegas_renderC | List renderers/templates and start, inspect, or cancel a guarded asynchronous VEGAS render. Outputs never overwrite existing files. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
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.
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.
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.
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.