Lets Claude (and other AI assistants) talk to your Adobe Lightroom Classic photo catalog. Search photos, set ratings, edit develop settings, manage collections, import/export — all by chatting.
Works with: Claude Desktop, Claude Code, Codex CLI, Cursor, Windsurf, VS Code. Needs: Lightroom Classic on macOS or Windows. Nothing else — no programming required.
This is the recommended path. Takes ~2 minutes, no terminal needed.
Go to the latest release page and download the file ending in .mcpb (it's near the top, called lightroom-mcp-<version>.mcpb).
Claude Desktop opens automatically and asks: "Install Lightroom Classic extension?". Click Install.
Don't have Claude Desktop yet? Get it free from claude.com/download. It runs on Mac and Windows.
- Quit and reopen Lightroom Classic. (The plugin needs a restart to show up.)
- In Lightroom, click File in the menu bar → Plug-in Manager.
- In the left list, click Lightroom MCP.
- On the right, click the Start Server button.
- You should see "Server running" appear. Done!
Open Claude Desktop and type:
List all my Lightroom collections.
Claude will list every collection in your catalog.
Some other things to try:
- "Find all my 5-star photos from last summer."
- "Add the keyword 'portfolio' to the photos I have selected in Lightroom."
- "Apply the 'Vivid' develop preset to these photos."
- "Export the selected photos to my Desktop as JPEGs at 2000px wide."
Already using Claude Code, Codex, Cursor, Windsurf, or VS Code? Pick your tool below. All paths still end with the Lightroom step from the section above — restart Lightroom and click Start Server in Plug-in Manager.
Claude Code
Same .mcpb file as Claude Desktop above — Claude Code accepts it too. Or install via the CLI:
claude mcp add lightroom -- npx -y @mskalski/lightroom-mcpCodex CLI
codex mcp add lightroom -- npx -y @mskalski/lightroom-mcpThe Lightroom plugin installs itself the first time Codex talks to the server.
Cursor / Windsurf / VS Code (Continue, Cline, Roo, ...)
Open your client's MCP settings and add:
{
"mcpServers": {
"lightroom": {
"command": "npx",
"args": ["-y", "@mskalski/lightroom-mcp"]
}
}
}The plugin installs itself the first time your client starts the server. If your client only starts the server on first tool call, you can install the plugin upfront:
npx -y @mskalski/lightroom-mcp install-pluginNo Node.js installed? Use the standalone binary
-
Download the right file from the latest release:
- Mac (Apple Silicon, M1/M2/M3/M4):
lightroom-mcp-darwin-arm64 - Mac (Intel):
lightroom-mcp-darwin-x64 - Windows:
lightroom-mcp-windows-x64.exe
- Mac (Apple Silicon, M1/M2/M3/M4):
-
macOS only — make it runnable and bypass Gatekeeper (the binary isn't signed):
chmod +x ~/Downloads/lightroom-mcp-darwin-arm64 xattr -d com.apple.quarantine ~/Downloads/lightroom-mcp-darwin-arm64
-
Install the Lightroom plugin:
~/Downloads/lightroom-mcp-darwin-arm64 install-plugin -
Point your AI tool at the binary's full path. Example for Codex:
codex mcp add lightroom -- /Users/you/Downloads/lightroom-mcp-darwin-arm64
Install the Lightroom plugin manually (any client)
If you'd rather drop the plugin in by hand:
- Download the matching zip from the latest release:
- Mac:
LightroomMCP-macos.lrplugin.zip - Windows:
LightroomMCP-windows.lrplugin.zip
- Mac:
- Unzip it. You get a folder called
LightroomMCP.lrplugin. - Move that folder into Lightroom's Modules folder:
- Mac:
~/Library/Application Support/Adobe/Lightroom/Modules/ - Windows:
%APPDATA%\Adobe\Lightroom\Modules\ - (If the
Modulesfolder doesn't exist, create it.)
- Mac:
- Restart Lightroom → Plug-in Manager → Start Server.
- Open Lightroom → File → Plug-in Manager → Lightroom MCP → Show Status. Both sockets should say
connected: true. If not, click Start Server. - Make sure you fully quit and reopened Lightroom after install (Cmd+Q on Mac, Alt+F4 on Windows). "Reload Plug-in" alone is not enough.
- See Troubleshooting below for specific errors.
| Tool | What it does |
|---|---|
search_photos |
Search by filename / keywords / rating / date range. |
get_selected_photos |
Photos selected in Lightroom (or filmstrip). |
get_photo_metadata |
EXIF, GPS, IPTC location, copyright + develop settings for one photo. |
list_collections |
All collections and collection sets. |
create_collection |
New collection (optional parent set). |
add_to_collection |
Add photos to a named collection. |
set_keywords |
Add or remove keywords on photos. |
set_rating |
Set 0-5 star rating on photos. |
import_photos |
Import a file or folder into the catalog. |
export_photos |
Export with format / quality / dimensions. |
list_develop_presets |
Discover available Develop presets. |
apply_develop_preset |
Apply a named preset to photos. |
copy_develop_settings |
Copy develop settings between photos. |
set_develop_settings |
Write SDK setting key/values directly. |
Full schemas and parameter docs: server/src/list-tools-handler.ts.
┌─────────────┐ stdio ┌──────────────────┐ TCP :58763 → ┌──────────────────┐
│ AI client │ ◄─────────► │ MCP server │ ──────────────► │ Lightroom plugin │
│ (Claude/ │ │ (Node TCP) │ ←────────────── │ (LrSocket) │
│ Codex/...) │ └──────────────────┘ ← TCP :58764 └──────────────────┘
└─────────────┘ │
▼
catalog:withReadAccessDo
Plugin binds two LrSocket servers on localhost (58763 request, 58764 response). Server connects as TCP client. Frame: line-delimited JSON, \n terminator. Auto-reconnect on both sides. Same dual-port pattern as MIDI2LR.
lightroom-mcp [stdio] Run MCP over stdio (default)
lightroom-mcp install-plugin Copy bundled plugin into Lightroom Modules folder
lightroom-mcp --help | --version
Env vars:
| Var | Default | Purpose |
|---|---|---|
LIGHTROOM_MCP_REQUEST_PORT |
58763 |
Plugin request port. |
LIGHTROOM_MCP_RESPONSE_PORT |
58764 |
Plugin response port. |
LIGHTROOM_MCP_TOKEN_PATH |
~/.config/lightroom-mcp/token |
Auth token file. |
If you change ports on the server side, change them in Plug-in Manager → Lightroom MCP to match.
The plugin generates a 256-bit token in ~/.config/lightroom-mcp/token on Start Server. The MCP server attaches it to every request. Localhost-only — no remote attack surface.
mise install # tools (node, bun, lua + luarocks, selene)
mise run install # npm ci
mise run build # tsc
mise run test # jest
mise run mcpb # build .mcpb bundle
mise run binary # build single-file binaries via Bun
mise run lua:lint # selene-lint the Lua plugin
mise run lua:test # busted specs for the Lua pluginRepo layout:
server/— TypeScript MCP server (ESM, NodeNext).plugin/LightroomMCP.lrplugin/— Lua plugin loaded by Lightroom Classic.mcpb/manifest.json—.mcpbbundle manifest.scripts/build-mcpb.mjs— pack the .mcpb.scripts/build-binary.mjs— Bun--compileper-target binaries.manual-test.mjs— direct TCP probe (bypasses MCP).
- Add a new
Handler*.luaunderplugin/LightroomMCP.lrplugin/. - Register it in the
DISPATCHtable inPluginInfoProvider.lua. - Add a contract entry in
server/src/tool-contracts.ts. - Declare any new LR globals in
lightroom.yml(selene std).
failed to open localhost:58763after Reload Plug-in — old async task still owns the port. Quit Lightroom (Cmd+Q on macOS / Alt+F4 on Windows) and reopen.- Plugin not connected — the server now self-restarts after a Reload Plug-in that tore down a running instance. If it's still stopped, click Start Server in Plug-in Manager; it reconnects within ~1s.
- Timeout errors — handler may be scanning a large catalog without filters; add
rating,filename,keywords, or date filters to narrow. - macOS "cannot be opened because the developer cannot be verified" (binary path) —
xattr -d com.apple.quarantine /path/to/binary. Or right-click → Open the first time. - Windows SmartScreen blocks the .exe — More info → Run anyway.
Logs:
| Component | macOS | Windows |
|---|---|---|
| Plugin | ~/Documents/LrClassicLogs/LightroomMCP.log |
%USERPROFILE%\Documents\LrClassicLogs\LightroomMCP.log |
| Claude Desktop | ~/Library/Logs/Claude/mcp*.log |
%APPDATA%\Claude\Logs\mcp*.log |
The plugin resolves its log path via the OS (LrPathUtils), so on Windows with
OneDrive-redirected Documents the file follows the redirect. The exact resolved
path is shown as Log file: in Plug-in Manager → Show Status — use that if
the table path above is empty.
MIT