**Adobe MAX: a local MCP that exposes Photoshop and Premiere to chatbots, and Firefly becoming a creative agent**

Adobe MAX 2026: a local MCP opens Photoshop and Premiere to ChatGPT, Claude, and Gemini

🔎 Adobe has just made its tools controllable by any AI agent

At its MAX event in Miami on November 10, 2026, Adobe crossed a threshold few expected to see at this pace: the company behind Photoshop is releasing a local Model Context Protocol (MCP) that lets ChatGPT, Claude, or Gemini directly use the features of Illustrator, Photoshop, After Effects, and Premiere Pro. Not a watered-down cloud copy of these tools — the real software, on your machine, with their layers, vector paths, bins, and sequences.

In the same move, Firefly becomes a "proactive and always on" agent: it runs recurring tasks in the background, revises its own action plan, and waits for your approval on the final result. Adobe is also adding a prototyping tool named Builder (in private beta), positioned head-to-head against Figma, along with an AI video editing tool and the first fruits of the Topaz Labs acquisition.

Why does this matter now? Because the question is no longer "will AI enter creative tools?" but "who controls the agent?". By releasing a local MCP, Adobe is choosing not to keep that control for itself. Dylan Field, Figma's CEO, said in late October that MCP "is not a perfect standard" and that it mostly benefits frontier labs. Adobe just proved him right — and owned it.

The Essentials

• Local Creative Cloud MCP: ChatGPT, Claude, and Gemini can manipulate the native project files of Photoshop, Illustrator, After Effects, and Premiere — layers, vectors, bins, and sequences remain hand-editable, with the ability to take over at any time (The Verge).
• Firefly becomes a "proactive and always on" agent: recurring background tasks, a revisable plan, human validation of the final result, first in Firefly AI Assistant.
• Firefly Builder: a prototyping tool in private beta, a direct competitor to Figma, plus an on-brand graphics generator and object-targeted image retouching.
• AI video editing: assembling generated clips, images, and sound effects directly in Firefly.
• Topaz Labs (acquired by Adobe) delivers Wonder 4 (upscaling/denoising) and ImageHDR.
• Private beta of the local MCP in early 2027; Illustrator, Photoshop, After Effects, and Premiere available at launch.
• History: since December 2025, ChatGPT can call Photoshop, Express, and Acrobat; April 2026, Claude connector (50+ tools); September 2026, Google (Fast Company).

Recommended Tools

For free alternatives while waiting for local MCP to go mainstream, our selection of the best free AI tools of November 2026 remains the right starting point.

What does this local MCP actually change?

The short answer: for the first time, an external AI agent gets the same tools as Adobe's native agent, on your machine, with full access to the structure of your project files.

This is the key point highlighted by Fast Company: the local MCP reverses the direction of control. Until now, cloud connectors (ChatGPT since December 2025, Claude since April 2026 with more than 50 tools, Google since September 2026) gave agents remote access to hosted Adobe features. With the local MCP, the external agent works directly within the applications installed and licensed locally.

Concretely, this means:

• Files stay native. The agent modifies layers, vector paths, bins, or sequences — not a flattened export. You can take back control at any time, with your mouse.
• Chaining becomes possible. An agent connected to other MCP servers can chain Google Docs → Adobe → Slack without human intervention between steps.
• The apps must be installed and licensed locally. No circumventing licenses: the agent inherits your rights.

Deepa Subramaniam, VP at Adobe, sums up the philosophy: "no need to limit what the MCP endpoint can expose". In other words, Adobe doesn't impose a restricted whitelist of functions — Illustrator, Photoshop, After Effects, and Premiere will be exposed from launch.

The nuance everyone will skim over

Fast Company says it bluntly: Adobe can no longer answer for what the external agent does. When Claude or Gemini manipulates your .psd file locally, it's the third-party lab's model making the decisions — with the errors, hallucinations, and unpredictable behaviors that implies. For studios, this will quickly raise the question of backups and versioning before letting an agent "clean up 200 layers".

Firefly, the "proactive and always on" creative agent

Firefly no longer just responds to prompts: Adobe now presents it as a proactive and always-on agent, in preview in Firefly AI Assistant.

The way it works, as described by The Verge:

1. Recurring background tasks — declinating a campaign into ten formats, generating the visuals for an editorial calendar, preparing print and web exports.
2. Revisable plan — the agent proposes a sequence of steps, which you can modify before execution.
3. Approval of the final result — nothing is published or delivered without human validation.

