Ext Ops Panel
Open dashboard
Comparison

Rube vs photoshop-mcp-server

Rube is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). photoshop-mcp-server is an MCP server published by loonghao. Marketplaces we read that list it: 1 (PyPI (MCP servers)). As of our marketplace pass on 2026-11-08. 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

Where each is published
MarketplaceRubephotoshop-mcp-server
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
PyPI (MCP servers) Not listed Listed
Version: 0.1.14
Downloads/month (PyPI): 1 522
Downloads/week (PyPI): 596
Forks (GitHub): 31
Stars (GitHub): 349
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

Rube vs photoshop-mcp-server
FactRubephotoshop-mcp-server
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub349
Forks (GitHub) (differs)No figure on GitHub31
Last release (differs)Not published2026-10-14
Where it runs (differs)Remote server (rube.app/mcp)On your machine (photoshop-mcp-server)
Transport (differs)Streamable HTTPNot stated
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)Apache-2.0MIT
Repository (differs)Not statedgithub.com/loonghao/photoshop-python-api-mcp-server
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-13
Endpoint at the last check (differs)Status out of date: no HTTP response at the last check 38 h agono remote endpoint we check

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

Rube

In its own words, on Docker MCP Catalog:

Access to Rube's catalog of remote MCP servers.

photoshop-mcp-server

In its own words, on PyPI (MCP servers):

MCP Server for Photoshop integration using photoshop-python-api

How to run each

Rube As a remote MCP server

Claude Code
claude mcp add --transport http rube https://rube.app/mcp

Requires: RUBE_API_KEY (secret)

photoshop-mcp-server

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Rube 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 photoshop-mcp-server publish no settings it asks for, so we do not compare settings.

What it can do: Rube · What it can do: photoshop-mcp-server · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.

Where the data comes from: how the catalog is built