review-intel
Related Servers
Alternatives to review-intel
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for Claude Desktop that exposes App Store Connect and RevenueCat APIs, enabling indie iOS developers to query portfolio metrics, sales reports, subscriptions, and customer reviews directly in chat.17MIT

GetAppNiche MCPofficial
AlicenseNot gradedqualityAmaintenanceEnables AI agents to query live App Store and Google Play data, including app search, revenue/download metrics, keyword difficulty, and reviews, via a hosted MCP server with API-key authentication.76 npmMIT- AlicenseNot gradedqualityDmaintenanceRemote MCP server that exposes Airspeed/Glyphic call data to Claude web, enabling tools to list, retrieve, and query calls, transcripts, snippets, and playbooks.ISC
- AlicenseNot gradedqualityBmaintenanceExposes MCP tools that give desktop agents durable two-tier memory with recall and graph traversal, project code intelligence (symbol lookup, impact walking, notes search), and web search with page-to-Markdown conversion. It also runs a local model gateway that routes Anthropic- and OpenAI-shaped traffic across providers with usage accounting.MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that exposes Google Play Console analytics to AI agents, including store-listing acquisitions by traffic source, installs, uninstalls, ratings, crashes, subscriptions, and reviews by reading bulk CSV reports from Cloud Storage.MIT
- AlicenseNot gradedqualityBmaintenanceExposes specialized agents as MCP tools so users can manage and triage Jira tasks, analyze repositories for health and conventions, generate commit/PR/DevOps patterns, assemble reports, produce slides and infographics, and run semantic search over a knowledge base. Everything is invokable directly from inside a coding session in Claude Code, Cursor, or Claude Desktop.1MIT
TDQS
Scored across 5 tools
Each tool targets a distinct analysis mode: raw semantic retrieval (search_reviews), complaint aggregation (top_issues), version diffing (compare_versions), time-series sentiment (sentiment_trend), and open-ended Q&A (ask). The main soft spot is `ask`, which is a general-purpose catch-all that could plausibly answer anything the other four handle, but its description explicitly tells agents to prefer the others, which mitigates the overlap.
All names are snake_case and self-descriptive, but the grammatical pattern varies: verb_noun (search_reviews, compare_versions), noun phrases (top_issues, sentiment_trend), and a bare verb (ask). It reads cleanly and an agent can infer intent, with `ask` being the only notably vague outlier.
Five tools is tightly scoped for a review-analytics server, with each tool covering a genuinely different question type (retrieval, ranking, comparison, trend, synthesis). Nothing feels padded or redundant.
The surface covers search, aggregation, version comparison, trends, and open Q&A with cited review ids, which is most of the review-intel lifecycle. Minor gaps: no direct fetch-by-review-id, no standalone patch-notes or category-taxonomy listing (those are only reachable indirectly through compare_versions and ask).