MCP YouTube Transcript
An MCP server retrieving transcripts of YouTube videos
Beschreibung vom Entwickler (englisches Original)
Hosted MCP for Google Ads, Search Console, GA4 and Merchant Center: ask, build, approve changes.
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
Du brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Funktioniert in Claude im Web, auf dem Desktop und auf dem Handy:
https://camberstack.io/mcpFühre das in deinem Terminal aus
claude mcp add --transport http google-ads https://camberstack.io/mcpIn .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"google-ads": {
"url": "https://camberstack.io/mcp"
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"google-ads": {
"type": "http",
"url": "https://camberstack.io/mcp"
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
ChatGPT verbindet sich nur mit Servern im Internet:
https://camberstack.io/mcpMenünamen können sich je nach Tarif und mit der Zeit leicht unterscheiden.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Der Server verlangt eine Anmeldung, bevor er seine Tools auflistet.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 6. Nov. 2026
Der Registry-Name wurde über die Domain camberstack.io bestätigt (die Registry prüft, wem die Domain gehört)
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Antwort in 323 ms (HTTP 401)
Gibt OAuth-Anmeldung an, damit deine KI-App dich zum Einloggen weiterleiten kann
Noch nicht geprüft; wir lesen die Tool-Liste, wenn wir den Endpunkt prüfen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 3 von 3 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.
Er läuft in der Cloud des Entwicklers. Du verbindest dich übers Internet, ohne etwas zu installieren, aber was du sendest, läuft über die Server des Entwicklers.
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.27.0) kam gestern in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Er verbindet sich per URL, also funktionieren auch Apps, die Remote-MCP-Server akzeptieren, zum Beispiel ChatGPT im Entwicklermodus.
In derselben Kategorie: MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
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.
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
Connect Google Ads, Search Console, Google Analytics 4 and Merchant Center to Claude, ChatGPT, Cursor or any MCP client with one Google sign-in, and use them together: the searches you pay for that already rank, whether ad clicks convert on the landing page, which disapproved products were earning in Shopping. Your AI reads with read-only tools and can propose changes, from negative keywords to whole Search, Performance Max, Display and YouTube campaigns, GA4 key events and Merchant Center product fixes. Nothing changes until you approve a specific proposal; risky changes and deletions Google can't reverse are flagged first, and the rest can be undone. A demo account lets anyone try every tool first.
Hosted: https://camberstack.io/mcp. Free: every tool and unlimited changes on 1 account, with one switch a month; from November 15, one Google service at a time. Plus $7/mo: all four services on 1 account. Pro $15/mo: up to 5 accounts. Agency $49/mo: up to 25.
Setup guides, with screenshots and troubleshooting: Connect Google Ads to Claude · Connect Google Ads to ChatGPT · every tool · Cursor, VS Code and others
| tool | writes? | what it does |
|---|---|---|
list_accounts | no | every account the login reaches, including client accounts under a manager (MCC) |
account_overview | no | spend, conversions, cost per conversion per campaign, plus attention when something needs a look: ads with policy problems and why, Google's open recommendations, primary conversions quiet for 30 days |
keyword_ideas | no | Keyword Planner ideas from seed keywords and/or a URL: monthly searches, competition, top-of-page bid range; marks ideas the account already targets or blocks |
keyword_metrics | no | Keyword Planner numbers for an exact list, with the last 12 months of searches |
run_gaql | no | any read-only GAQL SELECT |
search_console_sites | no | the websites (Search Console properties) the login can read |
search_console_summary | no | site-wide clicks, impressions, CTR and position for a window vs. the window before it |
search_console_performance | no | organic clicks, impressions, CTR and position by query, page, country, device or date; text or RE2 regex filters |
search_console_trend | no | a window vs. the one before it, per query and per page: rising, falling, new, lost, and rising searches losing position |
search_console_opportunities | no | queries on positions 4-20 with projected click gain, top-5 queries with weak CTR, question-shaped queries |
search_console_inspect_urls | no | URL Inspection for up to 20 pages: indexed or why not, last crawl, canonical chosen vs declared, structured-data errors |
search_console_sitemaps | no | submitted sitemaps: last downloaded, URL count, errors and warnings |
send_feedback | no | sends the user's approved message to the maintainer; no account data or conversation |
propose_search_console_changes | no | checks sitemap and property changes against the live property and stores a proposal |
paid_organic_overlap | no | joins an Ads account's search terms with a site's organic queries: searches paid for that already rank near the top, and page-2+ searches with no ad |
analytics_properties | no | the Google Analytics 4 properties the login can read; if Analytics isn't granted yet, a personal link that adds it |
analytics_setup | no | a property's web streams (measurement IDs), key events and Google Ads links |
propose_analytics_changes | no | like propose_changes, for GA4 setup: create_ga4_property (with a web stream; the applied result gives the tag), mark_key_event/unmark_key_event, link_google_ads/unlink_google_ads. Applied and undone with apply_changes/undo_changes |
analytics_landing_pages | no | sessions, users, engagement rate, key events and key event rate per landing page, optionally for one channel (e.g. Paid Search) |
analytics_report | no | any GA4 Data API report by dimension and metric names, with a contains filter |
landing_page_speed | no | PageSpeed Insights for up to 5 pages: Core Web Vitals from real Chrome visitors (28 days), a Lighthouse score, and the fixes worth most. Any public URL, no Google service needed |
merchant_accounts | no | the Merchant Center accounts the login can read (sub-accounts included); if Merchant Center isn't granted yet, a personal link that adds it |
merchant_product_issues | no | account issues, product status counts, and each product issue with how many products it hits and examples; or one product's issues in full |
merchant_report | no | any read-only Merchant Center Query Language (MCQL) query, e.g. Shopping clicks per product from product_performance_view |
merchant_ad_spend | no | Merchant Center problems (disapproved, limited, pending) joined with what each product earned in Shopping and Performance Max ads, most value first, and whether it stopped spending in the last 7 days |
propose_merchant_changes | no | like propose_changes, for Merchant Center products: set_product_attributes (price, GTIN, title, …), exclude_products/include_products, clear_product_overrides, and add_product/update_product/delete_product for products in Camberstack's own "Camberstack products" source. Applied and undone with apply_changes/undo_changes |
propose_changes | no | resolves changes against the live account, dry-runs them with Google (validateOnly), stores a proposal with a plain-English summary |
apply_changes | yes | applies a stored proposal (the user's own, un-applied, still matching the account; if the account moved, returns an updated proposal to approve instead); records each change's inverse |
undo_changes | no | builds the reversing proposal for an applied one |
switch_account | plan only | spends the plan's one account switch per 30 days on an account, after the user agrees; changes nothing in Google Ads |
billing | no | plan, Google Ads accounts in use (last 30 days) vs. the plan's limit, and a personal upgrade or manage-billing link |
discard_proposal | no | marks an open proposal discarded so it can't be applied |
change_history | no | every proposal, with what was applied, what failed and what was undone |
disconnect | no | revokes Camberstack's Google access and deletes the stored credentials (the user confirms) |
The Search Console tools take either days or exact start_date/end_date, and fresh: true to include the last 2-3 days Google is still filling in. Sitemaps and properties change through propose_search_console_changes (submit or delete a sitemap, add or remove a property). Requesting indexing has no API, and verifying a property is done in Search Console.
The Google Analytics tools need analytics.readonly and analytics.edit (Google-verified sensitive scopes). Sign-in asks for them alongside Ads and Search Console; a connection made before they were added gets a personal /connect/analytics link on its first Analytics call, which adds both to the same Google account. The Cloud project needs the Google Analytics Data API and Admin API enabled.
Merchant Center accounts are their own plan allowance, the same size as Google Ads' (Free 1, Plus 1, Pro 5, Agency 25), counted as mc: in tool_calls with their own switch (switch_account takes mc: ).
The Merchant Center tools need content, which isn't part of connecting: the first call without it returns a personal /connect/merchant-center link that adds it. Before any call works, the Cloud project needs the Merchant API enabled and registered once with a production Merchant Center account the operator administers (POST https://merchantapi.googleapis.com/accounts/v1/accounts/{ID}/developerRegistration:registerGcp); merchants don't register. Unregistered, calls answer 401 "not registered", which the tools report as Camberstack's to fix. Reports work on standalone accounts and sub-accounts, not on an advanced account itself. Account 000000001 is the demo (sample data: two best sellers disapproved for a price mismatch 9 days ago; overrides there fix the issue).
Products Camberstack creates live in its own primary API source ("Camberstack products"); only those can be updated in place or deleted (undo re-creates them from Camberstack's copy). Adding an offer_id another feed already has is refused, since Google would move that product into our source ("offer stealing").
Merchant Center changes never edit the merchant's feed. Each is an override in Camberstack's own supplemental data source ("Camberstack overrides"), created on the first write. Google applies a supplemental source only once it's in a primary source's rules, so the first override on a feed's products also patches that feed's defaultRule to put ours first (every source already there is kept): the summary shows it as a ⚠ line. Feeds made in the Merchant Center UI or by autofeed can't be patched, and the proposal says so. Google can't read overrides back, so merchant_overrides keeps Camberstack's copy per product; undo restores exactly that (removing the input when there was none). The Merchant API has no dry run: re-resolving at apply is the check, as with GA4.
What a proposal can do:
MUTATE_NOT_ALLOWED, v23).Images are existing image assets or https URLs, which are downloaded SSRF-safe (src/fetch-safe.ts) and uploaded. A proposal can also add an ad group, keywords, an ad or sitelinks to an existing campaign.
delete_*).productLinks:create/:remove; neither dry-runs: create has none and remove's always answers 500, so propose checks the account is reachable and not a test account, which Google won't link).Risky changes carry a ⚠ line in the proposal summary: enabling a campaign, more than doubling a budget or a bid, switching bid strategy, removing the last location, a new primary conversion action, removing a conversi
Nur der Anfang wird gezeigt; den Rest findest du im Repo