Skip to main content
Glama
app-reviews

app-reviews

by pipeworx-io

@pipeworx/app-reviews

Customer reviews of Apple App Store apps, and the app page, keyword search and user reviews of Google Play apps. Live and keyless.

Part of Pipeworx — an MCP gateway connecting AI agents to 2034+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

  • appstore_reviews(app_id, country?, sort?, page?, limit?) — recent or most-helpful reviews of an App Store app in one country storefront: rating, title, text, version, date, helpful votes.

  • gplay_app(app_id, lang?, country?) — Google Play listing: title, developer, category, rating, rating count, install band, price, content rating, description.

  • gplay_search(query, lang?, country?, limit?) — Google Play keyword search: package name, title, developer.

  • gplay_reviews(app_id, sort?, limit?, lang?, country?) — Google Play user reviews, newest, relevant or by rating.

Related MCP server: AppRanks MCP Server

Auth

Keyless.

Data sources

  • Apple, App Store customer reviews (public, per app and storefront).

  • Google, Google Play public app pages, search and reviews.

Reviewer names, profile data, user identifiers and avatars are not served.

Gotchas: Apple serves at most 10 pages of 50 reviews per app and storefront, and returns an empty page past the end (the tool reports that as an error rather than an empty list). Google Play app data is read from the public page, so a layout change shows up as an explicit "no app data" error, not an empty result. Find an App Store numeric id with itunes_search_search.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "app-reviews": {
      "url": "https://gateway.pipeworx.io/app-reviews/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/app-reviews/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 2034+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/appstore_reviews \
  -H 'Content-Type: application/json' \
  -d '{"app_id":"389801252","country":"us","limit":5}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/appstore_reviews. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Run it from npm

@pipeworx/mcp-app-reviews is a local stdio bridge to the Pipeworx gateway: your MCP client starts it with npx, and it forwards every call to the same https://gateway.pipeworx.io/app-reviews/mcp endpoint shown above. It needs network access; there is no offline mode.

{
  "mcpServers": {
    "app-reviews": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-app-reviews"]
    }
  }
}

Without a key it calls anonymously, capped at 50 calls a day. A free account raises that to 200 a day: get a key at https://pipeworx.io/signup and add "env": { "PIPEWORX_API_KEY": "<your key>" } to the server entry. The key is sent as a Bearer token, the same way a hosted connection sends it, so calls are metered and billed exactly as they are there.

It lists only this pack's tools by default. Set PIPEWORX_META_TOOLS=1 to also list ask_pipeworx and the other gateway-wide tools.

Behind an HTTPS proxy: Node's built-in fetch does not read HTTPS_PROXY by default. Newer Node releases honour it when NODE_USE_ENV_PROXY=1 is set; check your Node version's documentation.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about App Reviews data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    • App Store and Google Play reviews, ratings, sentiment and developer replies as agent tools.

    • Your agent needs app-store data — what an app looks like on the App Store and Google Play, what reviewers say, and what ranks for a search in a given country. **What you can ask for** • "What does this app's store listing look like, and how is it rated?" • "Pull recent reviews for this app and group the complaints." • "What apps rank for this search term in Japan?" • "List the top apps in this category on both stores." • "Compare this app's listing on iOS and Android." **How to use it** Point any MCP client at https://mcp.aisa.one/seo-apps/mcp and sign in with OAuth — there is no key to create or paste. 37 tools: Apple App Store and Google Play app info, app lists, category listings, reviews and store search results, in live and queued forms, with categories, languages and locations for each. **It is also a door to the rest** The same login reaches 26 sources and 580+ operations. Read the store listing here, then ask the same agent what the app's website ranks for — without adding a second server. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** https://mcp.aisa.one/seo/mcp for all of it at once — rankings, keywords, backlinks, site health and AI-answer visibility across DataForSEO, Semrush and Ahrefs.

    • ASO tools for AI agents: keyword research, rank tracking, competitor analysis (iOS & Android).

      https://trysonar.app/mcp
    • Live App Store and Google Play data for AI agents: revenue and download estimates for 3.6M+ apps, app search and filters, ASO keyword research, reviews and listing change history. Read-only tools; API key from GetAppNiche (https://getappniche.com/mcp).

      https://api.getappniche.com/mcp

    Related MCP Servers

    • A
      license
      C
      quality
      D
      maintenance
      Enables querying and retrieving data from App Store and Google Play Store, including app details, reviews, ratings, rankings, permissions, and search capabilities across both iOS and Android platforms.
      20
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides live App Store rankings, charts, app details, reviews, and search across 55 countries, enabling AI assistants to query app store data.
      17 npm
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Provides App Store Optimization tools for AI agents, enabling app lookup, keyword research, ASO audit, review mining, and revenue estimation across iOS and Google Play.
      43
      99 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to research mobile apps, compare onboarding and paywall flows, explore App Store reviews, and find visual UI references, bringing real screens and market context into their research.
      3
      MIT