Ext Ops Panel
Open dashboard
Comparison

EverArt (Archived) vs Claude Imagine

EverArt (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). Claude Imagine is a plugin bundle for AI coding tools published by Claude Imagine. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-17. 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
MarketplaceEverArt (Archived)Claude Imagine
Docker MCP Catalog Listed
Version: sha256:98c2aa1b6231
Forks (GitHub): 11 793
Pulls (Docker Hub): 18 819
Stars (Docker Hub): 3
Stars (GitHub): 91 324
Not marked · First seen
Not listed
Community marketplace davepoon/buildwithclaude Not listed Listed
Version: 1.0.0
Forks (GitHub): 617
Stars (GitHub): 3 645
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

EverArt (Archived) vs Claude Imagine
FactEverArt (Archived)Claude Imagine
Marketplaces that list it11
Stars (GitHub) (differs)91 324 (better)3 645 (worse)
Pulls (Docker Hub) (differs)18 819No figure on Docker Hub
Forks (GitHub) (differs)11 793 (better)617 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/everart)Remote server (claudeimagine.com/api/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)1Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Parts of the bundle (differs)Not a bundle1
Licence (differs)NOASSERTIONMIT
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/davepoon/buildwithclaude
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-15
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 days ago, requires a key

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

EverArt (Archived)

In its own words, on Docker MCP Catalog:

Image generation server using EverArt's API.

Claude Imagine

In its own words, on Community GitHub marketplaces:

Generate and edit AI images and videos from inside Claude Code through one remote MCP server. Nano Banana 2, GPT Image 2.5, Seedream 4.5, Flux 2 Pro and Z-Image for stills; Veo, Kling, Seedance, Grok Imagine and MiniMax for clips. quote_generation prices any call before you spend, and failed generations are refunded automatically. OAuth via /mcp; no API key to paste.

How to run each

EverArt (Archived) As a local MCP server: Docker image

Claude Code
claude mcp add --env "EVERART_API_KEY=<YOUR_EVERART_API_KEY>" --transport stdio everart -- docker run -i --rm -e EVERART_API_KEY mcp/everart

Requires: EVERART_API_KEY (secret)

Claude Imagine As a Claude Code plugin

Claude Code
/plugin marketplace add davepoon/buildwithclaude
/plugin install claude-imagine@buildwithclaude

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

Only Claude Imagine has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Claude Imagine publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Claude Imagine publish no settings it asks for, so we do not compare settings.

What it can do: EverArt (Archived) · What it can do: Claude Imagine · Compare two other plugins

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. 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