News2 min read

Adobe opens Creative Cloud projects to third-party AI agents

Adobe's local MCP preview will let outside AI agents edit native Photoshop, Illustrator, Premiere and After Effects projects.

By Aonghas Anderson

Adobe is preparing to let third-party AI agents make changes directly inside native Photoshop, Illustrator, Premiere and After Effects projects. The important part is not simply that an agent can edit media, but that the result remains a working creative file rather than a flattened export.

The company announced the local Model Context Protocol integrations at Adobe MAX on 10 November. They are still a preview and are due to enter private beta in early 2027, so this is not something most Creative Cloud customers can use today.

Editable projects are the point

Adobe says an outside agent will be able to work locally on project files while preserving editable elements such as Photoshop layers, Illustrator vectors, and Premiere bins and sequences. A designer or editor could then inspect the changes, undo them or refine the work by hand in the usual application.

That makes the proposal more useful than a workflow which only returns a finished image or video. A generated result may look right, but it becomes awkward when a client asks for one object to move, one clip to change or one part of a composition to be reused.

Adobe's example is repetitive production work: remove a logo once, ask an agent to carry the change across the rest of a campaign, then make any final adjustments manually. If the same agent can reach other MCP-enabled services, Adobe also envisages it collecting a brief from Google Docs and sharing completed work through Slack.

What remains uncertain

MCP gives AI software a common way to call tools, but it does not decide which controls an application should expose or make an agent reliable. Adobe product marketing vice-president Deepa Subramaniam told TechCrunch that the company is still working out the boundaries of the available capabilities and will use feedback to shape them.

Those boundaries matter. An agent that can alter a native project can save time, but it can also make the wrong change repeatedly or act on the wrong asset. Local operation and editable files reduce some risk; they do not replace permissions, version history, clear previews and human review.

Adobe is separately expanding its own Creative Agent and beta AI Assistants across Creative Cloud. The local MCP work is different: it is intended to let people bring a preferred third-party agent to Adobe's desktop tools.

For now, the announcement is a direction rather than a finished product. Its strongest idea is also its simplest: AI-assisted creative work is much easier to trust when people can see, revise and continue editing what the agent changed.

Sources

  1. Adobe transforms its Creative Cloud tools into agentic workflows
  2. Adobe brings AI agents and new creative tools to Photoshop, Premiere, and Firefly