VisiblyAI MCP Server
Related Servers
Alternatives to VisiblyAI MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceTurn Claude Code into your SEO manager with keyword research, content pipeline that ships pull requests, rank tracking, and a dashboard.2 npm91AGPL 3.0
- 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.2848 npmMIT
- AlicenseCqualityCmaintenanceEnables Claude Code to read Google Search Console and GA4 data locally with read-only access, and provides combined SEO analysis tools for comparing datasets and identifying opportunities.20MIT

DataForSEO MCP Serverofficial
AlicenseBqualityBmaintenanceA Model Context Protocol server that enables Claude to interact with DataForSEO APIs, allowing access to SEO data including SERPs, keyword research, on-page metrics, and domain analytics.1712,789 npm255Apache 2.0- AlicenseNot gradedqualityAmaintenanceEnables Claude to operate a local SEO tool through 50 MCP tools for crawling websites, listing and prioritizing issues, checking on-page optimization, measuring Core Web Vitals, researching keywords, viewing ranking data, and generating PDF reports.MIT
- AlicenseNot gradedqualityDmaintenanceEnables natural language analysis of Google Search Console data through Claude, with pre-built tools for quick wins, cannibalization detection, content decay, and more.Apache 2.0
TDQS
Scored across 84 tools
Many tools have overlapping purposes: score_text, optimize_content_draft, and run_content_optimizer all evaluate/improve content; classify_keywords_simple and classify_keywords_advanced do nearly the same thing; get_content_query, list_content_queries, and get_content_status all read query state; seo_agent and seo_workflow both run multi-step SEO tasks. An agent would struggle to pick the right one without deep inspection.
Naming mixes verb_noun (list_articles, create_content_query), noun-only (recall, remember, seo_checklist), and noun_verb (score_text, check_serp, query_search_console) patterns. Similar functions get different styles, e.g. optimize_content_draft vs run_content_optimizer, and get_gsc_clusters vs get_content_query, making the surface hard to predict.
84 tools is far beyond a reasonable scoped surface for an SEO/content platform. The set feels like several products bolted together (scoring, CMS, optimizer, GSC, analytics, SERP data, agents, memory, meeting import) with many redundant variants, guaranteeing confusion and high selection cost.
The surface covers most lifecycle operations: content queries (create/read/save/generate/optimize), articles (create/edit/status/publish/backup/restore), CMS connections (CRUD/test), optimizer suggestions (list/approve/reject/undo), and analytics. Minor gaps exist, such as no delete_article or bulk operations, but core workflows are well supported.