MCP YouTube Transcript
An MCP server retrieving transcripts of YouTube videos
제작자가 쓴 설명(영어 원문)
Hosted MCP for Google Ads, Search Console, GA4 and Merchant Center: ask, build, approve changes.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
웹, 데스크톱, 모바일의 Claude에서 쓸 수 있어요:
https://camberstack.io/mcp터미널에서 이 명령어를 실행하세요
claude mcp add --transport http google-ads https://camberstack.io/mcp프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"google-ads": {
"url": "https://camberstack.io/mcp"
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"google-ads": {
"type": "http",
"url": "https://camberstack.io/mcp"
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요:
https://camberstack.io/mcp메뉴 이름은 요금제나 시기에 따라 조금 다를 수 있어요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
서버가 도구 목록을 보여 주기 전에 로그인을 요구해요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 6일 점검
레지스트리 이름이 도메인 camberstack.io 기준으로 확인되었어요(레지스트리가 도메인 소유를 확인해요)
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
323ms 만에 응답(HTTP 401)
OAuth 로그인을 지원한다고 밝혀서, AI 앱이 로그인 화면으로 안내해 줘요
아직 점검하지 않았어요. 엔드포인트를 점검할 때 도구 목록을 읽어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 3개 중 3개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
제작자의 클라우드에서 실행돼요. 설치 없이 인터넷으로 연결하지만, 보내는 내용은 제작자의 서버를 거쳐요.
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.27.0)은 어제 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되기 때문에, 원격 MCP 서버를 지원하는 앱(예: 개발자 모드의 ChatGPT)에서도 쓸 수 있어요.
같은 카테고리에는: MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
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.
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
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
앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요