DataDive MCP
OfficialRelated Servers
Alternatives to DataDive MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceMCP 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.3MIT
- AlicenseAqualityBmaintenanceMCP Server for the Notion API, enabling Claude to interact with Notion workspaces.311,289 npm919MIT
- 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.10 npm1MIT

@krovacloud/mcpofficial
AlicenseAqualityAmaintenanceMCP 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 32 tools
Tools mostly target distinct resources and actions, but there is some potential for confusion among the three Rank Radar data tools (data, sqp, ppc) and between pause_rank_radar and pause_rank_radar_search_terms. Detailed descriptions help differentiate them, though an agent must read carefully. Overall, boundaries are clear enough for reliable selection.
All tool names follow a consistent snake_case verb_noun pattern (list_, get_, create_, pause_, resume_, delete_, add_, generate_). The verbs are predictable and the names are descriptive. No mixing of conventions or styles.
32 tools is on the heavy side, exceeding the typical 3-15 range for a well-scoped server. However, the server covers a broad domain (niches, rank radars, seller data, alerts, listing copy, quota), so many tools are justified. Still, the count may overwhelm agents and some consolidation could be possible.
The surface covers core CRUD/lifecycle for niches, rank radars, dives, seller data, and listing copy generation. Minor gaps exist: alerts can be listed but not resolved, and generated listing copy cannot be published directly. These are workable around but leave slight dead ends.