Unilytics MCP Server
OfficialRelated Servers
Alternatives to Unilytics MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceMCP server for Google Search Console. 21 tools for search analytics, keyword opportunities, URL inspection, sitemaps, indexing, and property management.1MIT
- AlicenseBqualityBmaintenanceSEO audit and Google Search Console MCP server with 23 tools. Search analytics, URL inspection, Indexing API, Core Web Vitals (CrUX), striking distance keywords, keyword cannibalization detection, branded query analysis, and automated site audits.302MIT
- AlicenseBqualityAmaintenanceMCP server providing 32 tools for Google Search Console and Google Analytics 4, enabling search analytics, URL inspection, indexing, and cross-platform analysis via natural language.4310MIT
- AlicenseAqualityDmaintenanceAn MCP server that provides a suite of SEO analysis tools for auditing meta tags, headings, links, keyword density, page speed, and sitemaps without requiring external API keys.625 npm1MIT
- AlicenseBqualityDmaintenanceAn MCP server that gives AI assistants 23 SEO tools for rank tracking, Google Analytics, site audits, keyword research, competitive analysis, and more, accessible through natural language.2510MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides SEO analysis tools including backlink analysis, keyword research, and traffic estimation using Ahrefs data, with CAPTCHA solving and caching.MIT
TDQS
Scored across 72 tools
Several tools overlap in purpose: site_map and aeo_site_pages both discover site URLs; serp_results and aeo_serp_urls both fetch Google results; content_scrape, js_scrape, batch_scrape, and site_crawl have overlapping scraping functions; the many aeo_* tools are similarly named and hard to distinguish. Descriptions help some, but the boundaries between tools like aeo_cluster_by_urls vs aeo_cluster_prompts or kb_write_text vs kb_add_file are not immediately clear.
Tool names mix consistent verb_noun patterns (list_skills, get_skill, create_skill) with prefixed groups (aeo_*, kb_*, seo_*) and standalone tools that deviate from the pattern (web_research_tool, page_screenshot, site_map, google_trends, social_profile). The prefixes are internally consistent, but the overall set has no single naming convention, making it harder to predict tool names.
With 72 tools, the server has an extreme number of tools, far exceeding the 50+ threshold for a coherent set. While the scope is broad (SEO, content, ads, analytics, project management, skills, knowledge bases), the sheer volume makes it unwieldy and likely to confuse agents.
The tool surface covers a wide range of marketing and SEO operations, including skills CRUD, scraping, SERP analysis, ad libraries, analytics, and knowledge base management. However, there are notable gaps: projects have create but no update or delete, folders lack delete/update operations, and there is no way to remove tracked keywords, competitors, prompts, or locations. These missing lifecycle operations create dead ends for some workflows.