App Reviews

io.github.shawmena-dotcomPublished by GitHub account shawmena-dotcomv1.0.0Updated Oct 24, 2026

App Store + Google Play reviews with per-app complaint summary for agents.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

A remote Apify-hosted MCP server that gives an assistant App Store and Google Play reviews plus a per-app complaint summary.

What you can do
Retrieve App Store and Google Play reviews for a given app, so an assistant can read user feedback directly in a conversation. Produce a per-app complaint summary that condenses recurring issues from those reviews. Runs are executed on Apify's hosted endpoint rather than locally.
When to use it
Useful when you want an assistant to look at mobile app user feedback, spot recurring complaints, or summarize what reviewers say about a specific app without building your own scraping pipeline.
Requirements
A remote MCP endpoint at mcp.apify.com over streamable HTTP. An Apify account and an Apify API token, supplied as an Authorization header in the form Bearer followed by the token. OAuth authentication is declared as required. Network access to Apify.
Before you install
The Apify API token is a secret passed in the Authorization header; keep it private. Runs are billed per review and per app summary to your Apify account, so usage costs money. Review data is fetched through Apify's third-party service.

Installation

In SourceWeft

  1. Open App Reviews in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.shawmena-dotcom%2Fapp-reviews/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "app-reviews": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=cybermax/app-reviews"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 24, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.