Adobe MCP Server: What It Does and How to Connect Adobe to AI in 2026
Yes — Adobe has an official MCP server, but “Adobe MCP” is more fragmented than one connection. The one most people searching for want is Adobe for Creativity, a hosted remote MCP connector (adobe-creativity.adobe.io/mcp) that Adobe and Anthropic launched in Claude on April 28, 2026. It exposes 50+ tools across Photoshop, Lightroom, Illustrator, Firefly, Premiere, Express, InDesign, and Adobe Stock — from a single prompt, no app-switching. There are also separate official servers for developers and for enterprise Experience Manager, plus community projects that drive the pro desktop apps directly.
Before you set any of it up, the thing worth knowing: an MCP server hands Adobe to an AI inside a conversation you start. It’s a doorway, not a worker. Nothing watches a folder of files for you, nothing fires when a new asset lands, and nothing runs while the chat is closed. Here’s exactly what the Adobe MCP does, how to turn it on, where it stops — and what to use when you want Adobe work that runs on its own.
What the Adobe MCP server does
Model Context Protocol (MCP) is the open standard that lets an AI client — Claude, ChatGPT, Cursor, VS Code, and others — talk to an outside app through a shared interface. “Adobe MCP” isn’t one thing; it’s a few official servers plus community ones:
- Adobe for Creativity (
adobe-creativity.adobe.io/mcp, remote, GA since April 2026) — the flagship. A hosted connector giving an AI natural-language access to Firefly generation and Express-tier editing across Photoshop, Lightroom, Illustrator, Premiere, InDesign, and Adobe Stock. It’s available today primarily in Claude (chat, Cowork, and Desktop). Guest users get roughly 40 free tools; signing in with a free or paid Adobe account unlocks more tools, storage, and higher limits. - Adobe for ChatGPT (launched December 2025) — brings Photoshop, Express, and Acrobat editing into ChatGPT itself, built on MCP but delivered as an app inside ChatGPT rather than an endpoint you add elsewhere.
- Adobe Express Developer MCP (local,
npx) — a different job entirely: it helps developers build Express add-ons with documentation search and TypeScript definitions. It does not edit your Express content.
With the Adobe for Creativity connector on, an AI client can:
- Generate images and assets — “make a commercially safe hero image of a mountain lake at dawn” answered by Firefly, right in the chat.
- Edit at the Express tier — adjust, crop, remove backgrounds, apply effects, and produce social or marketing layouts from a plain-language description.
- Reason across the toolset — pull a Firefly generation into an Express layout and export a set of sizes without opening a single app.
It’s genuinely useful for ad-hoc creative work: describe the outcome, get a real asset back, iterate on the spot.
How to set up the Adobe MCP server
The Adobe for Creativity connector is the quick path — no code, no hosting:
- In Claude, open the connector directory and enable Adobe for Creativity (or, in a client that supports remote MCP, add a server pointing at
adobe-creativity.adobe.io/mcp). - Start using it as a guest for the free tools, or sign in with your Adobe account through the OAuth prompt to unlock the full set, storage, and higher limits.
- Confirm the tools appear, then start a chat and ask it to generate or edit something.
Two caveats worth setting expectations on. First, this connector works at Express and Firefly level, not the full professional feature sets of desktop Photoshop or Premiere. Second, if you want an AI to script the actual desktop pro apps — full-power Photoshop layers, Premiere timelines — that’s still community territory: projects like mikechambers/adb-mcp and matrayu/adobe-mcp drive the installed apps locally through a UXP plugin you run yourself, with no Adobe support behind them.
Where the Adobe MCP stops
None of this is a knock on MCP — it’s just the shape of the protocol. Four limits show up the moment you want more than a conversation:
- It only works inside a chat you start. Close the window and nothing happens. The AI doesn’t watch your assets or your inbox; it waits for you to ask.
- No triggers. A new file dropped in Dropbox, a form submission that needs a matching graphic, a product photo that needs resizing on upload — none of these can start anything through MCP. There’s no “when this happens, generate that.”
- It’s one app at a time. The Adobe connector knows Adobe. Getting a finished asset into your CMS, a Slack channel, and a Google Drive folder means wiring up (and authing) a separate MCP server for each, then hoping your client can juggle them in one turn.
- You own the plumbing, the scopes, and the usage limits. OAuth, your Adobe account’s tool and generation limits, and the blast radius of what the AI can do are all on you — and the community desktop servers act as your machine with no vendor review.
So the Adobe MCP is a great way to ask Adobe to make something and edit on the spot. It is not a way to make Adobe run — to have creative work happen on a schedule or in reaction to an event, across the other tools an asset touches.
Running Adobe work that doesn’t need a chat open
That “run on its own, across apps” gap is exactly where Carly fits. Carly connects to Adobe natively — no MCP server to host, no OAuth plumbing to maintain — and to the ~260 other apps it supports natively, plus anything with a public API through your own key. The difference from MCP is the important part: Carly’s workflows are triggered and scheduled, so Adobe work happens whether or not anyone has a chat window open.
A few things that MCP can’t do but a Carly workflow can:
- When a new product photo lands in a Drive folder → generate resized and background-cleaned versions with Firefly and drop them into the Shopify listing — automatically, the moment it arrives.
- Every morning → produce that day’s social graphics from a content calendar and post them to the scheduling queue.
- When a form comes in requesting a custom banner → create the asset, save it to Dropbox, and notify the requester in Slack with the link.
The non-AI steps — the moving, matching, and routing between apps — are free and unlimited, the Zapier-style backbone of the workflow. The AI steps (generating, editing, deciding) start at $35/month. You describe the outcome in plain language and Carly wires up the Adobe connection and everything downstream.
If you just want to generate and edit from a chat, Adobe’s official connector is the right tool and it’s free to start. If you want Adobe to actually do things — on a trigger, on a schedule, across every app an asset flows through — that’s the job MCP wasn’t built for, and it’s the one Carly was.
FAQ
Does Adobe have an official MCP server?
Yes. The main one is Adobe for Creativity, a remote MCP connector at adobe-creativity.adobe.io/mcp, generally available in Claude since April 28, 2026, with 50+ tools across Photoshop, Lightroom, Firefly, Express, Premiere, and more. Adobe also offers an “Adobe for ChatGPT” app, a local Express add-on developer MCP server, and enterprise MCP servers for Experience Manager and Analytics.
Is the Adobe MCP server free? You can start the Adobe for Creativity connector as a guest with roughly 40 free tools, no Adobe account required. Signing in with a free or paid Adobe account unlocks more tools, Creative Cloud storage, and higher usage limits.
Can the Adobe MCP trigger automations? No. MCP is request/response inside an AI chat — it has no triggers and nothing runs when the conversation is closed. For event- or schedule-driven Adobe work across apps, you need a workflow tool like Carly rather than an MCP server.
Can I connect Adobe to AI without coding or hosting a server? Yes. You don’t have to touch MCP or run a community UXP server at all. Carly connects to Adobe for you and lets you build the automation in plain language — describe what you want to happen and it wires up Adobe and the other apps involved, with no server to host and no code to write.
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
