Ext Ops Panel
Open dashboard
Comparison

MyBestAngle vs io.github.editmamei/editmamei-photoshop-mcp

MyBestAngle is an MCP server published by mybestangle.com. Marketplaces we read that list it: 1 (Official MCP Registry). 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-12. 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
MarketplaceMyBestAngleio.github.editmamei/editmamei-photoshop-mcp
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 1.10.2
Downloads/month (npm): 1 864
Downloads/week (npm): 750
Forks (GitHub): 4
Stars (GitHub): 18
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 1.10.2
Downloads/month (npm): 1 864
Downloads/week (npm): 750
Forks (GitHub): 4
Stars (GitHub): 18
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

MyBestAngle vs io.github.editmamei/editmamei-photoshop-mcp
FactMyBestAngleio.github.editmamei/editmamei-photoshop-mcp
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub18
Forks (GitHub) (differs)No figure on GitHub4
Last release (differs)Not published2026-11-12
Where it runs (differs)Remote server (mcp.mybestangle.com/mcp)On your machine (editmamei)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)Not statedFSL-1.1-MIT
Repository (differs)Not statedgithub.com/editmamei/editmamei
Changes in the last 7 days (differs)07
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 12 h ago, requires authenticationno 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

MyBestAngle

In its own words, on Official MCP Registry:

Professional profile photos and headshots from your own selfies.

io.github.editmamei/editmamei-photoshop-mcp

In its own words, on Official MCP Registry:

Photoshop and GIMP MCP server for AI photo editing, layer by layer with real tools

How to run each

MyBestAngle As a remote MCP server

Claude Code
claude mcp add --transport http mybestangle https://mcp.mybestangle.com/mcp

io.github.editmamei/editmamei-photoshop-mcp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio editmamei-photoshop-mcp -- npx -y editmamei

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

Only MyBestAngle 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

Neither one's marketplaces publish the settings it asks for.

What it can do: MyBestAngle · 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. 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.

Where the data comes from: how the catalog is built