
Imagic
io.github.Lukefen31v1.4.4Updated Oct 2, 2026
AI-cull, edit and export RAW photos locally with the imagic desktop app, from any MCP client.
Overview
Lets an assistant drive the local imagic desktop photo editor: scan shoots, AI-cull, edit in your style, and export keepers.
- What it does
- The imagic MCP server is built into the imagic desktop photo editor and exposes 21 tools covering the whole photo pipeline. An assistant can index a folder of RAW and JPEG files, score sharpness, exposure, noise, composition and detail, flag duplicates and bursts, and set keep, trash or undecided status. It can apply adjustments and saved presets, read the non-destructive edit stack, learn your editing style from calibration or your edited library, match a shoot to a few hand-edited frames, and batch-export keepers. A local live-preview page shows what the agent is doing.
- When to use it
- Use it when you already edit photos in imagic and want an AI client to run culling, style-matched editing and export for a shoot. It suits photographers who want batch culling and consistent personal-style edits driven by conversation rather than manual clicking.
- Requirements
- The imagic desktop app for Windows or macOS, launched once and activated with a trial or license; the MCP server reuses that activation. The client is pointed at the installed imagic binary with the --mcp argument as a local stdio server. MCP and headless automation are part of the paid imagic Max tier, though the free trial includes full Max access for 500 exports.
Installation
In SourceWeft
- Open Imagic in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"imagic": {
"type": "http",
"url": "https://mcp.imagic.ink/mcp"
}
}
}README
imagic MCP server
The first photo editor with a built-in MCP server.
imagic is a desktop photo editor for Windows and macOS with AI culling, a full non-destructive editor, and style learning. Its MCP (Model Context Protocol) server is built into the app, so Claude Code, Claude Desktop, Cursor, Codex, GitHub Copilot, or any other MCP client can drive the whole pipeline: scan a shoot, cull it, edit it in your style, and export the keepers. Everything runs locally on your machine.
This repository is the documentation and setup reference for that server. The server itself ships inside the imagic desktop app; there is no separate server source here.
- Full guide: imagic.ink/mcp
- Scripting without an AI client: imagic.ink/automation
- Download: imagic.ink/desktop
What an agent can do with it
Once connected, the agent calls the same actions you would trigger by hand in the app. Things you can actually say:
- "Scan D:/Shoots/june-wedding, cull it, and tell me what you kept and why."
- "Make the keepers warmer and export them to D:/delivery."
- "Run my film preset over the golden hour frames."
- "Edit the whole shoot like I would." (after style calibration)
- "I edited five from this wedding, match the rest to them."
- "Actually, just keep the best 60 for the client gallery." (instant re-rank, no re-analysis)
- "Export the keepers as full-res JPEGs."
Edits land as non-destructive adjustments in imagic's edit history, the same as manual edits. Nothing overwrites your originals unless you explicitly export.
Install
- Download imagic from imagic.ink/desktop. The free trial covers 500 exports with everything in imagic Max, no card required (importing, culling and editing never count against it).
- Launch the app once and activate (trial or license). The MCP server reuses that activation.
- Connect your MCP client (below).
The server is the imagic app itself, started with --mcp. There is no pip package and no separate imagic-mcp command in the packaged app; point your client at the installed binary:
- Windows:
C:\Program Files\imagic\imagic.exe - macOS:
/Applications/imagic.app/Contents/MacOS/imagic
Per-client setup for fourteen clients (config file locations, the right config key for each) is at imagic.ink/mcp/setup.
Claude Code
On macOS:
Claude Desktop, Cursor and other JSON-config clients
Add this to the client's MCP config (claude_desktop_config.json for Claude Desktop):
On macOS use "command": "/Applications/imagic.app/Contents/MacOS/imagic" with the same "args": ["--mcp"].
Codex CLI
Or in ~/.codex/config.toml:
GitHub Copilot and any other MCP-compatible client work the same way: a local stdio server whose command is the imagic binary with --mcp.
The 21 tools
Style learning: start with 8, train it on everything
imagic's style tools are what make agent-driven editing personal rather than generic:
- A guided start, 8 photos.
start_style_calibrationpulls up to 8 scenario photos from your own library, covering a spread of light and subjects. Edit them your way in imagic,record_style_calibrationsaves each decision, and you have a first profile in minutes. - It reads your real decisions. The actual exposure, color, and crop values you set in imagic, recorded per scenario and turned into a profile that is yours alone. Inspect it any time with
get_style_profile. - Then train it on everything. Repeat sessions whenever your taste shifts, or point
learn_style_from_libraryat your back catalog: every photo you have ever edited in imagic feeds the profile.apply_my_stylethen edits any future shoot the way you would have.
Within a single shoot there is also edit-five-match-the-rest: hand-edit a few frames, then match_style_from_examples matches the remaining photos to that look without changing your saved profile.
The honest boundary: it learns from edits made in imagic, reading the actual adjustment values you set. It cannot guess your style from exported JPEGs or a Lightroom catalog.
Privacy
The MCP server runs locally beside imagic and talks to your AI client over your own machine. The agent sends tool calls and instructions; your photos are never uploaded anywhere. All scanning, scoring, editing, and exporting happens on your hardware, the same as using imagic directly.
Licensing
The MCP server and headless CLI are part of imagic Max (EUR 99, one-time, no subscription). imagic's paid tiers start at EUR 19; Lite and Plus run the full GUI but do not unlock headless or MCP automation. The free trial includes full Max access for 500 exports, MCP and CLI included, with no card required.
Headless and MCP use need an activated desktop license: launch the GUI once, activate with your trial or license key, and the MCP server reuses that activation.
Links
- imagic.ink/mcp: full MCP and CLI guide, per-client setup, FAQ
- imagic.ink/automation: all three automation routes (in-app batch tools, headless CLI, MCP)
- imagic.ink/desktop: download and free trial
imagic is a closed-source commercial application. This documentation is (c) imagic. You are welcome to reference and link to it, including in MCP directories and registries.
Source: README.md at commit ec09fee
Tools
0Version history
1- v1.4.4LatestOct 2, 2026

