@mskalski/lightroom-mcp vs io.github.AceDataCloud/mcp-luma
@mskalski/lightroom-mcp is an MCP server published by @mskalski. Marketplaces we read that list it: 1 (npm registry (MCP servers)). io.github.AceDataCloud/mcp-luma is an MCP server published by AceDataCloud. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-11-09. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.AceDataCloud/mcp-luma | |
|---|---|---|
| npm registry (MCP servers) | Listed Version: 0.27.0 Downloads/month (npm): 7 395 Downloads/week (npm): 2 360 Forks (GitHub): 41 Stars (GitHub): 189 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2026.11.1.0 Downloads/month (PyPI): 5 202 Downloads/week (PyPI): 272 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 2026.11.1.0 Downloads/month (PyPI): 5 202 Downloads/week (PyPI): 272 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | @mskalski/lightroom-mcp | io.github.AceDataCloud/mcp-luma |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 189 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 41 (better) | 0 (worse) |
| Last release (differs) | 2026-11-05 (better) | 2026-11-01 (worse) |
| Where it runs (differs) | On your machine (@mskalski/lightroom-mcp) | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/automaat/lightroom-mcp | github.com/acedatacloud/lumamcp |
| Changes in the last 7 days (differs) | 1 | 0 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | No HTTP response at the last check (less than an hour ago) |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
@mskalski/lightroom-mcp
MCP server bridging Claude/Codex/ChatGPT to Adobe Lightroom Classic via a Lua plugin.
io.github.AceDataCloud/mcp-luma
MCP server for Luma Dream Machine AI video generation
How to run each
@mskalski/lightroom-mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.AceDataCloud/mcp-luma As a remote MCP server
claude mcp add --transport http mcp-luma https://luma.mcp.acedata.cloud/mcpRequires: ACEDATACLOUD_API_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.AceDataCloud/mcp-luma has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of @mskalski/lightroom-mcp publish no settings it asks for, so we do not compare settings.
What it can do: @mskalski/lightroom-mcp · What it can do: io.github.AceDataCloud/mcp-luma · Compare two other plugins
Package data comes from the public npm registry (registry.npmjs.org). Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.