DataDive MCP
OfficialRelated Servers
Alternatives to DataDive MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP server that wraps Nightjar's analytics API, enabling Claude Code to query events, funnels, dashboards, and metrics through natural language.-
- AlicenseAqualityCmaintenanceMCP server for Claude that connects to MySQL, MariaDB, and SQLite databases. Query your databases using natural language.3132 PyPIMIT
- AlicenseAqualityCmaintenanceMCP Server for the Notion API, enabling Claude to interact with Notion workspaces.313,089 npm925MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that allows Claude and other AI assistants to interact with the YouTube API, providing tools to search videos/channels and retrieve detailed information about them.1MIT

@krovacloud/mcpofficial
AlicenseAqualityBmaintenanceMCP server for interacting with the Krova Cloud API, enabling AI assistants like Claude to manage cloud resources.37MIT- FlicenseNot gradedqualityDmaintenanceAn MCP server that connects Claude Desktop to PoetryQuill's live Supabase database. Ask Claude natural language questions about your platform data.-
TDQS
Scored across 56 tools
Even in dense clusters (SQP vs PPC vs ranking data on a Rank Radar; MKL vs Outlier vs Residue keywords; labels vs spaces) the descriptions state explicitly which tool to use and cross-reference the alternatives. Near-pairs like add_niche_labels/add_niche_spaces and pause_rank_radar/delete_rank_radar are documented with the exact semantic difference ('archive' = pause). A few pairs still require careful reading (run_fast_keywords vs refresh_fast_keywords, create_niche_dive vs create_niche_dive_from_competitors_list), so not perfect, but boundaries are clear.
Overwhelmingly consistent snake_case verb_noun: list_*, get_*, create_*, add_*, remove_*, pause_*, resume_*, delete_*. Minor deviations: redive_niche (object-first) sits awkwardly beside create_niche_dive, and run_/refresh_fast_keywords use different verbs for the same resource family than the niche equivalents.
56 tools is a very large surface, well beyond the 3-15 sweet spot, and several groups could be consolidated (the six rank-radar tag tools, the four add/remove label/space tools). The domain is genuinely broad (niches, dives, keywords, rank radars, PPC, inventory, alerts, quota, copywriting), which explains the size, but the sprawl still raises selection cost for an agent.
Coverage across the analytics lifecycle is strong: niche creation/re-dive/deletion, keyword list curation with exclusions, rank-radar creation, pause/resume/delete, tagging, PPC/SQP/ranking data, inventory, catalog, alerts and quota. Gaps remain: no update/rename for a niche, alerts are read-only (no resolve/dismiss tool), and inventory is single-ASIN only with no way to list at-risk ASINs.