Ext Ops Panel
Open dashboard
Comparison

Pref Editor vs Google Play Reviews (reviews, installs, charts)

Pref Editor is an MCP server published by charlesmuchene. Marketplaces we read that list it: 1 (Docker MCP Catalog). Google Play Reviews (reviews, installs, charts) is an MCP server published by akhilrajesh213. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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 EditorGoogle Play Reviews (reviews, installs, charts)
Docker MCP Catalog Listed
Version: sha256:9a25e5de0f1f
Forks (GitHub): 3
Pulls (Docker Hub): 34 268
Stars (Docker Hub): 0
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.21
No figure published
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 Google Play Reviews (reviews, installs, charts)
FactPref EditorGoogle Play Reviews (reviews, installs, charts)
Marketplaces that list it11
Stars (GitHub) (differs)2No figure on GitHub
Pulls (Docker Hub) (differs)34 268No figure on Docker Hub
Forks (GitHub) (differs)3No figure on GitHub
Last release (differs)Not published2026-11-03
Where it runs (differs)On your machine (mcp/pref-editor)Remote server (akhil-rajesh--google-play-reviews-scraper.apify.actor/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)7Not published
Environment variables it asks forNot publishedNot published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/charlesmuchene/pref-editor-mcp-serverNot stated
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-20
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 40 h ago returned HTTP 401

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.

Google Play Reviews (reviews, installs, charts)

In its own words, on Official MCP Registry:

Google Play reviews for AI agents: reviews by language, app details, keyword ranks, top charts.

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

Google Play Reviews (reviews, installs, charts) As a remote MCP server

Claude Code
claude mcp add --transport http google-play-reviews https://akhil-rajesh--google-play-reviews-scraper.apify.actor/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Only Google Play Reviews (reviews, installs, charts) has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Google Play Reviews (reviews, installs, charts) publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: Pref Editor · What it can do: Google Play Reviews (reviews, installs, charts) · 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. 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