Understanding Avid MCP

What is Avid Media Composer MCP?

An open-source server that connects AI assistants to Avid Media Composer projects. Read bins, analyze interchange files, and audit project trees — all without opening the application.

The short answer

Avid Media Composer MCP is an open-source Model Context Protocol server that gives AI assistants like Claude, ChatGPT, and Cursor read-only access to Avid Media Composer projects. It parses AVB bins, AAF files, ALE logs, EDL cut lists, and project metadata directly from disk — no Media Composer application required.

You install it locally, point it at your Avid project folders, and connect it to an MCP-compatible AI client. The assistant can then answer questions about your projects, validate deliverables, and audit editorial files using natural language.

Read-only by design

Offline analysis never modifies project files or source media. Guarded live editing requires a separately installed Avid Extension bridge.

Why it exists

Avid Media Composer projects are directories of proprietary binary files. Understanding what's in them — which bins are locked, what sequences exist, whether an AAF will conform cleanly — normally requires opening Media Composer, loading each bin, and inspecting them one by one.

That's slow, error-prone, and impossible to automate at scale. Post supervisors audit dozens of projects. Conform editors check interchange files from multiple facilities. Pipeline developers need structured project data for tracking and reporting.

Avid Media Composer MCP solves this by parsing those files directly and exposing their contents as structured tools an AI assistant can call. Ask "Which bins in this project contain sequences over 10 minutes?" or "Does this AAF have missing media?" and get accurate answers in seconds — no manual inspection required.

What it actually does

Project and bin analysis

Inventory project trees, classify files by type, detect active and orphaned bin locks, and parse AVB bins to extract clips, sequences, tracks, markers, and metadata through the open-source pyavb library.

Interchange file validation

Parse AAF, ALE, and CMX-style EDL files for structural errors, missing columns, malformed events, rate mismatches, and unsupported effects before anyone opens them in an NLE.

Media metadata inspection

Use ffprobe to extract codec, container, duration, frame rate, timecode, audio channels, and stream metadata from MXF, MOV, and other media files referenced by your projects.

Compatibility screening

Check Media Composer version, OS, and CPU architecture combinations against Avid's official qualification matrix to screen workstation configurations before deployment.

Guarded edit previews

Preview bounded editing plans, classify operations by risk, and require exact SHA-256 confirmation tokens before any live Media Composer changes can be applied through an Extension bridge.

Source-safe automation

Enforce explicit allowed roots so the server cannot read outside designated project folders. Report opaque data as labeled evidence instead of guessing, and fail closed when dependencies are unavailable.

Common use cases

Project audits before conform

Scan an Avid project tree, identify active and orphaned bin locks, validate interchange files, and catch missing media or malformed structures before anyone opens an NLE.

AAF, ALE, and EDL validation

Parse AAF, ALE, and CMX-style EDL files for structural errors, missing reels, rate mismatches, and unsupported effects — all without opening Media Composer or another application.

Metadata extraction and reporting

Pull clip names, timecode, markers, sequence structure, and custom bin columns from AVB bins and AAF files to generate reports, track changes, or feed downstream systems.

Pre-archive and migration checks

Inventory project files with checksums, verify interchange file integrity, and document project structure before long-term storage or facility migration.

Compatibility screening

Check whether a Media Composer version, OS, and architecture combination is qualified according to Avid's official compatibility matrix.

Automated QA workflows

Integrate with CI/CD pipelines to validate deliverables, check file completeness, and enforce post-production standards without manual inspection.

Who it's for

RoleHow they use it
Post-production supervisorsAudit projects and deliverables at scale without opening every bin manually.
Assistant editorsValidate interchange files, check lock status, and generate metadata reports in seconds.
Conform and finishing editorsInspect AAF, EDL, and ALE files for structural issues before starting a conform.
Pipeline developersBuild automated workflows that read Avid projects as structured data rather than screen scraping.
Archivists and data wranglersDocument project structure, verify file integrity, and prepare metadata for long-term storage.
Technical directorsScreen workstation configurations and diagnose integration issues programmatically.

What it is not

  • Not a replacement for Media Composer. It reads project files and provides analysis. It does not edit timelines, render effects, or transcode media.
  • Not a cloud service. The server runs locally on your workstation beside your project files. Your media and project data never leave your machine unless you explicitly configure remote HTTP transport.
  • Not UI automation or screen scraping. It parses structured project data directly from AVB, AAF, ALE, and EDL files. It never drives the Media Composer user interface or simulates mouse and keyboard input.
  • Not a general-purpose editor API. Avid Media Composer has no public scripting API. Live timeline editing through this MCP server requires a separately installed, compatible Avid Extension bridge that must advertise each operation.

How it works

The Model Context Protocol (MCP) is an open standard for connecting AI assistants to tools and data sources. Think of it as a structured way for Claude, ChatGPT, or Cursor to call functions on your behalf.

Avid Media Composer MCP implements this protocol as a local stdio server. You configure it with allowed project roots, add it to your AI client's MCP settings, and restart the client. From that point on, the assistant has access to a set of tools like avid_analyze_project, avid_analyze_bin, avid_analyze_aaf, and avid_inventory_project_files.

When you ask a question like "Which bins in Show_A are locked?", the assistant translates that into tool calls, the MCP server reads the project files, and the structured results flow back to the assistant for interpretation. You see the answer in plain language; the parsing happens behind the scenes.

Privacy and safety

The server runs on your machine. It reads only the folders you explicitly allow via AVID_MCP_ALLOWED_ROOTS. Optional telemetry is disabled by default and never includes prompts, file paths, or project names.

Getting started

  1. Install Node.js 20 or newer.
  2. Set AVID_MCP_ALLOWED_ROOTS to your Avid project folder and AVID_MCP_CAPABILITIES to inspect.
  3. Run npx -y avid-media-composer-mcp@latest to launch the server.
  4. Add the server configuration to your AI client (Claude, Cursor, VS Code, etc.).
  5. Ask the assistant to call avid_ping and avid_get_capabilities to verify the connection.
  6. Point it at a project with avid_analyze_project and see what it finds.

For detailed setup instructions, Python dependencies, and client-specific configuration, see the setup guide.

What comes next

The current release provides read-only analysis of projects, bins, interchange files, and media metadata. A development branch adds local media intelligence (transcription, speaker workflows, visual search), saved snapshot inspection, and guarded native operations on qualified Windows builds.

Live timeline editing through an Avid Extension bridge is protocol-defined and tested but requires a compatible extension installed on the host. Until that bridge exists, live operations fail closed.

See the implementation status for what works today, the capability matrix for the full tool list, and the bridge contract for the extension integration path.

Start reading your Avid projects with AI

Free, open source, and local-first. Install in about 10 minutes and connect the AI assistant you already use.

Install the server Read the docs