Skip to main content
Glama
JhostinAleck

looker-studio-mcp

by JhostinAleck
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to looker-studio-mcp

No user-submitted related servers found.

    Related Servers

    • bigquery-mcp

      vozzor
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to query and analyze Google BigQuery data, including schema browsing, running queries, and comparing datasets through natural language.
      MIT

    • BigQuery MCP Server

      pvoo
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLMs to explore BigQuery datasets and tables, run safe read-only queries, and optionally perform vector search using BigQuery embeddings.
      135 PyPI
      10
      MIT

    • dbt-agents

      the-datastrategist
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to inspect, query, test, and safely fix dbt projects and BigQuery warehouses under policy-enforced controls, with read-only direct queries and dbt-only allowlisted writes.
      Apache 2.0

    • google-marketing

      omarmfouad25
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI apps to plan, build, audit, and report on Google Ads, GA4, Search Console, and Tag Manager accounts through natural language. Accounts are read-only by default, and every change is validated in a preview, applied only after confirmation, logged, and reversible.
      MIT
    Deploy Server
    Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

    TDQS

    A3.6/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool targets a distinct resource+action: BigQuery querying (run_query, list_datasets, list_tables, describe_table) versus Looker Studio browsing (list_reports, list_report_pages, list_components, describe_component, screenshot_report), plus auth and link building. The parallel list/describe hierarchies are clearly separated by domain and no two tools overlap in purpose.

    Naming Consistency5/5

    All names use a consistent snake_case verb_noun pattern (list_reports, describe_component, run_query, build_report_link, check_auth). There are no mixed conventions or vague verbs, making the naming highly predictable.

    Tool Count5/5

    11 tools is well within the ideal range and each earns its place: reading BigQuery, reading reports/pages/components, auth checks, and link building. Nothing feels redundant or padded.

    Completeness2/5

    The surface is read-only yet descriptions reference editing operations that do not exist: describe_component tells you to learn the labels 'update_component' accepts, list_components says 'other component tools take' indexes, and screenshot_report is 'to check charts after editing'. Agents will hit dead ends because the referenced write/edit tools (e.g. update_component, add_component) are absent.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources