AlsoAsked MCP Server
Related Servers
Alternatives to AlsoAsked MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceConnects Claude to Google Search Console, GA4, Bing Webmaster Tools, IndexNow, PageSpeed Insights, AdSense and Google Ads Keyword Planner, plus live technical SEO audits of pages and sitemaps. Users ask plain-language questions about traffic drops, index status, canonicals, AI referral traffic and keyword volumes, and answers are pulled live from the APIs in real time.2818 npmMIT
- AlicenseAqualityBmaintenanceEnables Claude Code and Cursor to fetch live trending-search, interest-over-time, and related-query data and attach it to prompts for context-aware answers.4MIT
- AlicenseAqualityBmaintenanceLets you ask Claude questions about your Google Search Console data and get real analysis, not raw API rows. Provides 20 tools for analysis, indexing, and safety.292,471 npm192Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables Claude to query Google Search Console, Google Ads, and Bing Webmaster Tools in read-only mode, returning SEO and SEA metrics and comparisons through natural-language requests without exporting CSVs.MIT
- AlicenseNot gradedqualityCmaintenanceEnables querying Google Search Console data, including search analytics, indexing status, and sitemap management, through natural language conversations with Claude.101 npm6MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude, ChatGPT, Cursor, and other MCP clients to query Google Search Console, GA4, PageSpeed Insights, and live SERPs through 38 read-only SEO tools for quick wins, content decay, indexing, Core Web Vitals, AI traffic, and conversion analysis.2MIT
TDQS
Scored across 3 tools
The tools have overlapping purposes, as both 'search_people_also_ask' and 'search_single_term' appear to retrieve PAA questions, with the latter described as a 'convenience method' for single terms. This creates ambiguity about when to use each, though the descriptions provide some differentiation. The 'get_account_info' tool is clearly distinct, focusing on account metadata.
All tool names follow a consistent verb_noun pattern with snake_case, such as 'get_account_info', 'search_people_also_ask', and 'search_single_term'. This uniformity makes the tool set predictable and easy to parse, with no deviations in naming conventions.
With only 3 tools, the set feels thin for a server focused on PAA search functionality, as it lacks operations like filtering, saving results, or managing search history. The count is too low to adequately cover the domain, making it seem incomplete for practical use.
The tool set is severely incomplete for a PAA search domain, offering only basic search and account info retrieval. Missing are essential operations such as updating search parameters, deleting or exporting results, or handling batch searches, which limits agent workflows and creates dead ends.