Ext Ops Panel
Open dashboard
Comparison

Pref Editor vs Framegrove: App Store screenshot generator

Pref Editor is an MCP server published by charlesmuchene. Marketplaces we read that list it: 1 (Docker MCP Catalog). Framegrove: App Store screenshot generator is an MCP server published by tech-bam. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-15. 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
MarketplacePref EditorFramegrove: App Store screenshot generator
Docker MCP Catalog Listed
Version: sha256:9a25e5de0f1f
Forks (GitHub): 3
Pulls (Docker Hub): 33 643
Stars (Docker Hub): 0
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Downloads/month (npm): 48
Downloads/week (npm): 48
Forks (GitHub): 0
Stars (GitHub): 1
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

Pref Editor vs Framegrove: App Store screenshot generator
FactPref EditorFramegrove: App Store screenshot generator
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)2 (better)1 (worse)
Pulls (Docker Hub) (differs)33 643No figure on Docker Hub
Forks (GitHub) (differs)3 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/pref-editor)On your machine (framegrove)
Transportstdiostdio
Tools it declares (differs)7Not published
Environment variables it asks for (differs)Not published2, secrets among them: 0
Parts of the bundle (differs)Not a bundle2
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/charlesmuchene/pref-editor-mcp-servergithub.com/tech-bam/framegrove
Changes in the last 7 days (differs)02
First seen2026-10-112026-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

Pref Editor

In its own words, on Docker MCP Catalog:

Pref Editor is a tool for viewing and editing Android app preferences during development.

Framegrove: App Store screenshot generator

In its own words, on Official MCP Registry:

Render App Store, Google Play and iPhone Duo screenshots and Apple Creative Assets from templates.

How to run each

Pref Editor As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio pref-editor -- docker run -i --rm mcp/pref-editor

Framegrove: App Store screenshot generator As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio framegrove -- npx -y framegrove mcp

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

Tools each declares

The marketplaces of Framegrove: App Store screenshot generator publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: Pref Editor · What it can do: Framegrove: App Store screenshot generator · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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