For post houses
Keep Avid's native AI. Add the MCP lane.
Avid's IBC2026 announcements and Media Composer 2026.8 materials describe native Ready to Edit and embedded AI workflows. They do not document an MCP server. This independent, local-first MCP connects MCP-compatible agents—Claude, Cursor, Codex and others—to the Avid project evidence your post team already manages.Two complementary surfaces
Use Avid's built-in capabilities where they belong in the editor. Use this MCP when an assistant editor, coordinator, or automation agent needs a standards-based way to inspect projects and prepare a handoff across tools. The MCP does not replace Avid's native AI, claim to be an Avid product, or turn a plan into a completed edit.
Post-house work it can support
- Assistant editor tasks: inventory project trees, find active locks, inspect bins and sequences, and prepare bounded edit-plan previews.
- Bin organization: inspect AVB structure, clips, tracks, views and metadata before a human reviews any proposed organization.
- Metadata and review: inspect ALE, transcripts, markers, media streams and project evidence for logging, search and review workflows.
- Conform and turnover: validate AAF and EDL structures, inspect OTIO exchanges, and produce source-referenced evidence for conform or delivery handoffs.
Availability depends on the installed build, configured roots, dependencies and adapter. Read-only analysis is the default; live Media Composer operations require the separately installed compatible Extension bridge and its advertised capabilities.
Security that fits an on-prem workflow
Run the server on the workstation or an approved internal host. Allowed roots define which project folders it may read, offline analysis does not modify Avid projects or source media, and unsupported or unavailable live operations fail closed. Streamable HTTP is available for an internal deployment with bearer authentication; teams should still apply their own network, identity, storage and endpoint controls.
The MCP is not a hosted media service: it does not require uploading source media for its local analysis. Review the security policy, architecture notes and setup guide with your post-house security team before enabling any shared or live workflow.
A factual boundary
Avid's official IBC2026 announcementdescribes Ready to Edit, embedded AI and expanded APIs; its 2026.8 notesdescribe OTIO and SDK improvements. Neither page documents an MCP server. This project therefore makes a narrower claim: it provides an independent MCP interface to the project, interchange and guarded bridge capabilities that this repository actually implements.