Mode Analytics MCP Server
Related Servers
Alternatives to Mode Analytics MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceProvides AI assistants direct access to Looker through a standard MCP interface, enabling querying the semantic model, managing content, editing LookML, and administering users.33147 PyPI1Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables Claude and other MCP clients to securely read GA4 accounts, properties, reports, conversions, revenue, funnels, and realtime activity through Google's Analytics APIs. It supports guided setup, multiple authentication methods, and read-only querying of analytics data.MIT
- AlicenseAqualityBmaintenanceConnects Google Analytics 4 data to Claude, Cursor and other MCP clients, enabling natural language queries of website traffic, user behavior, and analytics data with access to 200+ GA4 dimensions and metrics.121,117 PyPI244MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to query live schema, lineage, and query-context across data warehouses, dbt projects, orchestration systems, and BI tools via MCP tools.Apache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables governed, read-only SQL analytics, hybrid RAG knowledge search, financial metric calculation, and database schema introspection through MCP, with role-based access control, audit logging, and AI observability.-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with the Metabase analytics platform, including dashboards, cards, databases, tables, collections, and query execution through a set of MCP tools.285 npmMIT
TDQS
Scored across 13 tools
Each tool targets a distinct resource and action: reports (create/get/update/archive/unarchive/list/search), queries (add/update), and read-only listings (spaces, data sources, runs, run results). The archive/unarchive pair and list_reports vs search_reports are clearly distinguished by scope and description, leaving no real overlap.
All 13 tools follow a strict snake_case verb_noun convention (create_report, update_query, list_spaces, get_run_results, etc.), including consistent use of the archive/unarchive antonym pair. No mixing of styles or verb conventions.
At 13 tools, the set is well-scoped for a report/query management domain, with each tool earning its place and no redundant operations. It stays comfortably within the ideal 3-15 range.
Report lifecycle is well covered (create, get, update, list, search, archive, unarchive), plus query add/update and run inspection. Minor gaps remain: there is no delete_query to remove a query from a report, and no tool to trigger a report run even though run-result and run-list tools exist.