Part of imagic Max

The first photo editor with a built-in MCP server

Point Claude Code, Claude Desktop, Cursor, Codex, or Copilot at your library and say what you want. imagic culls, edits in your style, and exports, all on your machine.

Start Free 500-Photo Trial Jump to Setup

Included in imagic Max, €99 once. The trial unlocks everything, no card required.

Recorded session · 21 tools

This is how your next edit could look

One real session on a folder of 40 RAWs: scanned, analysed, culled to the best 12, adjusted, graded, styled and exported, every one of the 21 MCP tools called in turn. Pick a tool below to watch that step, drag the slider, or click a frame in the library.

live session imagic

↵

Bypass permissions MCP

imagic live preview +

← →127.0.0.1:8765

imagiclive from your AI agent waiting

now editing—

Waiting for your agent to start editing a photo.

beforeafter

library

Playing the whole session

100% local The MCP server runs beside imagic on your machine. Photos never leave it.

Non-destructive Every AI edit lands in imagic's edit history. Review it, undo it, like any edit.

Any MCP client Claude Code, Claude Desktop, Cursor, Codex, Copilot, or anything MCP-compatible.

One command claude mcp add imagic, and your agent has the whole pipeline.

Style calibration

Start with 8. Train it on everything.

A guided session builds your first style profile from 8 of your own photos in minutes. From there it keeps learning without limit, from every edit you make in imagic.

Step 01 A guided start, 8 photos imagic pulls up to 8 scenario photos from your own library, covering a spread of light and subjects. Edit them your way and you have a first profile in minutes.

Step 02 It reads your real decisions Not vibes. The actual exposure, color, and crop values you set in imagic, recorded per scenario and turned into a profile that is yours alone.

Step 03 Then train it on everything Repeat sessions whenever your taste shifts, or point learn_style_from_library at your back catalog: every photo you have ever edited in imagic feeds the profile.

01golden labrador, backlit

basilica facade, seagull

02stone bridge, night

fruit stall, string lights

03temple columns, rooftops

04carved fountain mask

small dog, window light

05quadriga, waving flag

colonnade saints, grey sky

06travertine arches, EUR

colorful corner, taxis

07colonnade, looking up

aerial coastal skyline

08sparrow, stone texture

modernist arches, EUR

fountain, colonnade behind

style_profile · learning from every imagic edit

new shoot, untouched frameapply_my_style

before your style

train it deeper · edit five, match the restnew tools

›Learn my style from everything I've edited

●learn_style_from_library()

✓profile updated from your entire imagic edit history

›I edited five from this wedding, match the rest

●match_style_from_examples()

✓219 photos matched to your five examples · saved profile untouched

The honest boundary: it learns from edits made in imagic, reading the actual adjustment values you set. It can't guess your style from exported JPEGs or a Lightroom catalog.

Setup

One command and it's connected

imagic's MCP server works with any MCP client. Pick yours, paste, done.

Installed the packaged app from this site? Then there is no imagic-mcp command on your machine: the app itself is the server. Point the client at it and pass --mcp. Windows:

claude mcp add imagic -- "C:\Program Files\imagic\imagic.exe" --mcp

macOS:

claude mcp add imagic -- /Applications/imagic.app/Contents/MacOS/imagic --mcp

Add this to your claude_desktop_config.json:

{
  "mcpServers": {
    "imagic": {
      "command": "imagic-mcp"
    }
  }
}

Installed the packaged app from this site? Then there is no imagic-mcp command on your machine: the app itself is the server. Point the client at it and pass --mcp. Windows:

{
  "mcpServers": {
    "imagic": {
      "command": "C:\\Program Files\\imagic\\imagic.exe",
      "args": ["--mcp"]
    }
  }
}

On macOS the command is /Applications/imagic.app/Contents/MacOS/imagic, with the same "args": ["--mcp"].

Cursor and most other JSON-config clients use this shape. Two known exceptions: VS Code uses servers (see its tab) and Zed uses context_servers. Add this to the client's MCP config:

{
  "mcpServers": {
    "imagic": {
      "command": "imagic-mcp",
      "args": []
    }
  }
}

Installed the packaged app from this site? Then there is no imagic-mcp command on your machine: the app itself is the server. Point the client at it and pass --mcp. Windows:

{
  "mcpServers": {
    "imagic": {
      "command": "C:\\Program Files\\imagic\\imagic.exe",
      "args": ["--mcp"]
    }
  }
}

On macOS the command is /Applications/imagic.app/Contents/MacOS/imagic, with the same "args": ["--mcp"].

One command, which writes the config for you:

code --add-mcp "{\"name\":\"imagic\",\"command\":\"imagic-mcp\"}"

