Looker MCP Server
Related Servers
Alternatives to Looker MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to retrieve governed business metric definitions and compiled SQL through MCP-style tools, so they can query consistently under their own read-only roles without guessing joins or metric logic.MIT
- AlicenseNot gradedqualityCmaintenanceProvides an OAuth-protected, scoped, and audited MCP server that lets AI assistants safely query business data through a fixed set of tools without direct database access.1MIT
- AlicenseBqualityDmaintenanceEnables LLM applications to query Google Analytics 4 data through standard MCP interfaces, supporting real-time data, custom reports, and metadata discovery.5107 npm1MIT
- AlicenseBqualityNot gradedmaintenanceEnables AI assistants to interact with and manage Google Cloud Platform resources including Artifact Registry, BigQuery, Cloud Build, Compute Engine, Cloud Run, Cloud Storage, and monitoring services through a standardized MCP interface.1MIT
- AlicenseAqualityDmaintenanceEnables LLM applications to query and analyze Google Analytics 4 data through standard MCP interfaces, supporting service account and OAuth2 authentication.524 npmMIT
- AlicenseBqualityBmaintenanceEnables MCP hosts like ChatGPT and Claude to query data platform metadata, explore schemas and tables, inspect SQL explain plans, and monitor DAG and ETL status through standardized tools.21MIT
TDQS
Scored across 33 tools
Each tool targets a distinct action and resource (dashboard, look, query, explore, model, database, health, content, user). Even similar-sounding tools like query and run_query have clear differences: query requires a new definition, run_query uses an existing ID. No two tools are ambiguous.
The vast majority follow a consistent verb_noun pattern (e.g., list_models, create_dashboard, run_look). Minor exceptions include the bare verb 'query' and the single-word 'whoami', but these are negligible and do not hinder readability.
With 33 tools, the server exceeds the calibration threshold for 'too many' (>25). While the broad scope may justify a large surface, the number feels heavy and could overwhelm an agent, especially when many tools are for metadata exploration that might be consolidated.
The surface covers all major Looker workflows: CRUD for dashboards and looks, query execution, exploring models/explores, database metadata, health checks, and content validation. Minor gaps like missing update/delete for dashboard elements and lack of user management are acceptable given the server's focus.