Ext Ops Panel
Open dashboard
Comparison

imagesorcery-mcp vs io.github.JimothySnicket/gemini-image

imagesorcery-mcp is an MCP server published by sunriseapps. Marketplaces we read that list it: 1 (PyPI (MCP servers)). io.github.JimothySnicket/gemini-image is an MCP server published by JimothySnicket. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (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

Where each is published
Marketplaceimagesorcery-mcpio.github.JimothySnicket/gemini-image
PyPI (MCP servers) Listed
Version: 0.12.0
Downloads/month (PyPI): 542
Downloads/week (PyPI): 166
Forks (GitHub): 53
Stars (GitHub): 337
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.6.2
Downloads/month (npm): 1 102
Downloads/week (npm): 340
Forks (GitHub): 1
Stars (GitHub): 2
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.6.2
Downloads/month (npm): 1 102
Downloads/week (npm): 340
Forks (GitHub): 1
Stars (GitHub): 2
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

imagesorcery-mcp vs io.github.JimothySnicket/gemini-image
Factimagesorcery-mcpio.github.JimothySnicket/gemini-image
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)337 (better)2 (worse)
Forks (GitHub) (differs)53 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (imagesorcery-mcp)On your machine (@jimothy-snicket/gemini-image-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
LicenceMITMIT
Repository (differs)github.com/sunriseapps/imagesorcery-mcpgithub.com/jimothysnicket/gemini-image-mcp
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11

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

imagesorcery-mcp

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

A Model Context Protocol server providing image manipulation tools for LLMs

io.github.JimothySnicket/gemini-image

In its own words, on Official MCP Registry:

Google Gemini image generation, editing, and local processing via MCP

How to run each

imagesorcery-mcp

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

io.github.JimothySnicket/gemini-image As a local MCP server: npm package

Claude Code
claude mcp add --env "GEMINI_API_KEY=<YOUR_GEMINI_API_KEY>" --transport stdio gemini-image -- npx -y @jimothy-snicket/gemini-image-mcp

Requires: GEMINI_API_KEY (secret)

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

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

What it can do: imagesorcery-mcp · What it can do: io.github.JimothySnicket/gemini-image · Compare two other plugins

Package data comes from the Python Package Index (pypi.org). 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