Context7
Up-to-date docs for AI agents
Beschreibung vom Entwickler (englisches Original)
ASO tools for AI agents: keyword research, rank tracking, competitor analysis (iOS & Android).
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
SONAR_API_KEY, SONAR_API_URL, AuthorizationAls geheim markierte Werte sind Schlüssel zu deinem Konto. Gib sie nie weiter und füge sie nie in einen Chat ein.
Du brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Diese Adresse braucht einen Schlüssel in einem Header der Anfrage, und das Menü zum Hinzufügen von Connectors kann ihn nicht setzen. Nutze stattdessen Claude Code, Cursor oder VS Code.
Öffne Claude Desktop → Settings → Developer → Edit Config und füge dies in claude_desktop_config.json ein
{
"mcpServers": {
"sonar": {
"command": "npx",
"args": [
"-y",
"@sonarapp/mcp"
],
"env": {
"SONAR_API_KEY": "your-value",
"SONAR_API_URL": "your-value"
}
}
}
}Führe das in deinem Terminal aus
claude mcp add --transport http sonar https://trysonar.app/mcp --header 'Authorization: your-value'claude mcp add sonar --env SONAR_API_KEY=your-value --env SONAR_API_URL=your-value -- npx -y @sonarapp/mcpTrag die leeren Werte ein, bevor du ihn startest.
In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"sonar": {
"url": "https://trysonar.app/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"sonar": {
"command": "npx",
"args": [
"-y",
"@sonarapp/mcp"
],
"env": {
"SONAR_API_KEY": "your-value",
"SONAR_API_URL": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"sonar": {
"type": "http",
"url": "https://trysonar.app/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"sonar": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@sonarapp/mcp"
],
"env": {
"SONAR_API_KEY": "your-value",
"SONAR_API_URL": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
Diese Adresse braucht einen Schlüssel in einem Header der Anfrage, und das Menü zum Hinzufügen von Connectors kann ihn nicht setzen. Nutze stattdessen Claude Code, Cursor oder VS Code.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
SONAR_API_URL envAuthorization geheim erforderlich HTTP headerDiese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Die Tool-Liste dieses Servers haben wir noch nicht gelesen; wir prüfen die Endpunkte reihum.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 6. Nov. 2026
Der Registry-Name wurde über die Domain trysonar.app bestätigt (die Registry prüft, wem die Domain gehört)
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Noch nicht geprüft; wir prüfen die Endpunkte reihum
Noch nicht geprüft; wir prüfen die Endpunkte reihum
Noch nicht geprüft; wir lesen die Tool-Liste, wenn wir den Endpunkt prüfen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Das musst du eintragen: SONAR_API_KEY, Authorization
Beides geht: Installiere ihn auf deinem Computer oder verbinde dich mit der Cloud-Version.
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.7.0) kam vor 3 Monaten in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Er verbindet sich per URL, also funktionieren auch Apps, die Remote-MCP-Server akzeptieren, zum Beispiel ChatGPT im Entwicklermodus.
In derselben Kategorie: Context7, Codebase Memory, Exa
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
Up-to-date docs for AI agents
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
The official Sonar MCP server — App Store Optimization tools for AI agents.
For the hosted Grok Build and Cursor marketplace plugin, see plugin setup, authentication, and permissions.
Lets Claude Desktop, Claude Code, Cursor, Cline, and any Model Context Protocol-compatible client look up apps, research keywords, audit ASO, mine reviews, and estimate revenue across the iOS App Store and Google Play. Powered by Sonar.
55 tools covering the whole Sonar REST API, grouped by what they need.
| Tool | What it does | Works without a key | |-|-|-| | sonar_app_lookup | Look up app metadata by store ID | Yes | | sonar_app_search | Search apps by keyword (returns store ranking order) | Yes | | sonar_app_aso_score | ASO audit score (0-100) with itemized checks | Yes | | sonar_app_extract_keywords | Extract target keywords from an app's listing | Yes | | sonar_app_reviews | Fetch reviews with rating filters and sort options | — | | sonar_app_revenue | Estimate monthly revenue with a confidence grade | — | | sonar_keyword_search | Keyword research (difficulty, popularity, related terms) | — | | sonar_keyword_metrics | Difficulty + popularity for specific keywords (up to 25 per call) | Yes (5 keywords/day) | | sonar_keyword_suggestions | Autocomplete suggestions from the store | Yes | | sonar_top_charts | Top free/paid/grossing chart with day-over-day movement | Yes |
Stateless tools work on any plan with credits (API Credits, Indie or Agency), for both iOS and Android. The ones marked "Yes" also run keyless on the free tier (see "Try it free" below).
| Tool | What it does | |-|-| | sonar_list_products | List your products with their linked store versions and competitor counts | | sonar_list_apps | List your tracked apps with latest snapshots (rating, reviews, installs) | | sonar_get_app | App detail + up to 90 days of snapshot history | | sonar_app_overview | Dashboard scoreboard for an app: visibility, share of voice, movement, opportunities | | sonar_app_keywords | Keywords tracked for an app, with difficulty, popularity, notes and stars | | sonar_app_rankings | Daily rank history for an app's tracked keywords | | sonar_app_changes | Detected releases, metadata edits, screenshot/price/category changes | | sonar_keyword_rankings | SERP history for a tracked keyword (who ranked, when) | | sonar_discovered_keywords | Untracked keywords Sonar discovered for an app, sorted by opportunity | | sonar_competitor_keywords | Keywords a competitor ranks for + gap analysis vs your app | | sonar_competitor_landscape | Gaps, threats and leads vs all your competitors + latest AI insight | | sonar_review_insights | Latest AI review analysis: praise/complaint themes, quotes, trends | | sonar_list_alerts | List your alert rules (type, scope, threshold, enabled) | | sonar_alert_events | Detected alert events (rank moves, rating drops, review spikes), newest first |
Workspace reads require an Indie plan or higher (an active trial counts); the default read-scope key is enough.
| Tool | What it does | |-|-| | sonar_portfolio | Portfolio rollup: per-app KPIs, biggest movers, needs-attention list, top opportunities | | sonar_app_sales | App Store Connect sales: downloads, redownloads, IAP units, approximate proceeds | | sonar_app_engagement | App Store Connect funnel: impressions, page views, downloads, sources, sessions |
These require the Agency plan (an Agency trial counts) and return 403 on other plans. sonar_app_sales and sonar_app_engagement are iOS-only and also need an App Store Connect connection at trysonar.app/settings/connections; engagement data needs an Admin-role App Store Connect key.
| Tool | What it does | |-|-| | sonar_create_product | Create a product in your Sonar workspace and start tracking its app(s) | | sonar_track_app | Link the second-store version (iOS ↔ Android) of an existing product | | sonar_track_competitor | Add a competitor app under a product | | sonar_remove_competitor | Remove a competitor from a product | | sonar_delete_product | Delete a product and untrack its apps | | sonar_untrack_app | Untrack an app and its tracking data | | sonar_track_keywords | Start daily rank tracking for keywords on an app (bulk, idempotent) | | sonar_update_keyword_note | Set or clear the note on a tracked keyword | | sonar_star_keyword | Star or unstar a tracked keyword (mark it as a target) | | sonar_delete_tracked_keyword | Stop tracking one keyword/app pair | | sonar_untrack_keywords | Bulk-untrack an app's keywords (selected IDs or all) | | sonar_scan_competitor | Run an AI keyword discovery scan on a competitor (read results with sonar_competitor_keywords) | | sonar_analyze_competitors | Generate a fresh AI competitive insight for one of your apps (7-day cooldown) | | sonar_generate_review_insights | Generate a fresh AI review analysis for a tracked app (90-day cooldown) | | sonar_set_alert | Create or update an alert rule | | sonar_delete_alert | Delete an alert rule |
Write tools mutate your workspace and require an Indie plan or higher (an active trial counts) plus either an OAuth sign-in on the hosted endpoint (which carries write access) or an API key created with the `write` scope. The two AI generation tools, sonar_analyze_competitors and sonar_generate_review_insights, need a paid plan and are not available during the trial. The server enforces all of this — without it, calls return a 403 explaining what to fix.
Together these close the loop for agents: set up tracking with the write tools, then read back rankings, changes, and gap analyses with the workspace tools.
| Tool | What it does | Scope | |-|-|-| | sonar_screenshot_layout_guide | Layout-format reference; read it once before authoring layouts | none | | sonar_screenshot_devices | Supported device sizes and their canvas dimensions | read | | sonar_list_screenshot_sets | A product's screenshot sets (metadata only) | read | | sonar_get_screenshot_set | A full set: every screen's layout plus translation overrides | read | | sonar_create_screenshot_set | Create a screenshot set for a product | write | | sonar_update_screenshot_set | Rename a set, replace its locales, or reorder its screens | write | | sonar_delete_screenshot_set | Delete a set and everything in it | write | | sonar_add_screenshot | Append a screen to a set | write | | sonar_update_screenshot | Replace one screen's layout | write | | sonar_delete_screenshot | Delete one screen (a set keeps at least one) | write | | sonar_set_screenshot_translations | Write a locale's translation overrides | write | | sonar_export_screenshots | Render store-ready PNGs into one local ZIP per locale | read |
Agents author screenshot sets as layout JSON; humans review and fine-tune the same sets in the Screenshot Studio. The layout guide is embedded in the server and needs no key. sonar_export_screenshots writes files on the machine running the server, so it's available over stdio only, not on the hosted endpoint.
OAuth-capable MCP clients (Claude Code, claude.ai custom connectors) can skip both the npm install and the API key entirely:
claude mcp add --transport http sonar https://trysonar.app/mcp
The first tool call that needs your account opens a browser sign-in — approve it with your Sonar login and the agent has full access to the workspace you own (read + write). Clients without OAuth support can pass an API key instead: --header "Authorization: Bearer aso_...".
Submit https://trysonar.app/mcp/chatgpt to OpenAI. This endpoint returns tool-level sign-in challenges; /mcp retains HTTP 401 challenges for Claude and other MCP clients. Both advertise OAuth per tool. Anonymous store lookups can run without linking; workspace tools return a native sign-in challenge when authorization is missing or expired. Connect an existing Sonar account and approve access to the workspace you own. Existing account permissions and entitlements apply.
The ChatGPT endpoint requires resource-bound JWT access tokens for its canonical /mcp/chatgpt audience; the existing /mcp endpoint retains Clerk opaque-token support. Provider configuration and an end-to-end login must be verified before submitting the ChatGPT endpoint.
The hosted catalog excludes sonar_export_screenshots, which writes ZIP files to the local MCP host. It remains available over stdio. A native directory listing requires separate OpenAI review and publication; hosting an MCP endpoint does not itself create a listing.
The server runs without a key in free mode: sonar_app_search, sonar_app_lookup, sonar_app_aso_score, sonar_app_extract_keywords, sonar_keyword_suggestions, and sonar_top_charts share a free allowance of 30 requests/day per IP, and sonar_keyword_metrics (keyword difficulty + popularity) gets 5 keywords/day. Just install it with no env block and ask your agent about ASO. When you hit the limit, the error tells you how to sign up.
For everything else (tracking, rankings, competitors, higher limits) you'll need a Sonar API key — get one at trysonar.app/developers.
The cheapest path is prepaid API credits — packs from $10 (1,000 credits), with 50 free credits on signup and no subscription. Built specifically for this use case. See pricing.
Add to your config file (~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows):
{
"mcpServers": { "sonar": { "command": "npx", "args": ["-y", "@sonarapp/mcp"], "env": { "SONAR_API_KEY": "aso_your_key_here" } } } }
Restart Claude Desktop. The sonar_* tools will appear in the tool picker.
claude mcp add sonar -e SONAR_API_KEY=aso_your_key_here -- npx -y @sonarapp/mcp
Add to ~/.cursor/mcp.json (or your project's .cursor/mcp.json):
{
"mcpServers": { "sonar": { "command": "npx", "args": ["-y", "@sonarapp/mcp"], "env": { "SONAR_API_KEY": "aso_your_key_here" } } } }
Most clients use the same command + args + env shape as above. Point the command at npx -y @sonarapp/mcp and pass SONAR_API_KEY in the env.
| Variable | Required | Default | Description | |-|-|-|-| | SONAR_API_KEY | no (free mode without it) | — | Your Sonar API key (aso_...) | | SONAR_API_URL | no | https://api.trysonar.app | Override the API base URL (only used for self-hosting / staging) |
"Use Sonar to look up Spotify on iOS in the US store and report its rating, review count, and category."
"Run an ASO audit on
com.duolingoon Android and tell me what to fix."
"Research the keyword 'habit tracker' on iOS — give me difficulty, popularity, and 5 related terms with lower difficulty I should consider."
"Pull the 50 most recent 1- and 2-star reviews of
1517783697on iOS US and group complaints by theme."
"
Nur der Anfang wird gezeigt; den Rest findest du im Repo