Adobe MAX attendees report MCP support across Creative Cloud

• Adobe’s local MCP integrations reach private beta in early 2027, according to Adobe’s announcement, despite attendee reports describing a Creative Cloud-wide release.
• Photoshop support includes “Full real layer edit controls,” according to a follow-up from MAX.
• Headless shorts and After Effects longform work already coexist in one creator’s workflow.

Adobe’s own workflow example ends with an agent sharing creative work in Slack. A September Premiere feature request had already asked Adobe for an official MCP server with frame-accurate editing and explicit errors.

Adobe’s November 10 announcement previews local Model Context Protocol integrations that let third-party agents work in desktop creative projects. Its named integrations cover fewer apps than the lineup in the stage report:

• Named for the local MCP preview: Photoshop, Illustrator, Premiere and After Effects.
• Also on the stage slide: InDesign, Lightroom, Express, Firefly and Frame.io.

Adobe schedules the local integrations for private beta in early 2027. The wider slide establishes the breadth of the presentation, without providing an availability date for every app pictured.

Linus Ekenstam described “Full real layer edit controls” in a reply to his MAX report.

Adobe’s description of the integration says agents will change native project files on the user’s computer while preserving editable:

• Layers
• Vectors
• Bins
• Sequences

Creators can step back into the application and refine the work manually at any point. The editable project file is the prize here.

Photoshop layer-editing demonstration shared from MAX

When an agent also has MCP connections to services such as Google Drive and Slack, Adobe describes this workflow:

1. Retrieve a brief from Google Docs.
2. Work on the project using Adobe’s tools.
3. Share the result with colleagues in Slack.

That is Adobe’s proposed cross-tool workflow for the preview, with the creative project remaining on the user’s computer.

Bilawal Sidhu welcomed the announcement from a workflow that already combines headless editing with an editor working in Adobe tools.

After Effects serves as a “shared canvas for humans and agents” for Sidhu, where he can jump back into the application himself. He also said Claude hasn’t replaced all the plugins and workflows he likes using.

Adobe’s subscription moat drew pushback from BLVCKLIGHTai, who argued that handoff lives in file formats rather than applications. They later walked back an earlier claim that agents could already do “everything” Premiere and After Effects do, pointing instead to agents driving existing engines such as ffmpeg.

Ekenstam countered that enterprises couldn’t afford the risk of vibe-coding replacements. He also defended the craft involved in creative work, comparing dismissive accounts of professional workflows to “comparing McDonalds with The Bear.”

Adobe’s release describes two other routes into agent-assisted creative work alongside the forthcoming local MCP beta:

• Built-in Creative Agent: Adobe’s availability notes put AI Assistants in beta across flagship desktop apps, including Premiere, Illustrator, InDesign, After Effects and Frame.io. Photoshop’s assistant requires the Photoshop beta app.
• Adobe connectors: Adobe’s connector page lists integrations for Gemini, ChatGPT, Claude and Slack. Available tools vary by platform, and some capabilities require an eligible Adobe subscription.

Connector access also differs by platform: ChatGPT and Claude allow some Adobe capabilities without an Adobe account; Gemini requires an Adobe login, while Slack requires administrator enablement, according to Adobe’s connector FAQ.