Adobe has previewed local Model Context Protocol integrations for Premiere, After Effects, Photoshop and Illustrator. The company says creative professionals will be able to direct a preferred third-party agent to change native project files on their own computer. In Premiere and After Effects, that means an agent could work with editable sequences and compositions rather than returning only a rendered or flattened result.
The architectural distinction matters for production and post. An agent that operates through a documented application interface can potentially preserve timeline structure, layers and later human changes, while local execution may reduce the need to upload source projects to a separate automation service. Adobe has not identified the supported MCP clients, exposed commands or permission model, so the preview is not yet a deployable integration specification.
Adobe is also expanding its own Creative Agent into beta assistants for Premiere, After Effects, Illustrator, InDesign and Frame.io. Firefly Graph is entering beta as a node-based way to assemble repeatable workflows, while previewed always-on agents are intended to organize incoming assets, check quality and prepare versions in the background. These announcements put conversational control, reusable automation and native project editing into one broader workflow direction.
The release does not provide a shipping date for local MCP support, an API schema, operating-system coverage or details about authentication, audit logs, approval gates and rollback. Adobe also does not publish tests showing how agents handle linked media, plug-ins, shared storage, color management or concurrent editors. Broadcast and post facilities should therefore treat the announcement as a technical preview until Adobe documents the security boundary and production teams validate deterministic behaviour on representative projects.