MCP YouTube Transcript
An MCP server retrieving transcripts of YouTube videos
作者提供的说明(英文原文)
Google, Meta, LinkedIn and ChatGPT Ads for AI assistants. Every change needs your approval.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://adako.ai/mcp在终端中运行这条命令
claude mcp add --transport http ads https://adako.ai/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"ads": {
"url": "https://adako.ai/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"ads": {
"type": "http",
"url": "https://adako.ai/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://adako.ai/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过域名 adako.ai 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(0.3.2)于39天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 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、图片和脚本已被移除。链接会离开本站。
アダコ · adako.ai
Adako is an MCP server and REST API that connects Claude, ChatGPT, Cursor and other assistants to Google Ads, Meta Ads, ChatGPT Ads, TikTok Ads and LinkedIn Ads.
https://adako.ai/mcp
Ask "how did my campaigns do last month?" and get an answer from the live account, in the account's own currency. Ask "raise that budget to 40 a day" and get a proposal you approve before anything moves. Created campaigns are always paused.
This repository holds the public pieces: the Agent Skills, per-client configuration, one-file installers, a Claude Code plugin, and the MCP Registry entry. The server itself is hosted.
233 tools across five platforms, plus Adako's own.
| Platform | Tools | What they cover |
|---|---|---|
| Google Ads | 70 | Search and Performance Max, keywords and search terms, budgets and bid strategies, assets and extensions, conversion actions, labels, schedules, geo, hourly and device reports |
| Meta Ads | 44 | Campaigns, ad sets and ads, image, video, carousel and app-install launches, audiences and placements, pixels, lead forms, creative fatigue |
| LinkedIn Ads | 34 | Campaign groups and campaigns, image, video, carousel and text ads, B2B targeting, audience forecasts, conversion rules, engagement metrics |
| TikTok Ads | 30 | Campaigns, ad groups and in-feed video ads, Spark Ads, video metrics, identities, pixels, creative fatigue |
| ChatGPT Ads | 23 | Chat card campaigns end to end, account limits, pixels, review verdicts |
| Adako | 32 | Connections and usage, tool discovery, proposals, diagnostics, monitors, briefs and reports |
Your client does not see 233 entries. It sees 16 tools callable by name plus 13 routers. Each platform has a read router (google_ads, meta_ads, chatgpt_ads, tiktok_ads, linkedin_ads) and a write router beside it (google_ads_write, meta_ads_write, chatgpt_ads_write, tiktok_ads_write, linkedin_ads_write). Monitors have monitoring and monitoring_write, and diagnostics only reads. A read looks like google_ads(action="execute", tool_name="google_list_campaigns", arguments={...}), a change like google_ads_write(action="execute", tool_name="google_pause_campaign", arguments={...}).
Looking things up never changes an account, so an assistant that asks permission per tool can allow reads once. Every change runs through a _write tool, which asks each time and creates a proposal. search_tools finds the right tool from your own wording and returns its exact call line, and it is free. See adako.ai/docs/routers.
LinkedIn Ads reads are open to everyone: connect the member who administers the ad account and every report, structure and forecast tool works. A change needs that ad account added to Adako's LinkedIn application first — send the nine-digit id to support@adako.ai. The TikTok Ads tools are on the surface, but TikTok accounts cannot be connected until TikTok approves Adako's developer app.
Adako is built so that an assistant can be useful without being dangerous.
| Rule | What it means |
|---|---|
| Reads run immediately | Performance, structure, search terms, audiences. Nothing to approve. |
| Every write becomes a proposal | You see the object, the before and after values, and the daily cost before anything is sent. |
| Approval is yours | Confirm in the chat, or leave proposals in an inbox and approve them at adako.ai/approvals. Proposals expire after 48 hours. |
| Created objects are paused | Every campaign, ad set and ad Adako creates starts paused. You enable it yourself. |
| Almost nothing deletes | Eight tools remove something and each needs an explicit confirmation flag. Pause never routes to a delete. |
| Executed once | Each approved proposal carries an idempotency key. Approving twice reports the first result and repeats nothing. |
| Read-back on every write | The change is confirmed by reading the object back from the platform, not by trusting the response. |
| Tokens stay server-side | Your platform tokens are held encrypted by Adako and are never forwarded to the AI client. |
Details: adako.ai/docs/safety.
Two ways to authenticate:
Authorization: Bearer ak_live_your_key, where ak_live_your_key is replaced by the whole key you copied, prefix included and nothing around it. Use it for clients that read a static config file.Pick your client.
Pro and Max: Settings → Connectors → Add custom connector. Paste the URL, click Add, then Connect and sign in.
Team and Enterprise: an owner adds it first under Organization settings → Connectors → Add, hovers Custom, chooses Web, and pastes the URL. Members then connect it from their own Settings → Connectors.
https://adako.ai/mcp
The number of custom connectors you can add depends on your Claude plan.
Same Connectors settings as Claude.ai — add the custom connector with the URL above, then sign in when prompted. Desktop shares your Claude account, so a connector added on the web is available here too. Full guide: clients/claude-desktop.md.
claude mcp add --transport http adako https://adako.ai/mcp
Then run /mcp inside a session and pick adako to sign in through the browser.
Add it once for every project with --scope user:
claude mcp add --transport http adako https://adako.ai/mcp --scope user
API-key variant, no browser step:
claude mcp add --transport http adako https://adako.ai/mcp \
--header "Authorization: Bearer ak_live_your_key"
There is also a plugin that installs the server, the skills, a setup command and an operator agent in one step:
/plugin marketplace add ruslan2027/adako-mcp
/plugin install adako@adako /adako-setup
See clients/claude-code.md and plugin/.
Adako as the connection name and https://adako.ai/mcp as the MCP server URL. Add a short description, choose the public endpoint connection option, and click Create.Full guide: clients/chatgpt.md.
One command, idempotent, and it leaves your other servers alone:
node install/cursor.mjs # the home-folder .cursor/mcp.json
node install/cursor.mjs --project # .cursor/mcp.json in this repository
Or write the file yourself:
{
"mcpServers": { "adako": { "url": "https://adako.ai/mcp" } } }
Full file: clients/cursor/mcp.json. Guide: clients/cursor.md.
This repository is also a Cursor plugin, for the Cursor Marketplace: .cursor-plugin/plugin.json adds the server and the skills in skills/.
codex mcp add adako --url https://adako.ai/mcp
codex mcp login adako
Or run the installer, which rewrites one table in the Codex config (C:\Users\ \.codex\config.toml on Windows or /Users/ /.codex/config.toml on macOS) and leaves the rest of the file untouched:
node install/codex.mjs # API key from $ADAKO_API_KEY
node install/codex.mjs --oauth # sign in with codex mcp login instead
Full file: clients/codex/config.toml. Guide: clients/codex.md.
node install/windsurf.mjs
Or add the block by hand to C:\Users\ \.codeium\windsurf\mcp_config.json on Windows or /Users/ /.codeium/windsurf/mcp_config.json on macOS:
{
"mcpServers": { "adako": { "serverUrl": "https://adako.ai/mcp" } } }
Full file: clients/windsurf/mcp_config.json. Guide: clients/windsurf.md.
On a computer, open gemini.google.com/apps, or Settings → Connected apps, then scroll to Custom apps at the bottom, choose Add a custom app, and paste the URL:
https://adako.ai/mcp
Click Next and sign in. Leave the credential fields under Advanced features empty: Adako registers itself. In a chat, type @ and pick Adako.
Guide: clients/gemini.md. Custom apps are still rolling out, with conditions Google lists: a personal Google Account, English, the United States, 18 or over.
All three read one file, so Adako is added once. In the desktop app: Settings → Customizations, then Open MCP Config. In the IDE: the agent side panel, … → MCP Servers. In the CLI: /mcp, or the file itself — C:\Users\ \.gemini\config\mcp_config.json on Windows or /Users/ /.gemini/config/mcp_config.json on macOS (Linux: /home/ /.gemini/config/mcp_config.json). Use .agents/mcp_config.json for one project. After saving, press refresh beside _Installed MCP Servers_ and click Adako to sign in.
{
"mcpServers": { "adako": { "serverUrl": "https://adako.ai/mcp" } } }
Antigravity signs in through the browser on the first call. Guide: clients/antigravity.md.
Gemini CLI stopped serving free and Pro accounts on 18 June 2026 and now runs only on paid Gemini and Gemini Enterprise API keys. If you are still on it, the older spelling works: httpUrl in .gemini/settings.json in your home folder, with the extension manifests gemini-extension.json and clients/gemini-cli/gemini-extension.json. Separately, agy plugin import gemini carries an existing setup into Antigravity.
只显示了开头部分;其余内容请在仓库中阅读