It's the same orchestrating agent architecture that Adobe laid out in June 2026, when the Creative Agent extension allowed the user to describe a desired outcome and the assistant to orchestrate multi-step workflows across Firefly and the Creative Cloud apps (Adobe News). What's new at MAX is the permanence: the agent is no longer triggered only on demand, it monitors and anticipates.

My take: this is the right angle of attack. Reactive agents (prompt → result) don't change the lives of creatives, they change their click speed. An agent that handles recurrence — the declinations, the exports, the brand checks — attacks the real cost of the creative profession.

The new Firefly capabilities announced at MAX

According to TechCrunch:

• Builder: a prototyping tool in private beta, a claimed competitor to Figma.
• On-brand graphics: generation of visuals that automatically comply with a brand guideline.
• Targeted image retouching: editing a specific object without touching the rest of the image — the kind of task where generalist models still fail.
• AI video editing: assembling clips, images, and sound effects generated in a single flow.

Builder : Adobe takes on Figma head-on

Firefly Builder isn't just another feature — it's a strategic admission. Adobe never managed to catch up with Figma on prototyping — the abandoned $20 billion acquisition, blocked in December 2023, remains fresh in everyone's memory. Builder is the AI-powered answer: instead of cloning Figma, Adobe proposes generating and iterating on prototypes in natural language.

The timing is spicy. In late October 2026, Dylan Field judged that MCP "is not a perfect standard" and that it mainly benefits frontier labs (TechCrunch). Translation: agent interoperability standards primarily serve OpenAI, Anthropic, and Google — not application vendors. Adobe, by releasing its own local MCP about ten days later, is doing exactly the opposite — and forcing Figma to react.

Two possible readings:

• The optimistic reading: Adobe is normalizing interoperability for creative agents. If Adobe's local MCP becomes a reference, creatives gain freedom — their favorite agent drives their tools, with no lock-in.
• The cynical reading: Adobe, the leader in creative software, has nothing to lose by opening up its APIs. It's Figma, the challenger in AI prototyping, that has an interest in keeping its ecosystem closed. Field's remarks about "MCP's flaws" also serve to justify a more integrated model — his own.

The truth probably lies somewhere in both at once. And for users, the outcome of the Builder vs Figma duel will matter less than the precedent: a major vendor exposing its native tools to third-party agents.

Photoshop, Premiere, Lightroom: AI in Everyday Tools

Beyond the agents, Adobe has rolled out its classic MAX AI update. The most notable features (TechCrunch):

Video object removal in Premiere is the feature that, in my opinion, will have the greatest immediate impact. What previously required the work of a compositing specialist—erasing an unwanted passerby, a logo, a cable—is becoming a matter of seconds. Photoshop's relighting is in the same vein: relighting a portrait after the fact was nearly impossible without a reshoot.

These functions remain "classic" in the sense that they live within the application, driven by the user. The local MCP, however, allows an external agent to chain them: "relight this packshot, remove the object in the background, export in three formats"—without opening Photoshop.

Topaz Labs: Wonder 4 and ImageHDR join Adobe

Adobe has also drawn the consequences of its acquisition of Topaz Labs. The specialist in upscaling and image restoration is delivering two products: Wonder 4, dedicated to upscaling and denoising, and ImageHDR (TechCrunch).

This is a signal not to be underestimated. Adobe hasn't integrated Topaz into Creative Cloud for now — the products remain distributed under their own brand. But the logic is clear: AI-powered restoration and upscaling have become mass-market needs (photo archives, average-quality footage upscaled to 4K, generated images that need cleaning up), and Adobe preferred to buy the market leader rather than play catch-up.

For videographers working with drone footage or archives, Wonder 4 is probably the most immediately useful new release from MAX — even ahead of the local MCP.

Adobe's MCP Strategy Against Figma's Skepticism

Let's review the sequence, because it tells a story about the entire industry:

1. December 2025: ChatGPT can call Photoshop, Express, and Acrobat via cloud connectors.
2. April 2026: Claude obtains a connector with over 50 Photoshop, Illustrator, and Premiere tools, on the cloud side.
3. September 2026: Google joins.
4. Late October 2026: Dylan Field estimates that MCP "is not a perfect standard" and favors frontier labs.
5. November 10, 2026: Adobe publishes its local MCP and gives external agents parity with its native agent.

What this timeline shows is that Adobe first tested agentic capabilities in a controlled environment (cloud connectors, native agent), then opened the floodgates when the model proved its value. The official Firefly documentation on the "Run-Workflow MCP" already describes this ambition: connecting AI agents to Adobe creative workflows via natural language (Adobe).

