Ext Ops Panel
Open dashboard
Comparison

Open Screenshot Generator vs Framegrove: App Store screenshot generator

Open Screenshot Generator is a plugin bundle for AI coding tools published by Idrees Khan. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Framegrove: App Store screenshot generator is an MCP server published by tech-bam. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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
MarketplaceOpen Screenshot GeneratorFramegrove: App Store screenshot generator
Community marketplace dotnetdreamer/open-screenshot-generator Listed
Version: 0.1.34
Forks (GitHub): 14
Stars (GitHub): 134
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Downloads/month (npm): 65
Downloads/week (npm): 17
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

Open Screenshot Generator vs Framegrove: App Store screenshot generator
FactOpen Screenshot GeneratorFramegrove: App Store screenshot generator
Marketplaces that list it11
Stars (GitHub) (differs)134 (better)1 (worse)
Forks (GitHub) (differs)14 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (open-screenshot-generator)On your machine (framegrove)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 0
Parts of the bundle (differs)6Not a bundle
LicenceMITMIT
Repository (differs)github.com/dotnetdreamer/open-screenshot-generatorgithub.com/tech-bam/framegrove
Changes in the last 7 days (differs)24
First seen (differs)2026-10-162026-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

Open Screenshot Generator

In its own words, on Community GitHub marketplaces:

Turn app screenshots into finished App Store and Play Store sets: 101 templates, per device and per locale renders, MP4 previews, store rule checks, and 49 design tools over MCP.

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

Open Screenshot Generator As a Claude Code plugin

Claude Code
/plugin marketplace add dotnetdreamer/open-screenshot-generator
/plugin install open-screenshot-generator@open-screenshot-generator

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

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of Open Screenshot Generator publish no settings it asks for, so we do not compare settings.

What it can do: Open Screenshot Generator · What it can do: Framegrove: App Store screenshot generator · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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