Glif vs io.github.editmamei/editmamei-photoshop-mcp
Glif is an MCP server published by glif.app. Marketplaces we read that list it: 3 (Official MCP Registry, Docker MCP Catalog, Community GitHub marketplaces). io.github.editmamei/editmamei-photoshop-mcp is an MCP server published by editmamei. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-05. 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 |   Glif |  io.github.editmamei/editmamei-photoshop-mcp |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.1 Forks (GitHub): 32 Stars (GitHub): 218 Not marked · First seen |
Listed Version: 1.9.6 Downloads/month (npm): 1 864 Downloads/week (npm): 750 Forks (GitHub): 4 Stars (GitHub): 16 Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:3f93ddceeb99 Forks (GitHub): 32 Pulls (Docker Hub): 20 101 Stars (Docker Hub): 2 Stars (GitHub): 218 Not marked · First seen |
Not listed |
| npm registry (MCP servers) | Not listed | Listed Version: 1.9.6 Downloads/month (npm): 1 864 Downloads/week (npm): 750 Forks (GitHub): 4 Stars (GitHub): 16 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 | Glif | io.github.editmamei/editmamei-photoshop-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 3 (better) | 2 (worse) |
| Stars (GitHub) (differs) | 218 (better) | 16 (worse) |
| Pulls (Docker Hub) (differs) | 20 101 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 32 (better) | 4 (worse) |
| Last release (differs) | Not published | 2026-11-04 |
| Where it runs (differs) | Remote server or your machine | On your machine (editmamei) |
| Transport (differs) | Streamable HTTP, stdio | stdio |
| Tools it declares (differs) | 10 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 1 | Not published |
| Parts of the bundle (differs) | 11 | Not a bundle |
| Licence (differs) | MIT | FSL-1.1-MIT |
| Repository (differs) | github.com/glifxyz/glif-mcp-server | github.com/editmamei/editmamei |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Status out of date: last check 5 days ago returned HTTP 405 | no 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
Glif
Generate images, video, and audio with Glif's media-generation agent
io.github.editmamei/editmamei-photoshop-mcp
Photoshop MCP server: natural-language AI photo editing in desktop Photoshop. AI orchestration.
How to run each
Glif As a remote MCP server
claude mcp add --transport http glif https://glif.app/api/mcpio.github.editmamei/editmamei-photoshop-mcp As a local MCP server: npm package
claude mcp add --transport stdio editmamei-photoshop-mcp -- npx -y editmameiCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Glif has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of io.github.editmamei/editmamei-photoshop-mcp publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of io.github.editmamei/editmamei-photoshop-mcp publish no settings it asks for, so we do not compare settings.
What it can do: Glif · What it can do: io.github.editmamei/editmamei-photoshop-mcp · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.