MCP YouTube Transcript
An MCP server retrieving transcripts of YouTube videos
Description from the maker (original English)
Run Google Ads and Meta Ads from ChatGPT or Claude: audit wasted spend, create and manage campaigns.
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.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://api.loomascale.com/mcpRun this in your terminal
claude mcp add --transport http ads https://api.loomascale.com/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"ads": {
"url": "https://api.loomascale.com/mcp"
}
}
}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": {
"ads": {
"type": "http",
"url": "https://api.loomascale.com/mcp"
}
}
}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.
ChatGPT connects only to servers on the internet:
https://api.loomascale.com/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
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 loomascale.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
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.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
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.
Self-hostable MCP servers that let ChatGPT or Claude run real ad accounts — with spend guardrails they cannot talk their way past.
MIT licensed. Extracted from a production service that has run live campaigns from inside ChatGPT since 2026.
| What it does | Docs | |
|---|---|---|
| [google-ads-mcp](google-ads/README.md) | 42 tools over the Google Ads API: performance, keyword research, campaign and Performance Max creation, budget and bidding changes | README |
Meta Ads is next.
No JDK, no Maven, no source build:
curl -O https://raw.githubusercontent.com/loomascale/ads-mcp/main/docker-compose.yml
curl -O https://raw.githubusercontent.com/loomascale/ads-mcp/main/.env.example cp .env.example .env && $EDITOR .env # every value documented in place docker compose up
Then open http://localhost:8080/connections and connect an ad account.
Set MCP_DEFAULT_MAX_DAILY_BUDGET_CENTS low before pointing this at a live account. It is the last thing between a model and your card.
Full prerequisites — the Google Ads developer token in particular, which needs an application and takes days to approve — are in the server README.
Worth reading before running anything, because money is involved:
mcp-core is the reusable half: MCP's JSON-RPC transport, a tool registry SPI, and a minimal OAuth 2.1 authorization server with dynamic client registration, PKCE and refresh-token rotation. If you want ChatGPT or Claude to call *your* tools over an authenticated endpoint, that is the part to depend on — it knows nothing about advertising beyond a few shared abstractions the platform servers reuse.
One repository, one version. A change spanning the core and a platform is one commit and one build, which is why this is not three repositories:
mcp-core/ protocol, OAuth 2.1 server, shared ads abstractions
google-ads/client/ Google Ads API client — no Spring, no MCP, usable on its own google-ads/server/ the runnable MCP server and its tools
google-ads/server resolves mcp-core at ${project.version} inside the reactor, so a fresh clone builds with nothing published anywhere:
./mvnw verify
Credentials are encrypted at rest with AES-256-GCM. Authorization codes and refresh tokens are stored hashed and are single-use; reusing a rotated refresh token revokes the whole family. Model-supplied image URLs pass an SSRF policy before anything is fetched. Tool arguments are never logged — only argument names.
Put TLS in front of any of this. Report vulnerabilities privately: see SECURITY.md.
These servers are extracted from [LoomaScale](https://ai.loomascale.com), an AI operator for Google Ads: you talk to ChatGPT or Claude, and it reads your account, finds waste, and makes the changes. This repository is the engine that runs it — not a demo or a cut-down version. The tools here are the same ones that have created and managed live campaigns since 2026, guardrails included.
What stays in the product rather than here is the commercial half: accounts and billing, usage metering, the multi-user dashboard, and the connect flows for people who do not want to run a server. mcp-core exposes those as replaceable interfaces — QuotaPolicy, ResourceOwnerAuthenticator, AdsConnectionStore — precisely so the open-source build has working defaults and LoomaScale can substitute its own.
ai.loomascale.com is the hosted version. Same tools, no Docker, no developer token application, no OAuth client to register. It starts with a free Google Ads waste audit — the assistant reads your account and reports what is being wasted, before you pay anything. Plans and limits are on the pricing page.
Self-hosting is a genuine alternative, not a teaser: everything needed to run these servers against your own accounts is in this repository under the MIT licence, with no feature held back and no phone-home.
The connection guides are written for the hosted product but the client-side steps are identical against your own server — the same consent screen, the same connector setup:
Other things extracted from the same codebase live at ai.loomascale.com/oss.
See CONTRIBUTING.md — the secrets section first.
Built and used in production by LoomaScale. MIT licensed.