MCP YouTube Transcript
An MCP server retrieving transcripts of YouTube videos
Beschreibung vom Entwickler (englisches Original)
Google, Meta, LinkedIn and ChatGPT Ads for AI assistants. Every change needs your approval.
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://adako.ai/mcpFühre das in deinem Terminal aus
claude mcp add --transport http ads https://adako.ai/mcpIn .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"ads": {
"url": "https://adako.ai/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": {
"ads": {
"type": "http",
"url": "https://adako.ai/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://adako.ai/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.
Die Tool-Liste dieses Servers haben wir noch nicht gelesen; wir prüfen die Endpunkte reihum.
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 adako.ai 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
Noch nicht geprüft; wir prüfen die Endpunkte reihum
Noch nicht geprüft; wir prüfen die Endpunkte reihum
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 1 von 1 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.3.2) kam vor 38 Tagen 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.
アダコ · 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.
Nur der Anfang wird gezeigt; den Rest findest du im Repo