# How to Use the Adobe Creative Cloud MCP for Batch Editing (Photographers)
> Wire Adobe's Lightroom + Express APIs into Claude via MCP and chain with the Photographer Vault to batch-edit a wedding gallery, draft delivery copy, and stage social posts — without leaving the conversation.
**Author:** [Alex Lowe](https://theaicareerlab.com/about) — Founder, The AI Career Lab
**Published:** 2026-05-24
**Canonical URL:** https://theaicareerlab.com/blog/adobe-creative-cloud-mcp-photographers-batch-editing
**Profession:** photographer
**Category:** how-to
**Tags:** photographer, photography, MCP, Adobe, Lightroom, batch editing, gallery delivery, agentic AI, 2026
---The post-shoot workflow for a wedding photographer follows a brutally consistent pattern: cull, edit, export, deliver, post, follow up, archive. Eight hundred frames in, three hundred and fifty out, dozens of variants for social, gallery delivery, vendor pitches, and (in 2026) the AI-trained-on-similar-look prompts you don't actually use.

The culling step is a solved problem — AfterShoot and Imagen do that better than any general AI. The interesting agentic surface is everything *downstream*: applying your studio preset across the gallery, exporting for delivery, drafting the email that goes with it, generating the social calendar for the next two weeks, sending the vendor recap. That's where the [Adobe Creative Cloud MCP](https://developer.adobe.com/photoshop) and the [Photographer AI Cowork Vault](https://clowealex.gumroad.com/l/tfixf) come in.

> 💡 **The stack.** Adobe MCP handles the file ops (preset application, export, asset retrieval). The [Photographer Vault](https://clowealex.gumroad.com/l/tfixf) is the agentic layer that turns those files into gallery delivery emails, social-calendar posts, and vendor pitches in your studio voice. Always-on voice-keeper guard. **$9 one-time** — both Claude and Microsoft 365 Copilot plugins.

## What the Adobe Creative Cloud MCP actually does

Adobe's API surface is wider than most photographers realize. Lightroom Classic exposes preset application and batch export. Photoshop has Generative Fill and image-edit endpoints. Adobe Express has bulk template rendering. The MCP wraps the common photographer-relevant ones:

- **`apply_preset`** — given a folder of selects + a named preset (your "warm wedding" or "moody portrait" preset), apply across the folder
- **`batch_export`** — render JPEGs at delivery res (1080×1620 for galleries, 1080×1080 for Instagram), with metadata stripped if you want
- **`generative_fill`** — Photoshop's Generative Fill via API; useful for object removal on backgrounds (the catering truck in the ceremony shot)
- **`express_render`** — Adobe Express templates rendered with your selected images; useful for social posts with overlay text

What it doesn't do: cull. That's AfterShoot's job, and you've already done it before this point.

## Pre-flight

- **Claude Cowork** (desktop) or **Claude Code**
- A **Creative Cloud subscription** (any tier — individual works)
- An **Adobe Developer account** at developer.adobe.com — free; this is where you generate the OAuth credentials the MCP uses
- The **[Photographer AI Cowork Vault](https://clowealex.gumroad.com/l/tfixf)** installed in your Cowork Project
- Your selects already culled (by AfterShoot or by hand) sitting in a folder Claude can read — Dropbox, Drive, or a local path

## Configure the MCP server

```json
{
  "mcpServers": {
    "adobe-cc": {
      "command": "npx",
      "args": ["-y", "@adobe/mcp-server"],
      "env": {
        "ADOBE_CLIENT_ID": "your-client-id",
        "ADOBE_CLIENT_SECRET": "your-client-secret"
      }
    }
  }
}
```

The first call will trigger an OAuth flow in your browser. Sign in with the same Adobe ID that runs your Lightroom.

## Run a delivery-batch workflow

You've shot a wedding, AfterShoot culled to 350 selects, you've reviewed and approved. The folder is sitting in Dropbox at `~/Dropbox/Weddings/2026-05-15-Smith-Wedding/selects/`.

Inside your Cowork Project:

```text
Use the Adobe MCP to apply my "warm-wedding-v3" preset to the folder
/Dropbox/Weddings/2026-05-15-Smith-Wedding/selects/

Then batch-export at 2400px on the long edge, JPEG quality 90, metadata stripped.
Output: /Dropbox/Weddings/2026-05-15-Smith-Wedding/delivery/
```

The MCP applies the preset across all 350 selects, exports to the delivery folder. Takes a few minutes (Adobe runs the job server-side, no local processing).

## Chain it with the vault for delivery

With the gallery ready, switch to the vault skills:

```text
/gallery-delivery-email
Couple: Sarah & Mike Smith
Wedding date: May 15, 2026
Venue: [Venue]
Gallery: [link to delivered gallery — Pic-Time, ShootProof, etc.]
Notable moments: [3 you remember — the dad's speech, the dog showing up, the rain]
Tone: warm, personal, not generic
Deliverable count: 350 images
Print sales: enabled — gently mention print options
```

The vault drafts the email in your studio voice. The print-sales mention is calibrated (helpful, not pushy). The voice-keeper guard fires if the draft drifts into stock-photographer cliché. You review, hit send.

## Chain into the social calendar

While you have the delivery context loaded:

```text
/social-calendar-from-wedding
Couple: Sarah & Mike Smith
Selects to feature: [pick 8 — vault asks; you can paste filenames]
Platforms: Instagram (3 posts + 2 reels), Facebook (3 posts), TikTok (1 reel)
Schedule: spread over the next 21 days
Tag suggestions: venue, florist, planner, DJ — let me know what's appropriate
Voice: my studio voice (already loaded)
Compliance: client signed off on use in marketing? [vault asks before generating]
```

Out comes a calendar — captions, hashtags, scheduling suggestions, and (if you ran `/setup-wizard` with vendor partner info) draft tag mentions for the planner, venue, florist. The vault asks for client sign-off before generating; if Sarah & Mike opted out of marketing use in their contract, the calendar comes back empty with a one-line explainer.

## Chain into vendor pitches

Same context, different output:

```text
/vendor-pitch-from-wedding
Couple: Sarah & Mike Smith
Vendors I want to pitch as future referral partners: [planner name], [venue]
Pitch angle: 3 best shots of their work in action
Format: email + a small share-link to the 3 hero images via Pic-Time
```

The vault drafts the pitch, you review, you send. Each vendor gets a personalized email with three of *their* moments in the shoot — much higher conversion than a generic "great working with you" note.

## The voice-keeper guard, working ambient

While all of this is drafting, the vault's voice-keeper guard runs passively. It compares the generated text against the voice samples you provided to the `/setup-wizard` (a few of your own past emails, social captions, anything that captures how *you* sound). If the draft drifts toward generic wedding-photographer cliché — "magical day," "your love story," "couldn't have asked for more" — the guard flags it.

You don't invoke the guard. It invokes itself.

## Common failure modes

- **Preset doesn't transfer cleanly.** Lightroom Classic presets that rely on local masks (the AI subject/sky masks) don't always behave identically through the API. Spot-check 10 frames after the batch; if you see drift, run the preset locally in Lightroom for those specific shots.
- **Adobe API rate limits.** Free tier gets you 25 API calls/day. For a single wedding that's plenty (one batch preset + one batch export = 2 calls). If you're processing 5 weddings in a weekend, upgrade to the paid tier.
- **Voice guard fires too aggressively.** Means your voice samples don't have enough range. Run `/setup-wizard` again and feed it 5–8 samples instead of 2.
- **Print-sales mention reads pushy.** The vault has three tone settings for the print mention: `gentle`, `featured`, `none`. Default is `gentle`. Tune in `/setup-wizard`.

## When you'd skip this stack

- **You shoot < 6 weddings a year.** Manual delivery is faster than setup.
- **You use a non-Adobe workflow (Capture One, Lightroom mobile-only).** The MCP is Adobe-specific. The vault still applies (drafting + social) but you'd handle file ops manually.
- **Your studio voice is so specific that even the voice-keeper guard misfires.** Two-line jokes, dialect-heavy writing, very short sentences — these are hard to capture from samples. Stay in manual mode for delivery emails until the voice samples are dialed in.

## Sources

- Adobe: [Photoshop API documentation](https://developer.adobe.com/photoshop)
- Adobe: [Lightroom Classic API (developer)](https://developer.adobe.com/lightroom)
- Anthropic: [Model Context Protocol (MCP) introduction](https://modelcontextprotocol.io)
- VSCO: [Photographers and AI: Industry Research Report 2026](https://www.vsco.co/research/photographers-ai)
## Frequently asked questions

### Does this replace AfterShoot or Imagen?

No — those tools own the culling+editing-suggestion layer and they're excellent at it. This stack is the layer above: once AfterShoot has done its pass and you've approved the picks, the Adobe MCP applies your preset, exports for delivery, and the vault drafts the gallery copy + social posts. Different jobs.

### Do I need Creative Cloud teams or just individual?

Individual works. Adobe's API requires a Creative Cloud subscription (any tier) and a developer registration at developer.adobe.com. The MCP authenticates via OAuth; the same login that runs your Lightroom Classic.

### Does the vault handle AI-disclosure in client contracts?

Yes. The vault's contract templates ship with 2026 AI-edit transparency language by default (per the trend research showing 83% of photographers now use AI somewhere in their workflow). The disclosure is opt-out, not opt-in — you'd have to actively remove it.

---

*Canonical version: https://theaicareerlab.com/blog/adobe-creative-cloud-mcp-photographers-batch-editing*
*This document is the Markdown companion served for AI crawlers and answer engines. See the canonical URL for the rendered version with navigation, related content, and interactive elements.*