Or by hand in .vscode/mcp.json. Note the top-level key is servers, not mcpServers — this is the most common reason an imagic setup that works in Cursor fails in VS Code:

{
  "servers": {
    "imagic": {
      "type": "stdio",
      "command": "imagic-mcp"
    }
  }
}

Installed the packaged app from this site? Then there is no imagic-mcp command on your machine: the app itself is the server. Point the client at it and pass --mcp. Windows:

{
  "servers": {
    "imagic": {
      "type": "stdio",
      "command": "C:\\Program Files\\imagic\\imagic.exe",
      "args": ["--mcp"]
    }
  }
}

On macOS the command is /Applications/imagic.app/Contents/MacOS/imagic, with the same "args": ["--mcp"].

Tools appear in Copilot Chat's agent mode. For a machine-wide install run MCP: Open User Configuration from the Command Palette; VS Code will prompt you to trust the server the first time it starts.

One command with the Codex CLI:

codex mcp add imagic -- imagic-mcp

Or add it to ~/.codex/config.toml:

[mcp_servers.imagic]
command = "imagic-mcp"

Installed the packaged app from this site? Then there is no imagic-mcp command on your machine: the app itself is the server. Point the client at it and pass --mcp. Windows:

codex mcp add imagic -- "C:\Program Files\imagic\imagic.exe" --mcp

[mcp_servers.imagic]
command = "C:\\Program Files\\imagic\\imagic.exe"
args = ["--mcp"]

On macOS the command is /Applications/imagic.app/Contents/MacOS/imagic, with the same "args": ["--mcp"].

No AI client needed. imagic's headless mode has been scriptable since before MCP existed:

imagic --headless --scan DIR --analyse --export

Requires an activated imagic Max license or an active trial. Works with GitHub Copilot and any other MCP-compatible client too.

Prefer scripts to agents? The same pipeline also runs from in-app batch tools and the headless CLI, no MCP client involved. The photo editing automation guide covers all three routes, with command examples and instant re-culling.

The full walkthrough

Twelve minutes, start to finish

What MCP actually is, connecting imagic to your agent in one line, the real tool calls running against a wedding shoot, and what this emphatically is not. Nothing here generates a pixel.

12:31 · captions included · chapter list and the by-hand walkthrough

For the switchers

imagic vs. Lightroom, for automation

This isn't the full feature comparison, just the part that matters if you want an AI agent doing the work.

imagic

Lightroom

Price

From €19 once, MCP in Max at €99

$9.99/month

MCP / AI agent access

Built-in (imagic Max)

Not available

Scriptable CLI

Headless + MCP

Account required

Yes (Adobe ID)

Pricing

Included in imagic Max

€99 once. no subscription.

MCP and the CLI aren't an add-on. They ship in the top tier, alongside the rest of Max.

MCP server + CLI
Style calibration
Neural denoise + upscale
Semantic search

Start Free Trial Compare All Tiers

The free 500-photo trial includes MCP and the CLI. No card required, nothing to cancel.

RAWHover to see imagic Edits

edited by

Tap to see RAW

Questions

MCP & CLI questions

The specifics people ask before connecting an AI agent to their photo library.

What is MCP?

MCP (Model Context Protocol) is an open standard that lets AI assistants connect to external tools. imagic's MCP server exposes its scan, cull, edit, and export tools so an AI agent can call them directly, the same actions you'd trigger by hand in the app.

Does it work with Claude Desktop, Cursor, Codex, and Copilot?

Yes. imagic's MCP server works with any MCP-compatible client, including Claude Code, Claude Desktop, Cursor, Codex, and GitHub Copilot. Setup is a one-time config step per client.

Is my photo library safe? Does anything leave my machine?

No photos are uploaded anywhere. The MCP server runs locally alongside imagic and talks to your AI client over your own machine. Processing stays local, the same as using imagic directly.

Do I need coding skills to use this?

No. You paste one setup command or config snippet once, then talk to your AI assistant in plain English. It calls imagic's tools for you.

Does the AI edit my photos destructively?

No. Edits are stored as non-destructive adjustments in imagic's edit history, the same as manual edits. Nothing overwrites your original RAW or source files unless you explicitly export.

What does it cost?

MCP and the CLI are included in imagic Max, a one-time €99 license with no subscription. The free trial (no card required) includes full Max access for your first 500 exports, so you can try MCP and the CLI before buying anything. Lite and Plus don't include MCP or CLI.

Give your AI agent a photo editor to drive

Try the full imagic Max workflow, MCP and CLI included, free for 500 photos. No card required, no subscription, and nothing to cancel.

Start Free Trial Get imagic Max · €99