data_studio_ add_ membersGive people, groups or a domain a role on a report or data source (Google's addMembers).
Ask which dashboards anyone with the link can open, share a client report with a few emails, switch link sharing off, or build a report on a client's own data, from the AI client you already use.
PopMCPGoogle Data Studio
Every Data Studio API method, asset search and sharing, plus tools that find reports by name, check the sharing of many reports at once and build Linking API report links. Google now calls the product Data Studio again; links on either domain work.
13 tools in the full catalog: 7 read and 6 write. 13 load by default, and the rest are found with tool search.
data_studio_ add_ membersGive people, groups or a domain a role on a report or data source (Google's addMembers).
data_studio_ get_ permissionsWho has access to one report or data source: the members of each role (OWNER, EDITOR, VIEWER, LINK_VIEWER, LINK_EDITOR) and the etag.
data_studio_ revoke_ membersRemove people, groups or a domain from every role on a report or data source (Google's revokeAllPermissions).
data_studio_ set_ link_ sharingTurn link sharing off, or on for view or edit, for anyone or a domain.
data_studio_ share_ with_ peopleShare with people, groups or a domain as viewer or editor.
data_studio_ sharing_ auditCheck the sharing of many assets and flag link sharing and outsiders.
data_studio_ unshare_ with_ peopleRemove people, groups or a domain, saying who really had access.
data_studio_ update_ permissionsSet the members of one or more roles on a report or data source in one write (Google's permissions.patch).
data_studio_ find_ data_ sourcesFind data sources by name, owner or who they were shared with, with links.
data_studio_ find_ reportsFind reports by name, owner or who they were shared with, with links.
data_studio_ get_ assetOne report or data source by id or link: details and who has access, in words.
data_studio_ search_ assetsSearch the Data Studio reports or data sources the signed-in Google account can see, by title words or filters (owner:me, creator:me, to:/from:email).
data_studio_ build_ report_ linkBuild a Linking API link that creates a report from a template on the opener's data.
Authorize once, then an endpoint your client signs into. Nothing to deploy, and nothing to install on the Google Data Studio side.
Sign in with a Google Workspace or Cloud Identity account. Google only lets apps a Workspace admin has approved use Data Studio's API, so an admin first adds the client ID and the Data Studio scopes under domain-wide delegation in the Admin console. The connect form shows both.
1234567890-abc.apps.googleusercontent.com••••••••••••3f7ayour-google-data-studio-valueConnections start read-only. Once an owner allows writes, share_with_people, unshare_with_people and set_link_sharing change who can open a report as soon as the AI calls them. Google's API cannot read a report's charts or numbers, and cannot delete anything.
Drop the PopMCP URL into Claude, ChatGPT, Claude Code, Codex or any other supported client. It signs in through PopMCP with OAuth, so your Google Data Studio credential never leaves the server.
app.popmcp.com/mcpAsk for something harmless before the agent changes anything. Writes run as soon as it calls them, so confirm it reads the right account first.
Which of my Data Studio reports can anyone with the link open, and who outside the company has access?
data_studio_sharing_auditok
Then just ask for the work
“Which of my Data Studio reports can anyone with the link open, and who outside the company has access?”
“Find the Q3 client dashboard and share it with ana@client.com as a viewer”
“Turn link sharing off on every report the audit flags as open to anyone”
“Remove the freelancer's access from all of my reports”
“Build a report link from our SEO template for the client's Search Console property client.com”
One hosted endpoint, registered once per client. The same tools and the same permissions, whichever window the request comes from.
Add the PopMCP URL under Customize → Connectors and the tools appear in every chat.
The same endpoint, registered in the browser. Nothing to install on the machine you are working from.
Register PopMCP as a custom connector, then let ChatGPT read and update the account.
Wire the endpoint into Codex or the Codex CLI when a task needs live business context, not a fixture.
Register the remote MCP server in OpenCode's config for terminal-first and scripted agent runs.
Add PopMCP as an MCP server in Z.ai's desktop app and work the account from the same window.
FAQ
What teams ask before putting Google Data Studio behind an AI client.
Data Studio's API only answers apps that a Google Workspace admin has approved for the organization. Until an admin adds the app's client ID with the Data Studio scopes (Admin console, Security, Access and data control, API controls, Manage domain-wide delegation, Add new), Google refuses the sign-in with that error. After that, people in the organization connect without a consent screen at all. The connect form shows the client ID and the scopes to give your admin.
No. Google opens the Data Studio API only to Google Workspace and Cloud Identity accounts. Reports a personal account owns can still be reached: share them with your Workspace account and connect that one, since every tool covers everything the signed-in account can see.
No. Google's API covers finding reports and data sources and managing who can open them. It cannot read a report's pages, charts, fields or data, and it cannot create, copy or delete reports. For the numbers, connect the data source itself, such as Google Analytics, Search Console or BigQuery. To create a report, build_report_link makes a Linking API link that copies a template onto the opener's own data.
sharing_audit reads the sharing of each report or data source you own, up to a limit you choose, and flags anyone-with-the-link access (worst when it can edit), people and groups outside your organization's email domain, and whole domains. It returns the flagged ones first, with links, and counts the clean ones. set_link_sharing and unshare_with_people fix what it finds.
Both. Google renamed Looker Studio back to Data Studio in April 2026, and Data Studio Pro is now Data Studio Pro. Nothing about the API or your reports changed, and links on lookerstudio.google.com and datastudio.google.com both work with every tool.
Five, all by change detection. Across the account: a report created, edited, or moved to the trash. On a report you watch: someone gains or loses access, and link sharing turned on for anyone or a whole domain. A typical use is a message to the team whenever a client report becomes public.
No. PopMCP hosts it and gives you a Streamable HTTP MCP URL. There is nothing to deploy, no callback URL to register, and no infrastructure to keep running or patch.
Any client that supports a remote Streamable HTTP MCP server: Claude Desktop, Claude Web, Claude Code, ChatGPT custom connectors, Codex and the Codex CLI, OpenCode and Z.ai's ZCode, as well as editors such as Cursor, Windsurf and Zed. Your client signs in to PopMCP with OAuth; the provider credential never leaves the server.
Connect Google Data Studio in PopMCP first, then run claude mcp add --transport http popmcp https://app.popmcp.com/mcp in a terminal. Inside Claude Code, run /mcp and sign in to PopMCP in the browser window it opens, ticking Google Data Studio on the consent screen. The Google Data Studio tools are then available in that session, and no Google Data Studio credential is stored on your machine.
Yes. The Google Data Studio catalog is small enough that all 13 tool definitions load into every conversation, so your AI never has to search for one before it can call it.
A tool is something your AI calls, and there are 13 here. A trigger is something PopMCP watches for you: 5 Google Data Studio events that can start work on the PopMCP side. Triggers never enter your AI client's context, and none of them ask you to paste a callback URL into Google Data Studio.
Launch a hosted MCP endpoint for Google Data Studio, keep tool access under control, and start testing real workflow prompts right away.