App Store Tracker vs Seo Performance MCP | AllMCPs
Side-by-Side Model Context Protocol Comparison
App Store Tracker vs Seo Performance MCP
In-depth architectural comparison of the App Store Tracker and Seo Performance 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
App Store Tracker
Marketing · Remote HTTP/SSE
Quality: 45/100 (Fair) | Auth: API Key required
Seo Performance MCP
Marketing · Local stdio
Quality: 60/100 (Good) | Auth: No auth required
Verdict Summary: Choose App Store Tracker if you need specialized Marketing tools running via a hosted cloud SSE transport. Choose Seo Performance 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?
A
Choose App Store Tracker when:
You need dedicated capabilities in the Marketing domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: API Key required (Freemium).
Independent iOS App Store tracker: daily top free charts in 114 storefronts and 22 categories, history since 2025-03-09, plus an MCP server for AI agents.
Post-publish SEO performance MCP that unifies Google Search Console, Matomo, GA4, Clarity, and AI-citation signals per URL and emits a verdict (refresh / expand / merge / kill / doubledown / hold) per post with reason codes.
No explicit tool names declared in metadata yet. Check project README on main listing page.
Seo Performance MCP Tools (9)
posts_list
Discover posts via an XML sitemap (POSTS_SITEMAP_URL or the sitemap_url arg), a JSON override list (POSTS_LIST), or - if configured - the Ghost Admin API. Pass an explicit urls[] to skip discovery entirely.
Returns metadata: url, title, published_at, age_days, tags. Filter by minimum age or published-after date.
When to use: discover which URLs are eligible for snapshot / verdict / cohort analysis. Works with any CMS that exposes a sitemap.
posts_snapshot
Pull a 30/60/90-day snapshot across every configured signal source for one post: GSC clicks/impressions/CTR/position + top queries, Matomo visits + dwell, GA4 pageviews, Clarity scroll/rage clicks, AI-citation counts.
Each source is best-effort: if its env vars are missing the field is omitted. Returns whatever is available.
Read-only. No third-party writes. Optionally persists to the local DuckDB cache when persist=true.
posts_decay_curve
Bucket GSC clicks/impressions/avg-position into ~weekly windows for the last N weeks (default 12) and classify the trend: decay / plateau / growth.
Underpins the verdict engine's decay rules. Read-only GSC query.
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).
App Store Tracker is categorized under Marketing and uses a remote streaming HTTP/SSE transport. In contrast, Seo Performance MCP belongs to Marketing using local stdio subprocess. Select App Store Tracker when you need capabilities focused on marketing and Seo Performance MCP when you require tools for marketing.
Run the rule-based verdict engine on a single post: combine snapshot + decay curve and emit a verdict with reason codes and a 0-1 confidence score.
Reason codes are deterministic. The mapping reasons -> verdict lives in src/verdict/rules.ts and can be inspected.
Reporting only - does NOT mutate anything. To act on the verdict, hand the brief to a writer or to an AI rewrite tool.
posts_refresh_brief
Produce a markdown brief for a human (or downstream LLM) editor: verdict + reasons + raw numbers + top queries + suggested actions.
Use this as the hand-off artefact when verdict is refresh / expand / merge / double_down.
cohort_report
Run the verdict engine across a cohort (filtered by tag and/or min-age) and return a ranked table sorted by verdict priority then confidence.
Practical use: 'which three posts should I refresh this week?' - the top three rows with verdict=refresh and highest confidence are the answer.
posts_cite_loss
Return the list of LLMs that previously cited this URL but no longer do, with the prior query and last-seen date. Optionally includes the URL that replaced ours.
Requires a configured citation-intelligence MCP endpoint (CITATION_INTELLIGENCE_URL). Otherwise returns an empty list.
gsc_quick_wins
Scan GSC for (page, query) pairs sitting in positions 5-15 with non-trivial impressions and a CTR below their position-expected curve. These are the fastest title-rewrite wins.
Returns top results sorted by impressions desc. Pure GSC pull - platform-agnostic.
bing_quick_wins
Scan Bing Webmaster Tools for queries sitting in positions 5-15 with non-trivial impressions. Bing's index backs Copilot, ChatGPT search, and Perplexity grounding, so a Bing rank gap is an LLM-citation gap.
Query-level only: Bing has no single page+query API, so - unlike gsc_quick_wins, which returns (page, query) pairs - these carry no url. Sorted by impressions desc.
Requires BING_WEBMASTER_API_KEY (Bing Webmaster Tools -> Settings -> API Access). Best-effort: returns config_missing if unset.