In-depth architectural comparison of the Google Search Console MCP and Trysonar MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Google Search Console MCP
Marketing · Local stdio
Quality: 63/100 (Good) | Auth: OAuth 2.0
Trysonar MCP
Marketing · Local stdio
Quality: 63/100 (Good) | Auth: API Key required
Verdict Summary: Choose Google Search Console MCP if you need specialized Marketing tools running via a local process. Choose Trysonar MCP if your workspace requires Marketing integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Google Search Console MCP when:
You need dedicated capabilities in the Marketing domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (Free / Open Source).
You have access to required keys: GSC_CLIENT_ID, GSC_CLIENT_SECRET, GSC_REFRESH_TOKEN.
List every property the authenticated account can read.
Call this first when a property string fails: it returns the exact `site_url`
values the other tools expect, and whether each one is a domain property
(`sc-domain:example.com`) or a URL-prefix property.
gsc_site_details
Permission level and property type for one property.
gsc_query
Query the Search Analytics report: clicks, impressions, CTR, position.
This is the general-purpose tool. With no dates it covers the last 28 days
ending today (UTC), with data_state=all so today's partial data is included,
matching what the Search Console UI shows.
Example: site_url="sc-domain:example.com", dimensions="query,page",
period="last_28_days", row_limit=100.
Returns a `# meta ...` line then a TSV table, or JSON with `meta` and `rows`.
The meta names the exact range, the row count, whether more rows exist and
the `start_row` to pass next.
gsc_performance_overview
Site totals for a period, compared with the preceding one by default.
Start here: it answers "is the site up or down" in one call, with the
percentage change on every metric. `position_delta` is negative when the
average position improves.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Google Search Console MCP is categorized under Marketing and uses a local stdio subprocess. In contrast, Trysonar MCP belongs to Marketing using local stdio subprocess. Select Google Search Console MCP when you need capabilities focused on marketing and Trysonar MCP when you require tools for marketing.
Join two periods on one dimension and rank the rows by click delta.
Answers "what changed" without the model diffing two tables by hand. Rows
present in only one period are kept, with zeros on the missing side; the
biggest movers in both directions are returned, worst first. The meta counts
how many rows gained and how many lost clicks.
gsc_quick_wins
Queries close enough to the top that a push would pay off.
Ranked by the clicks each query would gain at `target_position`, not by
impressions: a big query already near its ceiling is not an opportunity.
The meta reports the thresholds that were applied.
gsc_ctr_gaps
Rows that rank well but are clicked far less than their position implies.
The snippet, not the ranking, is the problem, which makes these the
cheapest fixes available. `expected_ctr` is what a result at that position
normally earns.
gsc_cannibalization
Queries where several pages of the site compete for the same result.
Reads one page of up to 25,000 query/page pairs; on a very large property
the tail is cut off, and the meta says how many pairs were analysed.
Each row lists the competing pages with their own clicks and positions.
gsc_traffic_drops
Pages that lost clicks against the baseline, each with a likely cause.
`diagnosis` separates a ranking loss from falling demand, a collapsed CTR
and a page that disappeared: the four need different fixes, and the raw
numbers for both periods are in the row so the call can be checked.
gsc_content_decay
Pages sliding down month after month.
A period comparison hides this: a page that halves over six months never
shows a sharp drop in any single month-on-month check. One query per month
runs in parallel.
gsc_alerts
What changed sharply enough to be worth a message today.
Compares the last `window_days` against the window before it across both
queries and pages, and returns only movements past the alerting rules:
lost positions, collapsed CTR, dropped or vanished pages.
gsc_portfolio
Every accessible property at a glance, ranked worst first.
One row per property with the current period, the previous one and a health
flag: critical below -30% clicks, warning below -15%. Use it to decide which
property to look at before running anything else.
+5 more tools listed on main page
Trysonar MCP Tools (53)
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. A keyword the API cannot compute right away comes back as `pending` (queued on the scrape fleet, not charged) — this tool already waits and re-checks briefly; if it is still pending, call again after `retry_after_seconds`.
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).
Google Search Console MCP server: query performance data, inspect URLs, check indexing, and generate brandable HTML SEO audit reports with a 30/60/90-day roadmap. Read-only OAuth scope, installable via uvx mcp-google-search-console.
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