impeccable
The design vocabulary for your coding agent. Steer with polish and bolder, review with critique and audit, catch AI slop before it ships.
Let an AI agent cull, develop, mask and export photos in Lightroom Classic, render-checked
Skills that teach the AI this kind of work; they work alongside this one
The design vocabulary for your coding agent. Steer with polish and bolder, review with critique and audit, catch AI slop before it ships.
Editorial diagram design for Claude Code, Codex, GitHub Copilot, Cursor, Factory Droid, Qoder, and Pi. 45 diagram types. Self-contained HTML + SVG. No shadows. No Mermaid slop.
Create beautiful slides on the web using a coding agent's frontend skills
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 12/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Lightroom Agent. Follow https://mcp.popnx.com/i/fadeddexofan-lightroom-agent.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 20, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Lightroom Agent for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "lightroom-agent": { "command": "npx", "args": [ "-y", "lightroom-agent" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Lightroom Agent tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
SettingsDeveloperEdit Config
{
"mcpServers": {
"lightroom-agent": {
"command": "npx",
"args": [
"-y",
"lightroom-agent"
]
}
}
}Use Lightroom Agent and tell me what you can do for me, then show me one thing✓ If Claude says it is using Lightroom Agent or shows a Lightroom Agent tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
LIGHTROOM_AGENT_REQUEST_PORT Lightroom plugin request socket port. · default 58763LIGHTROOM_AGENT_RESPONSE_PORT Lightroom plugin response socket port. · default 58764LIGHTROOM_AGENT_TOOLSETS Toolsets to enable: core is always on; add develop, masks, develop,masks, or all. · default allLIGHTROOM_AGENT_READ_ONLY List and accept only read tools from the enabled toolsets. · default falseDescriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Lightroom Agent yet
Lightroom Agent runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Lightroom Agent
B · Others in Design, images & audio that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Lightroom Agent for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user lightroom-agent -- npx -y lightroom-agent 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Lightroom Agent tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user lightroom-agent -- npx -y lightroom-agentYou should see Lightroom Agent listed as connected
Use Lightroom Agent and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Lightroom Agent or shows a Lightroom Agent tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
LIGHTROOM_AGENT_REQUEST_PORT Lightroom plugin request socket port. · default 58763LIGHTROOM_AGENT_RESPONSE_PORT Lightroom plugin response socket port. · default 58764LIGHTROOM_AGENT_TOOLSETS Toolsets to enable: core is always on; add develop, masks, develop,masks, or all. · default allLIGHTROOM_AGENT_READ_ONLY List and accept only read tools from the enabled toolsets. · default falseDescriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Lightroom Agent for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "lightroom-agent": { "command": "npx", "args": [ "-y", "lightroom-agent" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Lightroom Agent tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use Lightroom Agent and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Lightroom Agent or shows a Lightroom Agent tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
LIGHTROOM_AGENT_REQUEST_PORT Lightroom plugin request socket port. · default 58763LIGHTROOM_AGENT_RESPONSE_PORT Lightroom plugin response socket port. · default 58764LIGHTROOM_AGENT_TOOLSETS Toolsets to enable: core is always on; add develop, masks, develop,masks, or all. · default allLIGHTROOM_AGENT_READ_ONLY List and accept only read tools from the enabled toolsets. · default falseDescriptions are as written by the maker.
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Lightroom Agent for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "lightroom-agent": { "type": "stdio", "command": "npx", "args": [ "-y", "lightroom-agent" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Lightroom Agent tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use Lightroom Agent and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Lightroom Agent or shows a Lightroom Agent tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
LIGHTROOM_AGENT_REQUEST_PORT Lightroom plugin request socket port. · default 58763LIGHTROOM_AGENT_RESPONSE_PORT Lightroom plugin response socket port. · default 58764LIGHTROOM_AGENT_TOOLSETS Toolsets to enable: core is always on; add develop, masks, develop,masks, or all. · default allLIGHTROOM_AGENT_READ_ONLY List and accept only read tools from the enabled toolsets. · default falseDescriptions are as written by the maker.
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Claude Code
claude mcp add --scope user lightroom-agent -- npx -y lightroom-agentClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"lightroom-agent": {
"command": "npx",
"args": [
"-y",
"lightroom-agent"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"lightroom-agent": {
"command": "npx",
"args": [
"-y",
"lightroom-agent"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"lightroom-agent": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"lightroom-agent"
]
}
}
}LIGHTROOM_AGENT_REQUEST_PORT envLIGHTROOM_AGENT_RESPONSE_PORT envLIGHTROOM_AGENT_TOOLSETS envLIGHTROOM_AGENT_READ_ONLY envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 20, 2026
The registry name was verified with the GitHub account fadedDexofan, which owns the repo
Code last changed 2 days ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Not checked yet
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/fadeddexofan-lightroom-agent)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 2 days ago, and the latest version (0.1.0-rc.4) reached the registry today.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: HyperFrames by HeyGen, Pascal 3D Editor, draw.io, Figma MCP Server, Remocn: Remotion MCP server
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Official HyperFrames by HeyGen: the best AI video editor in chat. Captions, motion graphics, MP4.
Create, inspect, validate, and save editable 3D building scenes with Pascal's MCP server.
Create draw.io diagrams in chat from Mermaid or XML, shown live and interactive. 10,000+ shapes.
Figma’s official server gives AI your design data so it can turn designs into code or describe them accurately. Connects to Figma’s cloud.
Hosted MCP for Remotion videos: search Remocn components, read docs, plan a video, preview it.
| This one Lightroom Agent | HyperFrames by HeyGen | Pascal 3D Editor | draw.io | Figma MCP Server | Remocn: Remotion MCP server | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Cloud or install on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | Yes | No | No | Yes | No |
| Basic checks | 3/3 | 4/4 | 5/5 | 4/4 | 4/4 | 4/4 |
| License | MIT | Apache-2.0 | MIT | Apache-2.0 | – | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
lightroom-agent
Let an AI agent cull, develop, mask and export your photos in Adobe Lightroom Classic, and check every change on Lightroom's own render.
lightroom-agent is an MCP server and a Lightroom Classic plug-in. Claude Code, Codex or any other MCP client gets tools for the catalog, Develop, masks and export, and a bundled skill that teaches the agent to cull and edit with them.
Things to ask for:
| lightroom-mcp | lightroom-agent | |
|---|---|---|
| Result of a call | Plain errors; a failed write looks like one whose result is unknown | One envelope: done, partial, failed, unknown, decided by what was written; failed means nothing changed |
| Mask edits | Sliders, curves and deletions act on the mask selected in Develop, which a click can change mid-call | By mask id in the photo's saved settings, read back after the write (invert_mask still works in Develop) |
| Mask construction on a new Lightroom build | Allowed for a list of versions in the source | Allowed once the live test suite has passed on this machine for that build |
| Agent guidance | A preset-building workflow: culling, closed-loop edits, lighting-cluster presets, XMP fallback | A skill for culling, developing, masking and exporting with these tools, with technical and editorial gates |
The decisions behind the first three rows are in docs/adr. A live test kit builds a throwaway catalog from fixed images and checks the tools against Lightroom's renders.
LIGHTROOM_AGENT_READ_ONLY=true, or let the agent work on snapshots and virtual copies, which the bundled skill does by default.You need Lightroom Classic 15.0 or later on macOS (checked live on 15.6 and 16.0; 15.0–15.5 and Windows are untested) and Node.js 20 or later. Install lightroom-agent in each agent you use; every route ends with the same Lightroom step.
/plugin marketplace add fadedDexofan/lightroom-agent
/plugin install lightroom-agent@lightroom-agent
The plugin brings the server with every toolset and the bundled skill. To update, run claude plugin marketplace update lightroom-agent, then claude plugin update lightroom-agent@lightroom-agent; to uninstall, claude plugin uninstall lightroom-agent@lightroom-agent.
Codex
codex plugin marketplace add fadedDexofan/lightroom-agent
codex plugin add lightroom-agent@lightroom-agent
The plugin brings the server and the skill, as in Claude Code. In codex exec, Codex does not yet offer the plugin's tools to the model. To update, run codex plugin marketplace upgrade lightroom-agent and add the plugin again; to uninstall, codex plugin remove lightroom-agent@lightroom-agent.
Claude Desktop
Download lightroom-agent- .mcpb from the latest release and open it; Claude Desktop installs it as an extension. Its settings set the toolsets and read-only mode. To update, open the newer release's .mcpb; to uninstall, remove the extension in Claude Desktop's settings.
Any other MCP client
Run the npm package over stdio, pinned to the latest release's version:
{
"mcpServers": { "lightroom": { "command": "npx", "args": ["-y", "lightroom-agent@ "], "env": { "LIGHTROOM_AGENT_TOOLSETS": "all" } } } }
all adds the Develop and mask tools to the default core set. Keep the version pinned: the server refuses to work with a plug-in of another build, so every client should run the same one. To update, change the version in every client. The server offers the skill as the MCP prompt lightroom-agent.
From source
git clone https://github.com/fadedDexofan/lightroom-agent.git
cd lightroom-agent npm --prefix server ci npm --prefix server run build
claude mcp add lightroom -e LIGHTROOM_AGENT_TOOLSETS=all -- node "$PWD/server/dist/index.js"
codex mcp add lightroom --env LIGHTROOM_AGENT_TOOLSETS=all -- node "$PWD/server/dist/index.js"
To update, pull and rebuild. CONTRIBUTING.md covers working on the code.
The server that holds the Lightroom connection installs the plug-in when it starts. Then quit and reopen Lightroom Classic and bring its window to the front: the plug-in starts its server. If File → Plug-in Manager shows Lightroom Agent stopped, click Start Server.
Ask your agent: *List my Lightroom collections.* It answers with your collections by name.
After any update, restart all your clients first, then Lightroom: every server refuses tool calls, naming both builds, until Lightroom has loaded the new plug-in.
Installing the plug-in by hand, and uninstalling
node server/dist/index.js install-plugin (or npx -y lightroom-agent@ install-plugin) copies the plug-in over its existing copy in Lightroom's Modules or Plugins folder, otherwise into the Modules folder (~/Library/Application Support/Adobe/Lightroom/Modules/ on macOS, %APPDATA%\Adobe\Lightroom\Modules\ on Windows). It replaces an installed copy whose files differ from its build and leaves an identical one alone. It refuses while a running lightroom-agent server on the same ports owns the plug-in, so quit your clients first; with custom ports, run it with the same port variables and quit clients on any other ports too, since every port pair installs into the same folder. If a LightroomMCP.lrplugin is installed, it refuses, because both use the same ports: quit Lightroom and delete that folder first.
To uninstall, remove the agent's plugin or server entry, then delete the installed LightroomAgent.lrplugin folder (Plug-in Manager shows where it is) and ~/.config/lightroom-agent.
skills/lightroom-agent teaches an agent how to work with these tools on photographs. It culls in two passes (technical, then editorial), develops one representative frame per lighting situation before copying to the rest, inspects mask edges, and checks each exported file.
The Claude Code and Codex plugins load it, and the server offers it to any client as the MCP prompt lightroom-agent. To install it by hand, copy or symlink the folder into ~/.claude/skills/ for Claude Code or ~/.codex/skills/ for Codex; agents/openai.yaml carries Codex's metadata. The skill describes the tools of the server it ships with, so replace a copied folder whenever you update the server.
The server reads LIGHTROOM_AGENT_TOOLSETS, LIGHTROOM_AGENT_READ_ONLY, the two port variables and LIGHTROOM_AGENT_TOKEN_PATH when it starts. docs/reference.md lists them with their defaults, and covers the toolsets, read-only mode, the command line and mask certification.
Starting the plug-in's server writes a random token to ~/.config/lightroom-agent/token. The MCP server sends it with every request, and the plug-in listens on localhost only, so the remaining risk is another user or process on the same machine. Lightroom's plug-in sandbox cannot set file permissions; on a shared machine run chmod 700 ~/.config/lightroom-agent. To report a vulnerability, see SECURITY.md.
The server writes its diagnostics to stderr, which MCP clients keep in their server log. Plug-in Manager → Show Status shows both sockets, the last event, the number of requests processed and the path of the plug-in log (`~/Documents/LrClassicLogs/Lightroo