Google Data Studio
Google Data Studio is Google's business intelligence platform for creating dashboards and reports; its Asset API searches organizational assets and manages their sharing permissions.
Verdict
Common use cases
- Audit dashboard access before quarterly reviews
- Grant contractor view-only rights for two weeks
- Find all reports owned by a departing analyst
- Bulk-add finance team as viewers on revenue dashboards
- Revoke external collaborator permissions after project wrap
Integration
- Vendor
- Google Data Studio
- Category
- other
- Auth
- OAUTH2
- Tools
- 5
- Composio slug
google_data_studio
Tools
- Add Members to Asset Role
Ensure one or more members belong to a mutable asset role and verify each requested membership after the write.
- Get Asset Permissions
Get every populated permission role and the current concurrency etag for one Google Data Studio asset.
- Replace Asset Permissions
Replace all four mutable permission-role memberships for a Google Data Studio asset, preserving owners and rejecting stale etags. Every mutable role is required; pass an empty list to clear that role.
- Revoke Asset Member Permissionsdestructive
Remove one or more members from every removable role on a Google Data Studio asset and verify whether each was removed or already absent.
- Search Assets
Search accessible Google Data Studio reports or data sources and return one page of asset metadata.
Setup
Setup guide
- 11. Inside any Switchy Project, type '@Google Data Studio' and click 'Connect new integration' in the dropdown. 2. You'll land on Google's OAuth consent screen — sign in with the account that owns or can access your Data Studio reports. 3. Review the requested scopes: 'View and manage your Google Data Studio assets' (read/write for reports, data sources, and permissions). 4. Click 'Allow' to authorize Switchy. 5. You'll return to your Project with a confirmation message. 6. Test the connection by typing '@Google Data Studio search for reports about revenue' — the MCP will return a list of matching assets with titles, IDs, and owner emails. 7. To manage permissions, grab an asset ID from search results and prompt '@Google Data Studio show who can access asset [ID]' to see current roles. 8. If you need to add or remove members, use prompts like '@Google Data Studio add user@example.com as editor on asset [ID]' — the MCP confirms each change and returns the updated permission list.
What teammates see: by default, memories from Google Data Studio are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Search Revenue Dashboards
@Google Data Studio search for reports with 'revenue' in the title and show me the asset ID, owner, and last modified date for each result.
List Current Permissions
@Google Data Studio get the current permissions for asset [ASSET_ID] and list every member in each role, including owners.
Add Bulk Viewers
@Google Data Studio add alice@example.com, bob@example.com, and carol@example.com as viewers on asset [ASSET_ID] and confirm each was added successfully.
Revoke All Access
@Google Data Studio revoke all permissions for user@example.com on asset [ASSET_ID] and tell me which roles they were removed from.
Replace Full Permission Set
@Google Data Studio replace all permissions on asset [ASSET_ID] with viewers: [user1@example.com], editors: [user2@example.com], commenters: [], and confirm the new roster matches.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@google-data-studio search for all reports containing 'Q4 revenue' in the title and show me their current sharing status
Found 3 reports matching 'Q4 revenue': 1. Q4 Revenue Dashboard (ID: abc123) – Last modified Dec 15, 2024. Currently shared with 12 viewers. 2. Q4 Revenue by Region (ID: def456) – Last modified Dec 10, 2024. Currently shared with 8 viewers, 2 editors. 3. Q4 Revenue Forecast (ID: ghi789) – Last modified Nov 28, 2024. Private (only you have access). This is an illustrative example showing how the MCP returns asset metadata including sharing scope. Actual results depend on your Data Studio account's current state.
Demonstrates the search capability across your accessible Data Studio assets. Requires OAuth2 consent with read scope for Data Studio. Search returns one page at a time; if you have many reports, you may need to refine your query or request subsequent pages.
@google-data-studio add sarah@company.com and mike@company.com as editors to report abc123, then confirm they both have access
Successfully added 2 members to the editor role on report abc123: ✓ sarah@company.com – Added as editor, verified in current permissions. ✓ mike@company.com – Added as editor, verified in current permissions. Both members can now edit this report. The MCP performed a write operation followed by a read-back verification to confirm the memberships are live. This is an illustrative example; actual confirmation depends on your account's permission state at runtime.
Showcases the write-and-verify workflow for granting access. Requires OAuth2 consent with write scope for Data Studio permissions. Side-effect: the specified users immediately gain editor access and will see the report in their Data Studio account. If a user is already an editor, the MCP treats it as a no-op.
@google-data-studio get the full permission breakdown for report def456, then draft a summary email explaining who can view versus edit this dashboard
Current permissions for report def456: - Owners: you@company.com - Editors: sarah@company.com, mike@company.com - Viewers: finance-team@company.com (12 members), exec-team@company.com (5 members) Draft email: Subject: Access Summary – Q4 Revenue by Region Dashboard Hi team, Here's the current access breakdown for our Q4 Revenue by Region report: - Edit access: Sarah and Mike can modify charts and data sources. - View access: Finance team (12 people) and exec team (5 people) can view the live dashboard but cannot make changes. Let me know if anyone else needs access. This is an illustrative example combining permission data with AI-generated prose.
Pairs the MCP's permission-read tool with the AI's summarization ability to produce human-readable access documentation. Useful for audit trails or onboarding new team members. The permission snapshot reflects the moment of the query; changes made afterward won't appear until you re-query.
Use-case deep-dives
When you need to audit and reassign report access fast
A 6-person marketing team loses a contractor mid-quarter who built three Data Studio dashboards tracking campaign spend. The team lead needs to confirm what the contractor could see, strip their access, and grant the replacement analyst editor rights before Monday's budget review. This MCP is the right call: the Get Asset Permissions tool shows exactly who has what role on each report, Revoke Asset Member Permissions removes the old email in one pass, and Add Members to Asset Role grants the new analyst editor access without touching viewer lists. The trade-off: if your org has dozens of dashboards and you need bulk audit across all of them, the Search Assets tool returns one page at a time and you'll script multiple calls. For a handful of known reports, this is faster than clicking through the Data Studio UI.
When you share 20+ dashboards with rotating stakeholders
A 12-person agency runs paid-media campaigns for eight clients and maintains a Data Studio dashboard per client. Every Monday, the account manager updates viewer permissions to add new client contacts and remove churned ones. This MCP is borderline: the Replace Asset Permissions tool can overwrite all four mutable roles in one atomic write, which prevents the "half-updated" state you get clicking through the UI. But if your client list changes fewer than three times a month, the OAuth2 setup and token refresh overhead isn't worth it—just use the Data Studio sharing dialog. The threshold: if you're touching permissions on more than five dashboards weekly, or if you need an audit trail of who-changed-what, this MCP pays off. Otherwise, skip it.
When your support reps need to find the right dashboard under pressure
A 9-person customer-success team maintains 15 Data Studio dashboards covering product usage, billing, and SLA metrics. During a live customer call, a rep needs to pull up the "enterprise-tier latency" dashboard but can't remember its exact name. The Search Assets tool lets the rep query "latency enterprise" from Switchy and get back the matching report link in under two seconds. This MCP wins when your dashboard library is large enough that scrolling the Data Studio home screen wastes time, but small enough that search results fit in one page (roughly under 50 dashboards). If your org has hundreds of reports, the one-page return limit means you'll need multiple searches with different keywords. For a mid-sized dashboard library and a team that lives in Switchy during support calls, this is a clean win.
Frequently asked
What does the Google Data Studio MCP do in Switchy?
It lets your team search Data Studio reports and data sources, then manage who can view or edit them. The MCP exposes five permission-management tools: you can add members to roles, replace entire permission sets, revoke access, and fetch current permissions. It doesn't create or modify report content—only the sharing settings around existing assets.
Do I need admin access to connect Google Data Studio?
You need owner-level permissions on the Data Studio assets you want to manage. OAuth2 prompts you to grant read and write access to your reports and data sources. If you only have viewer or editor rights on an asset, the MCP can search it but can't change its permissions. Connect with an account that owns the reports your team needs to share.
Can the MCP edit Data Studio report visualizations or data sources?
No. It only manages permissions—who can view, edit, or own an asset. If you need to change charts, filters, or data connectors, open Data Studio directly. The MCP is for automating access control, not report design. Think of it as a sharing-settings API, not a report-builder.
Why use this instead of Data Studio's built-in sharing UI?
The MCP is faster when you're granting the same permissions across dozens of reports or syncing access with another system. The built-in UI works fine for one-off shares; the MCP shines when you're scripting bulk permission changes or auditing who has access to which assets. It also logs every change in Switchy's activity feed.
Who on the team should connect this MCP?
Whoever owns the Data Studio reports you want to automate. That's usually a data analyst or BI lead. They'll authenticate once; then any Switchy teammate can trigger the permission tools without needing their own Data Studio owner rights. The connection doesn't consume extra Data Studio seats or quotas.