Ermöglicht KI-Agenten den schreibgeschützten Zugriff auf öffentliche Google Play Store Daten, einschließlich App-Details, Suchergebnissen, Rezensionen und Entwicklerinformationen.
Auch bekannt als kryuchenko/google-play-scraper, gpscrape
- Stars
- 0
- Tools
- 21
- Downloads, 30 Tage
- —
- Neueste Version
- 0.1.2
- Letzter Commit
- 14. Nov. 2026
- Lizenz
- MIT
Was ist Google Play Store MCP?
Ermöglicht KI-Agenten den schreibgeschützten Zugriff auf öffentliche Google Play Store Daten, einschließlich App-Details, Suchergebnissen, Rezensionen und Entwicklerinformationen. Er stellt 21 Tools bereit, etwa play_search_apps, play_get_app, play_get_apps.
Zusammenfassung generiert aus dem README des Projekts
Über Google Play Store MCP server
Entwickler können KI-Agenten mit diesem MCP server schreibgeschützten Zugriff auf öffentliche Google Play Store Daten geben. Er ermöglicht es Agenten, App-Details, Suchergebnisse, Nutzerbewertungen und Entwicklerinformationen abzurufen. Der Server ist für die Arbeit mit lokalen Clients wie Claude Code, Codex CLI und OpenCode via stdio oder mit Remote-Clients wie ChatGPT und der OpenAI API über streamable HTTP ausgelegt.
Bei der Remote-Nutzung benötigt der Server aus Sicherheitsgründen einen Token, der über einen Authorization Header oder als Teil eines geheimen URL-Pfads übergeben werden kann. Er enthält spezifische Tools wie play_search_apps für Keyword-Matches, play_get_chart für den Zugriff auf Top-Listen (kostenlos oder kostenpflichtig) und play_get_reviews zum Abrufen von Nutzerfeedback. Für Massendaten-Operationen wie das Katalogisieren von Sitemaps oder das vollständige Auslesen von Rezensionen weist der Server die Agenten an, das separate gpscrape CLI Tool zu verwenden. Diese Unterscheidung stellt sicher, dass der MCP server leichtgewichtig bleibt und schnell auf interaktive Agenten-Aufgaben reagiert.
Geschrieben aus dem README des Projekts. Jeder Use Case wurde gegen ein Zitat daraus geprüft.
So installierst du Google Play Store MCP
Formate geprüft am 10. Nov. 2026Zu Cursor hinzufügenZu Goose hinzufügenGoogle Play Store MCP in Claude Code installieren
$ claude mcp add gpscrape -- docker run -i --rm ghcr.io/kryuchenko/gpscrape-mcp:0.1.2Google Play Store MCP in Cursor installieren
~/.cursor/mcp.json
{
"mcpServers": {
"gpscrape": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/kryuchenko/gpscrape-mcp:0.1.2"
]
}
}
}Google Play Store MCP in VS Code installieren
.vscode/mcp.json
{
"servers": {
"gpscrape": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/kryuchenko/gpscrape-mcp:0.1.2"
]
}
}
}Google Play Store MCP in VS Code CLI installieren
$ code --add-mcp '{"name":"gpscrape","type":"stdio","command":"docker","args":["run","-i","--rm","ghcr.io/kryuchenko/gpscrape-mcp:0.1.2"]}'Google Play Store MCP in Claude Desktop installieren
claude_desktop_config.json
{
"mcpServers": {
"gpscrape": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/kryuchenko/gpscrape-mcp:0.1.2"
]
}
}
}Google Play Store MCP in Codex installieren
$ codex mcp add gpscrape -- docker run -i --rm ghcr.io/kryuchenko/gpscrape-mcp:0.1.2Google Play Store MCP in Codex config.toml installieren
~/.codex/config.toml
[mcp_servers.gpscrape] command = "docker" args = ["run", "-i", "--rm", "ghcr.io/kryuchenko/gpscrape-mcp:0.1.2"]
Google Play Store MCP in Gemini CLI installieren
$ gemini mcp add -s user gpscrape docker -- run -i --rm ghcr.io/kryuchenko/gpscrape-mcp:0.1.2Google Play Store MCP in Gemini settings.json installieren
~/.gemini/settings.json
{
"mcpServers": {
"gpscrape": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/kryuchenko/gpscrape-mcp:0.1.2"
]
}
}
}Google Play Store MCP tools 21
Erkannt aus dem READMEplay_search_appsplay_get_appplay_get_appsplay_get_chartplay_get_reviewsplay_get_similar_appsplay_get_developer_appsplay_get_permissionsplay_get_data_safetyplay_suggest_queriesplay_list_categoriesplay_check_availability
| play_search_apps | — | |
| play_get_app | — | |
| play_get_apps | — | |
| play_get_chart | — | |
| play_get_reviews | — | |
| play_get_similar_apps | — | |
| play_get_developer_apps | — | |
| play_get_permissions | — | |
| play_get_data_safety | — | |
| play_suggest_queries | — | |
| play_list_categories | — | |
| play_check_availability | — |
Alle 21 Tools anzeigenWeniger Tools anzeigen
invalid_argumentnot_foundnot_listedrate_limitedtimeoutbusycancelledstore_errorinternal
| invalid_argument | — | |
| not_found | — | |
| not_listed | — | |
| rate_limited | — | |
| timeout | — | |
| busy | — | |
| cancelled | — | |
| store_error | — | |
| internal | — |
Konfiguration
GPSCRAPE_MCP_TOKEN
| Name | Beschreibung | Typ |
|---|---|---|
| GPSCRAPE_MCP_TOKEN | — |
Automatisierte Checks
Geluften am 13. Nov. 2026Vollständiger Bericht →Unsere automatisierten Checks bestanden. Das ist kein Security-Audit: Lies den Code und gib dem Server nur den minimal notwendigen Zugriff. Wie die Checks funktionieren
- Source Repository verknüpft und erreichbarBestanden
- Open Source Lizenz (OSI)Bestanden
- Commit oder Release im letzten JahrBestanden
- Package-Name ähnelt keinem populären PackageNicht geprüft
- Remote Endpoint nutzt HTTPSNicht geprüft
- Destruktive Tools sind markiertBestanden
- Keine versteckten Anweisungen an das ModellBestanden
- Keine kritischen Advisories im Paket oder seinen AbhängigkeitenNicht geprüft
README
Auf GitHub ansehengpscrape-mcp
An MCP server that gives AI agents read-only access to public Google Play Store data: app details, search, charts, reviews, similar apps, developer listings, permissions, data safety, search suggestions and per-country availability.
It works with any MCP client. Claude Code, Codex CLI and OpenCode start it as a local process over stdio. ChatGPT, the OpenAI API and other remote clients reach it over Streamable HTTP.
This is a separate Go module, so the root library keeps its zero-dependency
guarantee. The long sweeps (the sitemap catalog, every review of an app) are
left out on purpose and stay in the gpscrape command. The
server tells the agent so, in its instructions and again in the play_get_reviews
tool description (some clients, such as claude.ai and the OpenAI Agents SDK,
do not pass instructions to the model). An agent that can run shell commands
is pointed at gpscrape for bulk jobs if it is already installed. If it is
not, the agent pages with the tools or tells the user the job needs the CLI,
and it is told to ask the user before installing it. The instructions open
with the untrusted-data warning and stay short; every tool description stays
under 1000 bytes, where Codex cuts them for servers installed as plugins.
Install
go install github.com/kryuchenko/google-play-scraper/mcp/cmd/gpscrape-mcp@latest
Requires Go 1.27. Without Go:
- Prebuilt binaries for macOS, Linux and Windows are attached to each
mcp-v*release (the Go module tag ismcp/v*; the release uses a tag without the slash, which the MCP Registry requires in download URLs). - MCPB bundle:
gpscrape-mcp.mcpbon the same release installs in one step in clients that take MCP bundles, such as Claude Desktop. It carries macOS (universal), Linux (amd64 and arm64) and Windows (amd64) binaries. - Container:
docker run -i --rm ghcr.io/kryuchenko/gpscrape-mcpspeaks stdio; for HTTP,docker run --rm -p 8080:8080 -e GPSCRAPE_MCP_TOKEN=<token> ghcr.io/kryuchenko/gpscrape-mcp -http 0.0.0.0:8080. - MCP Registry: listed as
io.github.kryuchenko/gpscrape, so clients that browse the registry can find it.
Every release file and the image carry signed build provenance. Check a download before running it:
gh attestation verify gpscrape-mcp.mcpb --repo kryuchenko/google-play-scraper
gh attestation verify oci://ghcr.io/kryuchenko/gpscrape-mcp:<version> --repo kryuchenko/google-play-scraper
For agents that also have a shell, the
gpscrape skill explains when to reach for the
CLI instead of these tools.
Connect a client
Claude Code
claude mcp add gpscrape -- gpscrape-mcp
Codex CLI: ~/.codex/config.toml
[mcp_servers.gpscrape]
command = "gpscrape-mcp"
OpenCode: ~/.config/opencode/opencode.json or opencode.json in a project
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"gpscrape": { "type": "local", "command": ["gpscrape-mcp"], "enabled": true }
}
}
Over HTTP: for clients that cannot start a local process
gpscrape-mcp -http 127.0.0.1:8080 # this machine only, no token
GPSCRAPE_MCP_TOKEN=$(openssl rand -hex 32) \
gpscrape-mcp -http :8080 # any interface, token required
The endpoint is http://<host>:8080/mcp. Clients send
Authorization: Bearer <token>. GET /healthz answers ok for probes. The
server will not bind a non-loopback address without a token. Put TLS in front
of it (nginx, Caddy) before exposing it to the internet. Without a token the
server refuses requests whose Host is not local (DNS-rebinding protection),
so a reverse proxy that forwards the public Host needs a token set.
Every method rejects an invalid Origin with 403, even if Fetch Metadata
claims the request is same-origin. Native clients can omit Origin; browser
origins must be HTTP(S) and match the request's public Host.
HTTP is sessionless: no Mcp-Session-Id is issued, and GET/DELETE return 405.
Protocol 2026-07-28 requests stop upstream work when their HTTP request is
cancelled. Legacy HTTP clients' cancellation notifications cannot reach work
running in a different request's temporary session; the per-call timeout
still bounds that work. Stdio cancellation uses the persistent connection.
Give the token in $GPSCRAPE_MCP_TOKEN or in a file with -token-file
(a Docker or systemd secret, for instance). There is no -token flag: a
secret on the command line is visible to every user of the machine in ps.
ChatGPT cannot start a local process and cannot send a token: its custom
apps take OAuth or nothing. Host the server yourself (a VPS, or your own
machine behind a tunnel such as Cloudflare Tunnel) with HTTPS in front, start
it with -secret-path, and give ChatGPT the token as the last part of the
URL:
https://play-mcp.example.com/mcp/<GPSCRAPE_MCP_TOKEN>
Add it in ChatGPT as a custom app (developer mode) with
No authentication: the secret path is the password. It is off unless
-secret-path is given, because a token in a URL ends up in proxy logs and
browser history; any path under /mcp/ answers 404 without it, and so does a
wrong token with it. Use a long random token (openssl rand -hex 32); the
server warns when it is shorter than 24 characters. Keep your proxy from
logging request paths, and rotate the token if the URL leaks. Requests to
Google Play then come from the host's IP, and Google rate-limits data-centre
addresses sooner than a home one.
claude.ai (and Claude Desktop, which shares claude.ai's connectors) does
not need the secret path: its custom connectors can send a fixed header.
claude.ai/customize/connectors → Add custom connector, enter
https://play-mcp.example.com/mcp, choose "No sign in", and under Request
headers add Authorization with the value Bearer <GPSCRAPE_MCP_TOKEN>
(the field takes the value as is, so the Bearer prefix is yours to type).
Claude connects from Anthropic's cloud, not from your device, so the server
must be reachable from the internet as for ChatGPT. claude.ai does not pass a
server's instructions to the model
(anthropics/claude-ai-mcp#93);
the play_get_reviews description repeats what matters, and the tools work
without them. (Anthropic: custom connectors)
For Claude Desktop on one machine there is a simpler way: install
gpscrape-mcp.mcpb from the release page, and Desktop runs the server
locally over stdio.
Remote clients that can set a header point at the URL:
# Codex
[mcp_servers.gpscrape]
url = "https://play-mcp.example.com/mcp"
bearer_token_env_var = "GPSCRAPE_MCP_TOKEN"
// OpenCode
"gpscrape": {
"type": "remote",
"url": "https://play-mcp.example.com/mcp",
"headers": { "Authorization": "Bearer {env:GPSCRAPE_MCP_TOKEN}" }
}
Tools
| Tool | What it returns | Default / max |
|---|---|---|
play_search_apps |
apps matching keywords, with package ids | 20 / 50 |
play_get_app |
one app's store page, including whether it can be installed in that country; response_format: detailed adds description, histogram, developer contacts |
— |
play_get_apps |
concise details for several package ids in one request | up to 20 ids |
play_get_chart |
a chart: top_free, top_paid, grossing, new_free, new_paid, movers_shakers |
50 / 200 |
play_get_reviews |
one page of reviews; next_token for the next page; filter by star rating |
20 / 100 |
play_get_similar_apps |
apps the store lists as similar | 20 / 100 |
play_get_developer_apps |
apps by one developer | 20 / 100 |
play_get_permissions |
Android permissions, grouped | — |
play_get_data_safety |
declared data collection, sharing and security practices | — |
play_suggest_queries |
autocomplete suggestions for a query | — |
play_list_categories |
category ids accepted by play_get_chart |
— |
play_check_availability |
per country: available, region_locked (listed, not installable) or not_listed |
up to 50 countries |
Tools take lang and country (default en, us), with three exceptions:
play_get_reviews takes only lang, play_check_availability takes a list
of countries, and play_list_categories takes nothing. An unknown country code or a malformed language
code is an error, because the store would silently answer with its defaults.
In play_get_reviews, lang selects the language group of the reviews (Google's
grouping, so a few may be in other languages); reviews are the same in every
country. Prices, charts and installability depend on country.
play_search_apps, play_get_chart, play_get_similar_apps and
play_get_developer_apps fetch full details for their
results (one extra batched request per 32 apps), because the store's result
rows carry no developer id, and outside charts no price.
Design notes
-
Names say what they do.
play_+ verb + object, as Anthropic's tool guidance (namespacing) and OpenAI's (action-oriented names) both ask; the prefix also keeps them apart from another store's tools in one session. -
Small answers by default. Lists come back as one-line summaries.
play_get_reviewscuts each text to 400 characters unless you ask fordetailed, and says how many it returned, which filters applied and whether anything was cut. -
Schemas both ways. Input schemas carry
minimum/maximum,enumand array lengths, so a client can check an argument before calling; an omitted number takes its default, an explicit0is out of range. Every tool also publishes an output schema, as OpenAI's MCP guidance asks for structured results, and the server validates each result against it before sending. That roughly doublestools/list(about 17.5 KB, from 9.8 KB); clients with tool search load definitions on demand and pay it only for the tools they use. Results come back asstructuredContentand as the same JSON incontent, because some clients (the OpenAI Agents SDK by default) show the model onlycontent. -
Ids as they come.
app_idtakes a package id or a store link with?id=. -
One contract with the CLI. The records these tools return are the ones in package
records, andgpscrapewrites the same objects one per line, with the same error codes. A filter or parser written against one works on the other;records/testdata/fields.txtpins the field names. -
Third-party text is marked. Review text, reviewer names, developer replies, app summaries, descriptions and release notes come back in fields named
untrusted_*, and the server's instructions tell the agent to treat them as data, not instructions. -
Errors say what to do next, behind a stable code. Every tool error reads
code: what to do. A name instead of a package id points toplay_search_apps; an unknown category points toplay_list_categoriesbefore any request is made; a 404 says to check the id or the country; a block says to wait; a bug that panics returns an error instead of ending the session. The codes:Code Meaning Retry? invalid_argumentfix the arguments no not_foundno such app or page in this storefront another id or country not_listedthe store returned nothing for this id here once, then check the id rate_limitedthe store is refusing this server for now after a few minutes timeoutthe store did not answer in time once busythis server is at capacity shortly cancelledthe client cancelled the call — store_errorany other failure talking to the store once internala bug in gpscrape-mcp no; report it Arguments that break the input schema are rejected by the MCP SDK before the tool runs; those errors start with
validating "arguments". -
Gentle on the store, bounded on the server. Requests to Google Play are throttled and retried honouring
Retry-After. Tool calls run at most-max-concurrentat once, at most four times that many wait for a slot, and any further call is refused at once asbusy. String arguments have a maximum length in the schema.play_check_availabilitygets twice the-timeout. -
Progress for the slow tool.
play_check_availabilitymakes one store request per country and can take two minutes for fifty. A client that sends aprogressTokengets a notification per country over stdio (the stateless HTTP transport answers with one JSON body and has no stream to send them on). -
Cancelled means cancelled. A call the client cancelled returns no result, even if the work behind it finished.
-
Cacheable catalog.
tools/listandserver/discoversayttlMsof an hour: the tool set never changes while the server runs.
Flags
-http addr serve Streamable HTTP instead of stdio
-token-file path read the bearer token from a file (default $GPSCRAPE_MCP_TOKEN)
-secret-path also accept the token as /mcp/<token>, for ChatGPT
-throttle 300ms minimum interval between requests to Google Play
-max-concurrent 4 tool calls running at once
-timeout 60s time limit for one tool call
-v log every tool call to stderr
-version print the version
Logs go to stderr only. In stdio mode stdout carries the protocol.
Conformance
CI runs the official MCP conformance suite
against the HTTP server. Most of its server scenarios call fixtures of the
reference test server (test_simple_text, test_sampling, test prompts and
resources) or features this server does not offer (completion, resource
subscriptions, sessions); conformance-baseline.yml
lists them with the reason. Everything else must pass. To run it locally:
gpscrape-mcp -http 127.0.0.1:3001 &
npx -y @modelcontextprotocol/conformance@0.1.16 server \
--url http://127.0.0.1:3001/mcp --expected-failures conformance-baseline.yml
Google Play Store MCP Fragen
Wie füge ich Google Play Store MCP zu Claude Code hinzu?
Führe claude mcp add gpscrape -- docker run -i --rm ghcr.io/kryuchenko/gpscrape-mcp:0.1.2 in deinem Terminal aus. Füge --scope user hinzu, damit der Server in jedem Projekt verfügbar ist.
Wie füge ich Google Play Store MCP zu Cursor hinzu?
Öffne ~/.cursor/mcp.json und füge den Server unter mcpServers hinzu, mit der Cursor-Config aus dem Installationsabschnitt oben.
Welche Tools bietet Google Play Store MCP?
Er stellt 21 Tools bereit, darunter play_search_apps, play_get_app, play_get_apps, play_get_chart, play_get_reviews.
Welche Art von Daten kann ich abrufen?
Du kannst auf App-Details, Suchergebnisse, Charts, Rezensionen, ähnliche Apps, Entwicklerlisten, Berechtigungen, Datensicherheit und die Verfügbarkeit in einzelnen Ländern zugreifen.
Wie installiere ich den Server?
Du kannst ihn via Go mit go install github.com/kryuchenko/google-play-scraper/mcp/cmd/gpscrape-mcp@latest installieren oder vorgefertigte Binaries und Docker-Container nutzen.
Kann ich das mit ChatGPT nutzen?
Ja, aber da ChatGPT keine lokalen Prozesse starten kann, musst du den Server selbst hosten und den Token als Teil der URL bereitstellen.
Sind die Daten sicher als Instruktionen nutzbar?
Nein, Texte von Drittanbietern wie Rezensionen und Beschreibungen sind als untrusted data markiert, damit der Agent weiß, dass er sie als Daten und nicht als Instruktionen behandeln muss.