Trysonar MCP

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.