Expose Firefly generation (image + video) via MCP/API so it can be driven from Claude and other AI agents

Forum|Forum|24 days ago
August 16, 2026
3 replies
214 views

Adobe already ships an MCP connector that lets Claude reach Creative Cloud — asset storage, Lightroom-style adjustments, background removal, vectorise, InDesign merges, video render. It's genuinely good. But the one thing it can't do is the thing Firefly is actually for: generate an image or a video from a prompt.

That means my workflow is split down the middle. I plan a sequence with Claude — shot list, prompt text, aspect ratios, continuity notes — and then I have to hand-carry every prompt into the Firefly web UI one at a time, download the outputs, re-upload them, and manually keep track of which frame is which. For a 7-episode vertical micro-serial, that's hundreds of context switches for work the agent could already orchestrate end to end.

Higgsfield shipped an MCP server this spring that does exactly this, and it's now the default entry point for a lot of us: connect once, describe the shot, the agent picks the model, fires the generation, polls, and returns the clip in chat. It works from Claude web, desktop and Claude Code. No API key — OAuth through the account you already pay for. The result is that Firefly, which has better provenance, better integration with the rest of the Adobe stack, and a licensing story no one else can match, is losing agent-driven work to a competitor purely on plumbing.

What I'm asking for:

Text-to-image and text-to-video generation tools in the existing Adobe MCP server — same auth, same asset storage, outputs landing straight in Creative Cloud Files.
Availability on individual Creative Cloud / Firefly plans, not enterprise-only Firefly Services contracts. The people building this way are mostly solo creators and small studios.
A CLI for terminal-based agents, so the same generations can run inside scripted pipelines.
Batch and reference support — style/character reference images, multi-shot batches, seed control. Consistency across shots is the whole game for narrative work.
Content Credentials preserved on every asset returned through the API. This is Adobe's genuine differentiator, and it should be the default, not something I have to reattach later.

Why this is worth building: agent-orchestrated generation isn't a niche. It's becoming the way serialised and high-volume creative work gets made. Adobe already has the models, the storage, the editing tools, and the connector. The generation endpoints are the missing link, and without them the connector reads as a nice editing utility rather than a production environment.

G

Gleeful_Penguin2720

Participant

Hi Hugo Torres,

Thanks for the detailed write-up. This is exactly the kind of feedback that's useful for us, so I appreciate you laying it out with specific asks instead of just "please add this."

You're right that the current Adobe connector for Claude covers editing, asset search, and document/video transforms, but doesn't expose text-to-image or text-to-video generation directly. So for now, prompt-to-asset still has to happen in the Firefly web app itself, which is exactly the workflow split you're describing.

I can't promise a timeline or commit to the five specific asks (generation endpoints, non-enterprise availability, CLI, batch/reference support, Content Credentials on API-returned assets), although I think the ideas are great, especially the CLI/API point for scripted pipelines, since that's a real gap for terminal-based workflows right now. I'll escalate the suggestion internally to the right team. Feedback like this, with a concrete use case (serialized/episodic video work) and a competitor comparison, carries a lot more weight than a generic feature request, so thank you for taking the time to write it up properly.

Keep an eye here in the community, because me or one of my colleagues will update this thread or create a new one with the update if we hear anything back.

Thanks

Matt

Takis_Pagonis

Participant

I can confirm this from an active production. I am currently finishing a short film, produced entirely with AI generation, working inside Claude with an agent that manages my shot list, prompts, references and continuity.

My subscription includes Firefly with partner models, exactly the models I use in production. But because the Adobe for Creativity connector exposes no generation, my agent cannot use them. It prepares the prompt and the reference images, and then I hand carry everything into the Firefly web UI one shot at a time, download, rename, and file the outputs manually. For a 35-shot film with strict character and set continuity, this is hundreds of manual steps that the agent could orchestrate end to end.

The result is what the original post describes: I route production to platforms whose MCP lets the agent generate directly, and my Adobe credits stay underused, not because of the models, which are excellent, but purely because of the missing plumbing.

Points 2 and 4 of the request matter most to me: availability on individual Creative Cloud plans, and reference image support, because consistency across shots is the whole job in narrative work.

K

knowledgeable_face9b25

Participant

I can confirm this is a real issue.

I purchased Creative cloud specifically to use Firefly with Claude through the Adobe for Creativity MCP connector.

After testing, the connector exposes editing tools but not Firefly image generation.

I had to move my workflow to OpenArt MCP because Claude can directly call image and video generation there

Please expose Firefly Image and Firefly Video generation to Creative Cloud subscribers through the existing MCP connector.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.