# Adobe Run-Workflow MCP

> Adobe's second hosted MCP — compose and run Firefly Creative Production batch pipelines.

- **Category:** Editing & Post
- **Vendor:** Adobe (official)
- **Pricing:** paid
- **Verified:** 2026-09-01

## What it does

The agent front end to Firefly Creative Production, Adobe's graph-based batch pipeline for images, video and 3D. An agent lists the available workflow actions, reads their schemas, composes a graph from a plain-language brief, uploads assets, submits the batch, and polls until the outputs land — then publishes the graph as a reusable endpoint or saves it into Workflow Builder. Where Adobe for Creativity edits one asset at a time in conversation, this is the thing you point at 400 frames, product turntables or a delivery matrix of aspect ratios.

## Connect

- Remote endpoint: `https://run-workflow.adobe.io/mcp`
- Remote headers required: `Authorization`, `x-api-key`
- Claude Code: `claude mcp add --transport http run-workflow https://run-workflow.adobe.io/mcp --header "Authorization: Bearer YOUR_IMS_TOKEN" --header "x-api-key: YOUR_API_KEY"`

**Auth:** api_key — Both an Adobe IMS access token and a Run-Workflow API key are issued by your org admin — there is no self-serve signup

## Capabilities

[batch-processing](https://mcp.film/capabilities/batch-processing.md) · [workflow-automation](https://mcp.film/capabilities/workflow-automation.md) · [background-removal](https://mcp.film/capabilities/background-removal.md) · `color-grade` · `video-processing` · `3d-render` · [remote-mcp](https://mcp.film/capabilities/remote-mcp.md)

## Sample tools

`list_actions` · `get_action_schema` · `compose_workflow` · `upload_asset` · `run_workflow_submit` · `run_workflow_get_status` · `cancel_workflow` · `list_workflow_history` · `inspect_run` · `get_workflow_examples` · `publish_workflow` · `save_workflow_to_acp`

## Field notes

Enterprise-gated and priced that way: Firefly Creative Production is an add-on to select Adobe enterprise plans, and both credentials come from your org admin rather than a developer console, so an independent filmmaker cannot connect this. Bearer tokens are IMS access tokens and expire — expect to re-add the server, not set it once. Everything is async: run_workflow_submit returns a batchId and you poll run_workflow_get_status, which matters for video and large batches. Presigned asset URLs expire in about an hour and break if a single character is retyped. The framing is marketing production, not editorial — the shipped starter templates are standardized packshots, 360-degree spin video and composite imagery, and the broadly available preset actions are remove background, crop and colour grade. Verified 1 Sep 2026 from Adobe's own sources: the endpoint and http transport from the .mcp.json in github.com/adobe/skills (plugins/creative-cloud/run-workflow), the tool names from the run-workflow SKILL.md in the same repo, and the install command from Adobe's helpx install page. helpx.adobe.com times out for automated fetchers, so the entitlement details here come from Adobe documentation read through search excerpts rather than a direct page load, and no live handshake was possible without an org token. For conversational single-asset work on a personal Adobe account, use adobe-creativity instead.

## Verification

- Status: Freshly checked (checked today)
- Added: 2026-09-01
- Last verified: 2026-09-01
- Machine JSON: https://mcp.film/api/mcps/adobe-run-workflow.json

## Links

- Site: https://business.adobe.com/products/firefly-business/firefly-creative-production.html?utm_source=mcp.film&utm_medium=referral&utm_campaign=directory&utm_content=adobe-run-workflow%3Asite
- Docs: https://helpx.adobe.com/firefly/web/work-with-enterprise-features/creative-production/run-workflow-mcp-overview.html?utm_source=mcp.film&utm_medium=referral&utm_campaign=directory&utm_content=adobe-run-workflow%3Adocs
- Repo: https://github.com/adobe/skills

---

Structured data: https://mcp.film/api/mcps/adobe-run-workflow.json · Directory: https://mcp.film