# Adobe Local MCP: What Is Available Now and What Waits Until 2027

Adobe’s desktop-agent preview could preserve editable project files, but it is easy to confuse it with the AI assistants you can use today.

By Paras Madan | 2026-11-10


Adobe’s new local MCP integrations for Photoshop, Illustrator, Premiere and After Effects are not publicly available today. Adobe previewed them at MAX on November 10 and says a private beta will arrive in early 2027. Its in-app AI assistants are a separate offering, already available in beta.

That distinction matters if you want an external agent to edit a real project rather than generate an image and hand you a flattened result. The promised integration is interesting precisely because it reaches the working document, but a preview is not something a production team can depend on next week.

## Local MCP versus Adobe’s current AI assistants

MCP is a protocol that lets an AI application connect to tools and data. In Adobe’s announced implementation, a third-party agent would work through local integrations to make changes in native Creative Cloud project files. Adobe says layers, vectors, bins and sequences will remain editable.

The [Creative Cloud announcement](https://news.adobe.com/news/2026/11/adobe-transforms-creative-cloud-tools) separates that future integration from Adobe’s own Creative Agent. Its AI assistants are in beta in flagship desktop apps; Photoshop’s assistant is specifically in the Photoshop beta app.

| Capability | Status announced November 10 | Practical meaning |
| --- | --- | --- |
| Local MCP for Photoshop, Illustrator, Premiere and After Effects | Private beta planned for early 2027 | No general installation workflow announced for this release |
| Adobe Creative Agent assistants in flagship desktop apps | Beta | Available through Adobe’s supported app experiences |
| Photoshop AI Assistant | Photoshop beta app | Do not assume it appears in the regular Photoshop release |
| Firefly AI Assistant | Beta | A conversational workflow inside Firefly |

A third-party project with “Photoshop MCP” in its name is not automatically the Adobe integration announced at MAX. Check the publisher and support model before treating a similarly named tool as an official release.

## Why editable files change the handoff

Consider a product video that needs several versions. A generated final video can look convincing but leave the editor little room to change one title, adjust one mask or replace one clip. An agent that modifies an editable sequence can potentially leave the work in the structure the editor already uses.

The difference becomes visible during revisions. If the customer asks for a different opening shot, the question is whether the editor can make that change directly or must regenerate an entire output. Preserving the project structure could reduce that cost, provided the agent also leaves the document organized and understandable.

**Editability is a useful requirement, not a quality guarantee.** A sequence can remain editable and still contain wrong timing, poor masks or an effect applied to the wrong clips. Teams will need to review the project itself as well as the export.

## What you can evaluate before the MCP beta

Adobe says its current Premiere Creative Agent can apply effects across clips in a sequence, track masked subjects and adjust color and exposure across a sequence. That makes a copied, non-client-critical project a sensible starting point for evaluating assisted editing today.

Keep the trial narrow. Ask for one change across a defined set of clips, inspect what changed, and check whether you can refine it by hand. Record the time spent correcting the result. A fast initial response offers little advantage if repairing the sequence consumes the time saved.

For planning outside the desktop apps, [Firefly’s November update](https://news.adobe.com/news/2026/11/adobe-firefly-expands) adds a Plan Mode that lets creators review, edit and approve an agent’s plan before execution, along with model selection and saved preferences. These are different controls from the future local MCP connection, but they address the same practical need: knowing what a delegated task is about to do.

## A useful acceptance test for the future integration

Before adopting local MCP, define a task whose success you can inspect. For a hypothetical launch video, the brief might ask an agent to duplicate the project, replace a closing card, create a second aspect ratio and leave the original sequence untouched.

Then check four things: the original still opens unchanged; the new output uses the correct approved assets; the project remains editable; and another editor can understand the result without replaying the full agent conversation. This is a proposed evaluation, not a claim that the preview already supports every step.

Cross-app workflows deserve another boundary. Adobe describes a possible agent bringing in a Google Docs brief and sharing results through Slack when connected to those tools. A team should approve the assets and destination separately from permission to edit the project. The convenience of one instruction should not erase the difference between preparing an export and sending it to someone.

## What remains unknown

The release announcement does not establish a public launch date, detailed installation steps, final supported agent list or standalone MCP pricing. It also does not justify assuming that every model request or connected service stays on the computer simply because the integration is called local.

For now, evaluate the beta tools you can actually access and keep the 2027 integration out of client delivery promises. When it arrives, the important test will be how much usable work it leaves for the next human editor, not how impressive the first automated pass looks.

I’m Paras. I work at the intersection of AI, engineering and distribution.

I help technical teams explain new products and workflows without turning the details into marketing language.

[Book a 30-minute call](https://cal.com/paras-madan/30min).