datastudio-mcp
Related Servers
Alternatives to datastudio-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to build and modify reports, connect BigQuery, Google Sheets, and GA4 data, arrange charts and pages, check for data errors, and export or restore versions by using Playwright to call the editor's internal APIs instead of simulating clicks.MIT
- AlicenseAqualityBmaintenanceEnables an AI assistant to explore BigQuery datasets, run read-only queries and create views, then build and refine dashboards in the Looker Studio editor — charts, text, shapes, themes and exact layouts — verifying the result with screenshots. Write actions are gated behind explicit configuration, dry-run and audit logging.114MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude Code or Codex to edit the Power BI Desktop report you currently have open, applying changes live on the canvas without touching project files or losing unsaved work. Agents can build pages, write and verify DAX measures, add date tables, and style visuals from a design system.MIT
- AlicenseBqualityBmaintenanceEnables AI agents to drive a persistent Chrome session that stays signed in to your own Google account, with tools for navigation, snapshots, clicking, typing, keystrokes, screenshots, JavaScript evaluation, and lifecycle or re-login control. It also exports every row behind a Looker Studio report to CSV and checks whether the session is still healthy.14MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to create, format, and verify Google Sheets with native tables, themes, validation, linting, rendering, and safeguards for human-edited spreadsheets.11 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables 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.4MIT
TDQS
Scored across 109 tools
The tool set has many closely related operations across reports, pages, components, filters, blends, and datasources, and several tools overlap in apparent purpose (e.g. report_patch vs components_patch vs settings_set, and the many filter-binding tools). The descriptions are unusually detailed and usually clarify scope, but with 109 tools an agent can still easily misselect among near-neighbors.
Most names follow a domain_action pattern (report_publish, page_get, components_create), but singular/plural prefixes are inconsistent (datasource_get vs datasources_list, filter_validate vs filters_list, blend_get vs blends_list). Some names are noun-only or action-only (native_catalog, report_audit, visibility_set, theme_from_image), so the convention is readable but not uniform.
109 tools is far beyond a well-scoped set and is an extreme mismatch even for a complex report editor. The surface is fragmented into many highly specialized operations, making discovery and correct selection costly.
The surface covers a very broad lifecycle: reports, pages, components, datasources, filters, blends, controls, publishing, revisions, themes, images, and auditing. Minor gaps remain, such as report creation/deletion, report-level sharing, and datasource deletion or non-BigQuery connector creation.