# trysonar/mcp [Health: Active]

**Category:** 🎯 Marketing  
**Repository:** https://github.com/trysonar/mcp  
**GitHub Stars:** 0  
**npm Downloads (last month):** 1168  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/trysonar-mcp

## Description
App Store Optimization for AI agents — keyword research with difficulty and popularity scores, daily rank tracking, review mining, competitor gap analysis, and revenue estimation across the iOS App Store and Google Play. 32 tools. npx @sonarapp/mcp

## Tools
Capabilities this server exposes over MCP:

- **sonar_app_lookup** — Look up a single app by its store ID. Returns app metadata including name, developer, category, rating, reviews, installs (Android), and price. Works without an API key (free tier, limited daily use per IP).
- **sonar_app_search** — Search apps in the App Store or Google Play by keyword. Returns ranked list of apps with metadata (results are returned in store ranking order). Works without an API key (free tier, limited daily use per IP).
- **sonar_app_aso_score** — Calculate an ASO (App Store Optimization) audit score (0-100) for an app. Returns the overall score plus an itemized breakdown of checks (title length, keyword usage, screenshots, ratings, etc.) so you can identify what to improve. Works without an API key (free tier, limited daily use per IP).
- **sonar_app_extract_keywords** — Extract the most likely target keywords from an app's title and description, ranked by relevance. Useful for understanding what an app (yours or a competitor) is optimizing for. Works without an API key (free tier, limited daily use per IP).
- **sonar_app_reviews** — Fetch user reviews for an app. Supports filtering by star rating range and sorting by recent or helpful. Useful for sentiment analysis, feature-request mining, and competitive research.
- **sonar_app_revenue** — Estimate monthly revenue for an app, based on install counts, ratings, and category benchmarks. Returns the dollar estimate, a confidence grade (high/medium/low) with the factors behind it, and the methodology used — always communicate the confidence alongside the number.
- **sonar_keyword_search** — Research a keyword and related terms. Returns difficulty (0-100), popularity score, and results count for the seed keyword plus related autocomplete suggestions. Use this to find keywords worth targeting.
- **sonar_keyword_metrics** — Difficulty + popularity for a specific keyword (or up to 25 in bulk). Use this when you already know which keywords you care about — costs 1 credit per keyword. Works without an API key for up to 5 keywords/day (free tier, per IP); an API key removes that cap. Use sonar_keyword_search instead when you want related keyword ideas alongside metrics.
- **sonar_keyword_suggestions** — Get autocomplete suggestions for a seed keyword from the App Store or Google Play. Returns terms with a priority score (higher = more searched). Lighter and faster than sonar_keyword_search — use when you only need term ideas without difficulty/popularity scoring. Works without an API key (free tier, limited daily use per IP).
- **sonar_top_charts** — Get a store top chart (free / paid / grossing, overall or by category) with day-over-day movement: per-app rank delta, apps new to the chart, biggest movers and apps that dropped out. Use to see what's rising in a market or category. Note: summary, movers and droppedApps always describe the full top 200 — `limit` truncates the returned entries only. Movement is empty on the first day a chart is requested (no previous snapshot yet). Works without an API key (free tier, limited daily use per IP).
- **sonar_list_apps** — List the apps tracked in the caller's Sonar workspace (own apps + competitors), each with its latest snapshot (rating, review count, version, installs). Returns the Sonar app UUIDs needed by sonar_get_app, sonar_app_keywords, sonar_app_rankings, and sonar_app_changes. Cursor-paginated (default 100 per page). Requires an Indie plan (trial counts).
- **sonar_get_app** — Get full details for one tracked app in the caller's Sonar workspace: store metadata plus up to 90 daily snapshots of rating, review count, version, and installs. Requires an Indie plan (trial counts).
- **sonar_app_keywords** — List the keywords tracked for an app in the caller's Sonar workspace, with latest difficulty, popularity, results count, note, and starred_at (favorite/target marker) per keyword. Returns the tracked-keyword ids used by sonar_update_keyword_note and sonar_star_keyword, and the keyword_ids used by sonar_keyword_rankings. Cursor-paginated (default 50 per page). Requires an Indie plan (trial counts).
- **sonar_app_rankings** — Rank history for an app's tracked keywords — daily ranks over the requested window, one history array per keyword. Use this to check how rankings moved after a metadata change or to find keywords trending up or down. Cursor-paginated over keywords (default 50 per page). Requires an Indie plan (trial counts).
- **sonar_app_changes** — Change history for a tracked app — detected releases, metadata edits, screenshot swaps, price changes, and category moves, newest first. Useful for correlating rank movements with what the app (or a competitor) changed. Requires an Indie plan (trial counts).
- **sonar_keyword_rankings** — SERP history for one tracked keyword — which apps ranked in the top results on each measured day, newest first. Use this to see who competes on a keyword and how the top spots shifted over time. The keyword must be tracked in the caller's Sonar workspace. Requires an Indie plan (trial counts).
- **sonar_competitor_keywords** — Keywords a tracked competitor currently ranks for (last 7 days of SERP data), with difficulty and popularity per keyword. Pass own_app_id for gap analysis: keywords where the competitor ranks but your app doesn't are marked gap=missing. Cursor-paginated (default 50 per page). Requires an Indie plan (trial counts).
- **sonar_competitor_landscape** — The full competitive keyword picture for one of your own apps vs every tracked competitor, in one call: live stats (keyword gaps where competitors rank and you don't, winnable gaps, competitors climbing on your tracked keywords, keywords you lead), the top gap/threat/lead rows with metrics, and the latest AI insight if one was generated (opportunity clusters, threat narratives, strengths, posture). Read this before deciding which keywords to target next. Requires an Indie plan (trial counts).
- **sonar_list_products** — List your products with their linked store versions and competitor counts. Use it to discover product/app UUIDs. Requires an Indie plan (trial counts).
- **sonar_list_alerts** — List your alert subscriptions — each rule defines a change type (rank drops, review spikes, etc.), its scope (a specific app or org-wide), threshold, and whether it's enabled. Requires an Indie plan (trial counts).
- **sonar_alert_events** — The detected alert events for your workspace, newest first — the same feed as the in-app Recent Alerts panel and the email digest: rank drops/gains, top-10 entries/exits, new rankings, rating drops, review spikes, and competitor changes, each with a type-specific payload (app/keyword names, old vs new values). Events only exist for alert types you've enabled rules for (sonar_set_alert); detection runs once daily. Poll with `since` to react to changes programmatically. Requires an Indie plan (trial counts).
- **sonar_app_overview** — The dashboard's computed scoreboard for one of your apps in a single call: visibility index and share of voice (with 7-day deltas and a daily spark), ranked / top-10 keyword counts with movement, best rank, the biggest 7-day improvements and drops, the rank-distribution trend, and the actionable opportunity list (near_page_one / top_three_push / easy_target). Read this FIRST when asked how an app is doing — it's the same numbers the dashboard renders, so you don't need to recompute anything from raw rank history. Requires an Indie plan (trial counts).
- **sonar_discovered_keywords** — Keywords Sonar's discovery engine surfaced for one of your tracked apps but that aren't tracked yet — ranked finds (the app already ranks, unnoticed), competitor gaps, and AI/autocomplete-sourced ideas — each with popularity, difficulty, AI relevance, and an opportunity score (0-100, best first). This is Sonar's "what should I track next" answer: read it, pick the winners, then track them with sonar_track_keywords. Requires an Indie plan (trial counts).
- **sonar_review_insights** — The latest AI review analysis for a tracked app (your own or a competitor): what users praise and complain about as named themes with frequency, verbatim quotes, and trend movement (new / persisting / growing / improving / resolved), plus overall sentiment, surfaced feature requests, and what changed vs the previous analysis. `insight` is null if none has been generated yet — use sonar_generate_review_insights. Requires an Indie plan (trial counts).
- **sonar_portfolio** — The whole portfolio's health in one call — for orgs managing many apps: per-app KPIs (visibility + 7-day delta, ranked/top-10 counts, net rank movement, rating, review count), org-wide totals, the biggest keyword movers in both directions, a needs-attention triage list (visibility drops, rating drops, not-ranked apps), and the best discovered-keyword opportunities across all apps. Same numbers as the /portfolio page. Requires an Agency plan (403 on other plans).
- **sonar_create_product** — WRITE tool — creates a product in the caller's Sonar workspace and starts tracking the given app(s). A product is the cross-store unit (one iOS + one Android app, or just one of either). Returns the product id and the Sonar app ids needed by sonar_track_keywords and sonar_track_competitor. Requires an Indie plan (trial counts) and an API key with the write scope.
- **sonar_track_app** — WRITE tool — links the second-store version of an existing Sonar product (e.g. the product already tracks the iOS app and you want to add the Android version, or vice versa). Each product holds at most one iOS + one Android app; to start tracking a brand-new app, use sonar_create_product instead. Requires an Indie plan (trial counts) and an API key with the write scope.
- **sonar_track_competitor** — WRITE tool — adds a competitor app under a Sonar product so its keywords and rankings get tracked alongside the product's own app. The product must already have its own app linked in the same store as the competitor. Requires an Indie plan (trial counts) and an API key with the write scope.
- **sonar_track_keywords** — WRITE tool — starts daily rank tracking for one or more keywords on an app in the caller's Sonar workspace. Idempotent: re-posting the same terms reports them as already_tracked instead of creating duplicates. Returns per-keyword outcomes (created / already_tracked / failed). Requires an Indie plan (trial counts) and an API key with the write scope.
- **sonar_update_keyword_note** — WRITE tool — sets or clears the note on a tracked keyword in the caller's Sonar workspace (e.g. why it's tracked, an optimization hypothesis, a reminder). Idempotent: re-sending the same note is a no-op. Requires an Indie plan (trial counts) and an API key with the write scope.
- **sonar_star_keyword** — WRITE tool — stars or unstars a tracked keyword in the caller's Sonar workspace. A star marks the keyword as a favorite/target the user is actively pursuing; starred keywords carry a starred_at timestamp in sonar_app_keywords results. Idempotent: re-starring refreshes the timestamp, unstarring a non-starred keyword is a no-op. Requires an Indie plan (trial counts) and an API key with the write scope.
- **sonar_scan_competitor** — WRITE tool — runs an AI keyword discovery scan on a tracked competitor: generates the search terms the competitor's listing is optimized for (brand terms included), queues them for SERP verification, and verifies the first batch inline (~30s), recording both apps' ranks. Returns generated/queued/verified_now counts; the rest verify in the background over the following hours — read results with sonar_competitor_keywords. Requires an Indie plan (trial counts) and an API key with the write scope.
- **sonar_analyze_competitors** — WRITE tool — generates a fresh AI competitive insight for one of your own apps: clusters the keyword gaps vs your competitors into named opportunity themes (with a why-now narrative and per-keyword metrics), writes threat narratives for competitors climbing on your keywords, and diffs against the previous analysis. At most one analysis per app per 7 days (429 with the next available time while in cooldown — use sonar_competitor_landscape to read the current one). Requires a paid (non-trial) Indie plan and an API key with the write scope.
- **sonar_generate_review_insights** — WRITE tool — generates a fresh AI review analysis for a tracked app from its recent reviews (praise/complaint themes, sentiment, feature requests, trend vs the previous run). At most one analysis per app+country every 90 days (429 with the next available time while in cooldown — use sonar_review_insights to read the current one); needs at least 5 recent reviews. Requires a paid (non-trial) Indie plan and an API key with the write scope.
- **sonar_delete_tracked_keyword** — WRITE tool — stop tracking one keyword/app pair in the caller's Sonar workspace. Identify the pair by its tracked-keyword id (from sonar_app_keywords). Requires an Indie plan (trial counts) and an API key with the write scope.
- **sonar_untrack_keywords** — WRITE tool — bulk-untrack keywords for an app in the caller's Sonar workspace. Pass `all: true` to remove every tracked keyword, OR `ids: [...]` to remove specific ones (exactly one of the two). Requires an Indie plan (trial counts) and an API key with the write scope.
- **sonar_untrack_app** — WRITE tool — untrack an app and its associated tracking data in the caller's Sonar workspace. Requires an Indie plan (trial counts) and an API key with the write scope.
- **sonar_delete_product** — WRITE tool — delete a product and untrack its apps in the caller's Sonar workspace. Requires an Indie plan (trial counts) and an API key with the write scope.
- **sonar_remove_competitor** — WRITE tool — remove a competitor from a product in the caller's Sonar workspace. Requires an Indie plan (trial counts) and an API key with the write scope.
- **sonar_set_alert** — WRITE tool — create or update an alert subscription in the caller's Sonar workspace. Upserts on (type + scope): re-submitting the same type/scope updates the existing rule. Omit `threshold` for the per-type default; omit `scope_app_id` for an org-wide rule. Requires an Indie plan (trial counts) and an API key with the write scope.
- **sonar_delete_alert** — WRITE tool — delete an alert subscription in the caller's Sonar workspace. Requires an Indie plan (trial counts) and an API key with the write scope.
- **sonar_screenshot_layout_guide** — The layout-format reference for Sonar screenshot sets. Call this ONCE before creating or editing screenshot layouts — it documents the layout JSON schema, coordinate system, image handling (remote URLs), flowing background shapes, fonts, translation overrides, and the recommended workflow.
- **sonar_screenshot_devices** — List the device sizes supported for app-store screenshot sets, with their canvas dimensions (the pixel coordinate space all layouts use) and which store each belongs to. Pick a device here before sonar_create_screenshot_set.
- **sonar_list_screenshot_sets** — List a product's app-store screenshot sets (metadata only: store, device size, locales, studio_url). Use sonar_get_screenshot_set for full layouts.
- **sonar_create_screenshot_set** — Create an app-store screenshot set for a product. Read sonar_screenshot_layout_guide first, then author the screens array. The set is immediately visible/editable for humans in the Screenshot Studio (studio_url in the response). Requires a write-scope API key.
- **sonar_get_screenshot_set** — Fetch a screenshot set in full: every screen's layout JSON plus per-screen translation overrides keyed by locale. By default inline image data is replaced with placeholders to keep the response readable.
- **sonar_update_screenshot_set** — Rename a screenshot set, replace its extra-locale list, and/or reorder its screens. Returns the updated set (with image data stripped). Requires a write-scope API key.
- **sonar_delete_screenshot_set** — Permanently delete a screenshot set and everything in it (screens, translations). Irreversible — confirm with the user before deleting work they may want. Requires a write-scope API key.
- **sonar_add_screenshot** — Append a screen to a screenshot set (at the end; reorder with sonar_update_screenshot_set). Requires a write-scope API key.
- **sonar_update_screenshot** — Replace one screen's layout in a screenshot set. Whole-document replace — fetch the current layout, modify it, send it back. The change shows up immediately in the Screenshot Studio for human review. Requires a write-scope API key.
- **sonar_delete_screenshot** — Delete one screen from a screenshot set. A set keeps at least one screen — deleting the last one is rejected. Requires a write-scope API key.
- **sonar_set_screenshot_translations** — Write a locale's translation overrides for screens in a screenshot set (text copy, localized captures/images). Geometry and styling always come from the source layout; anything not overridden falls back to it. The locale is auto-enabled on the set. Requires a write-scope API key.
- **sonar_export_screenshots** — Render a screenshot set to store-ready PNGs SERVER-SIDE (no browser needed) and save them as one ZIP per locale in output_dir — ready for App Store Connect / Play Console upload. Rendering happens through the same engine as the Screenshot Studio editor. Writes to the filesystem of the machine running the MCP server, so this tool is for local (stdio) use; over the hosted transport call GET /api/v1/screenshots/sets/:id/export directly instead.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "mcp": {
    "command": "npx",
    "args": ["-y","@sonarapp/mcp"],
    "env": {
      "SONAR_API_KEY": "",
      "SONAR_API_URL": ""
    }
  }
}
```

**Requires environment variables:** `SONAR_API_KEY`, `SONAR_API_URL` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What the trysonar/mcp MCP server does

The trysonar/mcp MCP server exposes Sonar's App Store Optimization features through Model Context Protocol. It covers both the iOS App Store and Google Play, allowing an MCP-compatible client to inspect public app-store data and, with authentication, query data stored in a Sonar workspace.

Public or stateless capabilities include looking up an app by store ID, searching apps by keyword, calculating an ASO score, extracting likely target keywords, fetching reviews, estimating monthly revenue, researching keyword difficulty and popularity, retrieving autocomplete suggestions, and reading top-chart movement. Revenue results include an estimate, confidence grade, contributing factors, and methodology, so the numeric result should not be treated as exact financial data.

Workspace tools provide a longer-term view of tracked apps and competitors. They can return app snapshots, tracked keyword metrics, daily ranking history, detected listing changes, competitor keyword gaps, SERP history, and a competitive landscape. Additional tools cover products, alerts, alert events, app-level dashboards, discovered keywords, review insights, and portfolio reporting. Write operations can create products, link store versions, add competitors, start keyword tracking, and maintain keyword notes.

## How it works

The package is a thin client for Sonar's REST API and does not keep local state. Inputs such as app IDs, keywords, and country codes are sent over HTTPS; authenticated calls send the API key as a Bearer token. Workspace data remains in the Sonar account, while the package itself does not store data on disk.

The unauthenticated free mode covers selected tools and applies per-IP limits: the listed free tools share a 30-request daily allowance, while keyword metrics permits up to five keywords per day. An API key is needed for higher limits, tracking, rankings, competitor data, and other authenticated features. Workspace reads require an Indie plan or active trial. Workspace writes additionally require an API key with the `write` scope. Portfolio reporting requires an Agency plan.

## Setup and configuration

Install the server with `npx -y @sonarapp/mcp` and register that command in an MCP client. The README provides configurations for Claude Desktop, Claude Code, Cursor, Cline, and other MCP clients. The `SONAR_API_KEY` variable is optional for free mode and should contain a Sonar key when authenticated features are needed. `SONAR_API_URL` can override the default `https://trysonar.app` endpoint for staging or self-hosted deployments.

For the trysonar/mcp MCP server, a client configuration normally supplies the command, package argument, and an environment block. If a configured key is not detected, the server continues in free mode rather than treating the missing variable as a startup failure. API keys and plan access are managed through Sonar's developer service.

## Tools and capabilities

- Inspect app metadata, ratings, reviews, categories, prices, and Android installs.
- Search store listings and return results in store ranking order.
- Audit listing factors such as title length, keyword use, screenshots, and ratings.
- Compare keyword difficulty, popularity, related terms, and autocomplete suggestions.
- Filter and sort reviews for sentiment or feature-request research.
- Track daily keyword ranks and review changes for workspace apps.
- Analyze competitor keyword coverage and identify missing or winnable terms.
- Monitor alerts for ranking, rating, review, and competitor changes.

The trysonar/mcp MCP server also exposes cursor-paginated workspace results for several listing and history tools. Some dashboard-style responses summarize data already computed by Sonar, which can reduce the need for an agent to assemble metrics from individual calls.

## Limitations and notes

Free access is rate-limited and does not provide the full workspace feature set. Plan restrictions produce access errors when an operation is unavailable. Write calls mutate the Sonar workspace, so they should be used only when the agent has permission to change tracked products, competitors, keywords, or notes.

Chart movement is empty the first time a chart is requested because no prior snapshot exists. Alert events are generated only for enabled alert rules and detection runs once daily. Keyword ranking history requires the keyword to be tracked in the relevant workspace. The package itself is MIT licensed, while Sonar account data and API usage remain subject to Sonar's service terms and privacy policy.

_Full upstream README: https://allmcps.com/mcp/trysonar-mcp/readme_