Adobe previews MCP for Photoshop and Premiere at MAX 2026
Adobe announced at its MAX conference in Miami on November 10, 2026 that it is previewing local MCP integrations, which let third-party AI agents edit native Photoshop, Illustrator, Premiere and After Effects project files on a user’s machine. It also expanded the Firefly AI Assistant in beta and introduced always-on agents in preview. For developers, the MCP part matters most: it is Adobe’s first step toward letting outside agents drive its desktop tools.
What’s new
Details below come from IT Brief’s report on the announcements and Engadget’s coverage. We could not open Adobe’s own press release, so wording and dates should be checked against it.
- Local MCP integrations (preview): third-party agents can make changes locally in native Photoshop, Illustrator, Premiere and After Effects project files. Layers, vectors, bins and sequences stay editable, according to IT Brief.
- Firefly AI Assistant (beta): an expanded version inside Adobe’s Creative Agent that carries out multi-step tasks. Users can set formats, colours, brand guidelines and characters once, and choose a model or leave selection automatic.
- Planning mode: per Engadget, you can review and edit the workflow the assistant proposes before approving it.
- Always-on agents (preview): they handle recurring background work such as organising incoming assets, checking quality and preparing content for different channels. In Engadget’s demo the assistant offered to organise uploaded footage, apply LUTs, clean up audio and back it up, and the user approved the steps.
- Firefly Builder (private beta): turns text prompts into prototypes of websites, presentations or apps without code.
- Premiere mobile agent: a natural-language editing agent in private preview, per Engadget.
Neither article mentions pricing. IT Brief gives no availability dates for these features.
What it means for developers
MCP, the Model Context Protocol, is the open standard many AI assistants use to call external tools. Adobe supporting it locally means an agent you build, or a chatbot your team already uses, could eventually edit a layered PSD or a Premiere sequence rather than just exporting flattened files.
Today there is little to try: the integrations are a preview, and the sources do not say how to apply, which agents will be supported or what the interface looks like. One outlet, relayed by TechFlow from The Verge, reports that agents from OpenAI, Google and Anthropic are expected to be able to modify local project files, but that list is a report, not a confirmed Adobe statement.
If you build creative automation, the useful preparation is to keep your tool definitions separate from any one application, so that adding Adobe as another MCP server later is a configuration change. Watch Adobe’s developer announcements for access details.
How it compares
Per IT Brief, the preview’s stated aim is that project structure stays editable, rather than agents producing flat images. Separately, we covered Adobe and Disney’s Firefly partnership earlier this week.