MCP YouTube Transcript
An MCP server retrieving transcripts of YouTube videos
Description from the maker (original English)
Google Analytics 4 MCP server: 27 read tools, no write tools.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
GA4_CLIENT_ID, GA4_CLIENT_SECRET, GA4_REFRESH_TOKEN, GA4_PROPERTY_ID, GA4_PROPERTY_IDSValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"google-analytics": {
"command": "npx",
"args": [
"-y",
"@getmcpads/google-analytics-mcp-server"
],
"env": {
"GA4_CLIENT_ID": "your-value",
"GA4_CLIENT_SECRET": "your-value",
"GA4_REFRESH_TOKEN": "your-value",
"GA4_PROPERTY_ID": "your-value",
"GA4_PROPERTY_IDS": "your-value"
}
}
}
}Run this in your terminal
claude mcp add google-analytics --env GA4_CLIENT_ID=your-value --env GA4_CLIENT_SECRET=your-value --env GA4_REFRESH_TOKEN=your-value --env GA4_PROPERTY_ID=your-value --env GA4_PROPERTY_IDS=your-value -- npx -y @getmcpads/google-analytics-mcp-serverFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"google-analytics": {
"command": "npx",
"args": [
"-y",
"@getmcpads/google-analytics-mcp-server"
],
"env": {
"GA4_CLIENT_ID": "your-value",
"GA4_CLIENT_SECRET": "your-value",
"GA4_REFRESH_TOKEN": "your-value",
"GA4_PROPERTY_ID": "your-value",
"GA4_PROPERTY_IDS": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"google-analytics": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@getmcpads/google-analytics-mcp-server"
],
"env": {
"GA4_CLIENT_ID": "your-value",
"GA4_CLIENT_SECRET": "your-value",
"GA4_REFRESH_TOKEN": "your-value",
"GA4_PROPERTY_ID": "your-value",
"GA4_PROPERTY_IDS": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
GA4_PROPERTY_ID envGA4_PROPERTY_IDS envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified against the domain getmcpads.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: GA4_CLIENT_ID, GA4_CLIENT_SECRET, GA4_REFRESH_TOKEN
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (2.1.1) reached the registry 11 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
An MCP server retrieving transcripts of YouTube videos
GA4 MCP server for AI agents: schema discovery, server-side aggregation, analysis-ready defaults.
AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Explore traffic, conversions, funnels and property configuration through a read-only MCP server.
Watch the film · What's new · Install · Tool reference · Try hosted getmcpads
[Play the 45-second film](https://www.getmcpads.com/home/film/get-mcp-ads-brand-film-1080p.mp4)
The film shows hosted getmcpads with sample data. Its MCP Apps, from creative galleries and alerts to Google Sheets exports and bulk launches, belong to the hosted product. This repository provides the standalone native API tools.
27 read tools · Read-only by design.
Run locally with your own platform credentials and a client that supports stdio MCP, such as Claude Desktop, Claude Code or Cursor. Your requests go directly to the platform. For managed connections, including supported ChatGPT setups, use the hosted option.
[v2.1.1: Zod 4 security update](https://github.com/get-mcp-ads/google-analytics-mcp-server/releases/tag/v2.1.1) · October 26, 2026
zod to 4.6.7. Every Zod release before 4.6.6 is covered by the high-severity advisory GHSA-mrhx-c7xc-m3w5: validating an oversized constrained collection can exhaust memory, and no Zod 3 release carries the fix. npm audit --omit=dev reports no vulnerability again.server-card.json is regenerated with Zod 4's JSON Schema output, which spells some constraints differently.Earlier releases
| Version | Date | Highlights |
|---|---|---|
| 2.1.0 | October 23, 2026 | Property allowlist and revoked-token handling |
| 2.0.1 | September 23, 2026 | Public repository restored |
| 2.0.0 | September 20, 2026 | Gateway sync and security fixes |
| 1.1.0 | September 13, 2026 | Platform capability sync and quality contracts |
| 1.0.2 | August 30, 2026 | Announce the package version over MCP. |
| 1.0.1 | August 30, 2026 | Add server.json and mcpName for the official MCP Registry, under com.getmcpads/google-analytics. |
| 1.0.0 | August 29, 2026 | First open-source release |
Full changelog · All releases
Source synchronization: SOURCE_SYNC.md.
Requires Node.js 22.23.4, 24.22.1 or 26.12.1, or a newer release of one of these lines. Older releases lack the October 2026 security fixes, and the server prints a warning on stderr when it starts on one. CI covers Node 22, 24 and 26.
This release makes no breaking change to the configuration. One change is announced for 3.0.0: GA4_PROPERTY_IDS is optional in 2.x and becomes required. When set, every tool is limited to the listed properties, and GA4_PROPERTY_ID must be one of them. When unset, the server starts as before and prints one line on stderr recommending it. The tools and their schemas are unchanged.
This is a GitHub source release. npm and MCP Registry versions are published separately. The commands below select this exact version; unpinned npx examples later in this document select the version currently available on npm.
git clone --branch v2.1.1 --depth 1 https://github.com/get-mcp-ads/google-analytics-mcp-server.git
cd google-analytics-mcp-server npm ci npm run build
Configure your MCP client to run node with the absolute path to dist/cli.js and the platform credentials documented below.
Prefer a managed connection? Use Google Analytics 4 with hosted getmcpads. Connect your account, select the data your assistant may access and use the hosted MCP connection. See the site for current features and plans.
| 27 read tools | Reports, pivots, funnels, realtime, plus the Admin API: properties, data streams, custom definitions, key events, audiences |
| Diagnostics | Ecommerce, BigQuery export, server-side tagging, audience exports, quota snapshots |
| 51 metrics, 62 dimensions | With a compatibility matrix that catches invalid combinations before they hit the API |
| 6 resources | Live catalogues the model can read: metrics, dimensions, compatibility rules, 12 workflow recipes |
| Identifier redaction | User, email and device identifiers redacted by default on access bindings and audience exports, with explicit opt-in to see them |
| No writes at all | Not a flag, a property of the code. See below |
GA4 rejects many metric and dimension combinations, and its errors rarely explain which pair is at fault. This server carries the compatibility matrix, so ga4_check_compatibility and ga4_validate_query let the model verify a combination before spending a call and a quota token on it.
Quotas matter here more than on ad platforms: GA4 charges tokens per property per day, and a few careless exploratory queries can exhaust them. ga4_get_property_quotas_snapshot shows what is left.
There are no write tools, and no environment variable that adds any. Every tool calls a read method of the Data API or the Admin API.
This is not caution for its own sake. A misread report is a wrong answer you can spot. A mistaken write to an analytics property, a deleted audience or an edited data stream, corrupts the record you use to judge everything else, and often silently. The other servers we publish do have write tools, guarded by a mandatory preview. This one has none.
Our ad platform servers with guarded writes: Meta Ads · Google Ads · TikTok Ads
Analytics data is not anonymous by default. A GA4 property can carry a userId you set yourself, a device identifier, or a Google Signals pseudonymous ID. An MCP conversation sends whatever a tool returns to a model.
Identifiers are redacted by default wherever this server can return them, and showing them is an explicit opt-in, never the default.
| Tool | Behaviour |
|---|---|
ga4_list_admin_resources | Access bindings have user and email identifiers redacted |
ga4_query_audience_export | Identifier columns redacted, matched against the export's own dimension metadata |
ga4_get_audience_export_diagnostics | Same redaction on the row sample |
Every one of these accepts includePersonalIdentifiers: true to return raw values, and defaults to false.
Audience export rows are positional, so the redaction reads the export's dimension metadata to find identifier columns. If that metadata is missing, every value in the row is redacted rather than guessing which column is safe. Failing closed is the point.
Report rows are not redacted. ga4_run_report and the other reporting tools return what you asked for. Altering the numbers a report returns would be worse than returning them.
So one decision stays yours: if your property carries a userId you consider personal, do not request it as a report dimension in a conversation whose transcript leaves your machine.
Three values, obtained once.
In a Google Cloud project, enable the Google Analytics Data API and the Google Analytics Admin API, then create an OAuth client under APIs & Services → Credentials. Choose Desktop app for local use. Note the client ID and client secret.
Run the OAuth consent flow once, signed in as a Google account with access to your GA4 properties, and keep the refresh token. The analytics.readonly scope is enough, and it is the only one you should grant.
📖 Google OAuth for installed apps
The refresh token does not expire. It is the sensitive value: anyone holding it can mint access tokens indefinitely. Use an OAuth client dedicated to this server so you can revoke it on its own.
Set GA4_PROPERTY_ID to avoid passing it on every call. Find it in GA4 under Admin → Property Settings, or list them with ga4_list_properties.
Run `ga4_health_check` as your first call. It verifies the credentials and lists the properties you can actually reach, without printing any secret.
~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": { "google-analytics": { "command": "npx", "args": ["-y", "@getmcpads/google-analytics-mcp-server"], "env": { "GA4_CLIENT_ID": "your-client-id", "GA4_CLIENT_SECRET": "your-client-secret", "GA4_REFRESH_TOKEN": "your-refresh-token", "GA4_PROPERTY_IDS": "123456789" } } } }
Restart Claude Desktop. Ask it: *"list my Google Analytics properties"*.
claude mcp add google-analytics --env GA4_CLIENT_ID=... --env GA4_CLIENT_SECRET=... --env GA4_REFRESH_TOKEN=... -- npx -y @getmcpads/google-analytics-mcp-server
.cursor/mcp.json in your project, same shape as the Claude Desktop config above.
git clone https://github.com/get-mcp-ads/google-analytics-mcp-server.git
cd google-analytics-mcp-server npm install && npm run build cp .env.example .env # then fill in your credentials npm start
| Variable | Default | Meaning |
|---|---|---|
GA4_CLIENT_ID | none | Required. OAuth client ID |
GA4_CLIENT_SECRET | none | Required. OAuth client secret |
GA4_REFRESH_TOKEN | none | Required. From the consent flow |
GA4_PROPERTY_ID | none | Optional default, saves passing it on every call |
GA4_PROPERTY_IDS | *unset* | Recommended. Comma-separated property IDs every tool is limited to. Unset, every property the credentials reach is available. Required in 3.0.0 |
LOG_LEVEL | info | debug, info, warn, error |
Check your setup at any time:
npm run doctor
`
Only the beginning is shown; read the rest in the repo