Field's counterpoint deserves to be taken seriously nonetheless. MCP is a young standard, its specifications evolve quickly, and the labs that train the models (OpenAI, Anthropic, Google) indeed capture a disproportionate share of the value: they are the ones who decide what the agent can do and how it does it. Adobe responds to this with a trump card — creative data remains with the user, in native files, on their machine. The agent's cloud stops at the port of your workstation.

To keep up with this kind of announcements as they happen, our monitoring of recent AI news is continuously updated.

What This Changes for Your Creative Workflows

Three scenarios become realistic as soon as the 2027 beta:

Multi-tool chaining. The example from The Verge: an agent reads a brief in Google Docs, produces the visuals in Photoshop, then sends the exports to Slack. None of these steps is new; chaining them together without a human in the middle, however, is.

Delegating the repetitive work. Format variants, campaign adaptations, multi-resolution exports — the work nobody likes doing. Firefly always-on targets exactly that, and the local MCP lets you plug in the agent of your choice.

Assisted video editing. Between object removal in Premiere, pro color grading, and AI-powered clip assembly in Firefly, the barrier to entry for editing keeps dropping. For an analysis of the current tools, our guide to the best AI tools compares the approaches.

One note of intellectual honesty: we're still at the stage of announcements and private betas. The MAX demos are impressive, but the real value will be judged on how reliably agents handle complex projects — and on how Photoshop deals with an agent that "misunderstands" a client file. Those who already run agents on real browsers and real tools know that the gap between demo and production remains wide — our review of OpenCode Browse and the agents that drive your browser documents it in detail.

❌ Common Mistakes

Mistake 1: believing that local MCP replaces applications

No. Apps must be installed and licensed locally — the MCP exposes their capabilities, it doesn't replace them. You'll still need your Creative Cloud subscriptions, and you'll still need to know how to take over a file manually when the agent goes off the rails.

Mistake 2: letting an agent work unsupervised on production files

Adobe can no longer vouch for what an external agent does (Fast Company). Solution: work on copies, version systematically (Creative Cloud's native versioning helps), and keep human approval for anything that goes out to a client.

Mistake 3: confusing Firefly Builder with a Figma replacement

Builder is in private beta and targets AI-assisted prototyping, not the entirety of Figma's design workflow (collaboration, design systems, dev handoff). Comparing it feature by feature with Figma today makes no sense — and vice versa.

Mistake 4: waiting for local MCP to structure your workflows

The beta arrives in early 2027. In the meantime, the existing cloud connectors (ChatGPT since December 2025, Claude since April 2026) already make it possible to automate part of the work. Teams that will have documented their repeatable processes will be the ones that get the most out of local MCP on the day it ships.

❓ Frequently Asked Questions

Is Adobe's local MCP available now?

No. It enters private beta in early 2027, first for Illustrator, Photoshop, After Effects and Premiere Pro. The existing cloud connectors (ChatGPT, Claude, Gemini) remain the only option for driving Adobe tools by agent until then.

Are my files sent to Adobe's cloud?

No, that's the whole point of the local MCP: the external agent works on your machine, in your locally installed and licensed applications. However, be careful: the model driving the agent (ChatGPT, Claude, Gemini) runs, for its part, in its vendor's cloud — your prompts and instructions pass through there.

Do you need a specific subscription for Firefly Agent?

Firefly AI Assistant is included in the Firefly and Creative Cloud plans, with generation limits depending on the plan. The always-on features are in preview and their final pricing had not been announced at MAX (November 2026) — check on adobe.com.

Is Firefly Builder available?

No, Builder is in private beta. Adobe did not announce a general availability date at MAX. Interested teams can request access via Adobe's Firefly page.

Are Wonder 4 and ImageHDR included in Creative Cloud?

No. Topaz Labs products remain distributed under their own brand and sold separately on topazlabs.com. Future integration into Creative Cloud is plausible but has not been announced.

Is MCP really a reliable standard for creative tools?

That's the debate opened by Dylan Field, who considers the standard "not perfect" and favorable to frontier labs. Adobe's bet: maturity will come through adoption, and a major vendor exposing its native tools will accelerate that adoption. To be continued in 2027.

✅ Conclusion

With this local MCP, Adobe is making the most interesting choice of MAX 2026: opening its creative tools up to third-party agents rather than keeping agentic capabilities locked in a walled garden — even if that means, despite itself, proving Figma's skepticism about MCP right. The real battle of 2027 won't be Firefly vs. Figma, but the one over your workflows: those who know how to cleanly delegate repetitive tasks to an agent will have a head start. To learn more, explore our guide on creating an AI agent and start building your own today.