MCP YouTube Transcript
An MCP server retrieving transcripts of YouTube videos
Beschreibung vom Entwickler (englisches Original)
Server-side conversion tracking for Meta, TikTok, etc. Set up tracking and ask about events.
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://api.pixelflow.so/mcpFühre das in deinem Terminal aus
claude mcp add --transport http pixelflow https://api.pixelflow.so/mcpIn .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"pixelflow": {
"url": "https://api.pixelflow.so/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": {
"pixelflow": {
"type": "http",
"url": "https://api.pixelflow.so/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://api.pixelflow.so/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 pixelflow.so 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 (2.0.1) kam vor 3 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.
PixelFlow is server-side conversion tracking for Meta and TikTok. No tag manager, and no developer needed.
The MCP server lets your AI agent do two things from the chat:
The server URL is https://api.pixelflow.so/mcp.
The client opens the PixelFlow login and the customer clicks Allow. No token is pasted.
| Reads | Events, attribution, journeys, and site status. Reads do not need approval. |
| Edits | Creating, editing, or deleting a trigger, a blocking rule, a site field, a pixel label, or an integration. Show the change and wait for one approval. |
| Never touches | The customer's ad account. The server does not change campaigns, budgets, or ads. |
| Never touches | The customer's website. The server does not edit it. A coding agent that already has the repo may place the snippet the install tool returned. |
| Never touches | Tokens, keys, and passwords. They are not returned and must not be typed into the chat. |
| Never touches | A visitor's raw email, phone, or name. Hashed values stay hashed. IP stays masked unless the customer asks for the full value. |
| Never touches | Deleting a Site or a Pixel. Those tools do not exist. |
| Tool | What it does | Access |
|---|---|---|
list_sites | List the websites the signed-in user can access in PixelFlow: each site's site_id, domain, platform, currency, whether the user can edit it, and the workspace it belongs to with the user's role there. | Reads |
list_supported_values | List the names PixelFlow supports and other tools accept: the platforms a site can run on, the ad platforms events can be sent to, the integrations that report conversions, the supported events, and the traffic sources events are attributed to. | Reads |
get_site_status | Get the setup and health state of one site: its settings (domain, platform, currency, ecommerce flags), whether the PixelFlow script or plugin is installed, connected pixels and integrations, blocking rules, consent mode, the last event received of each type, which Get Started checklist items are done, and the plan, limits, and usage of its workspace. | Reads |
get_install_instructions | Get step-by-step instructions the user follows on their website or in their ad platform's ads manager, for one task: installing PixelFlow, adding UTM parameters to ad links, removing an ad platform's own pixel code (such as the Facebook pixel) that was added before PixelFlow and would count events twice, or removing PixelFlow. | Reads |
verify_tracking | Check that tracking works on one site by loading one of its pages in a headless browser and reading the events received since checked_from. | Loads the customer's site |
get_connect_link | Create a one-time link to the PixelFlow dashboard page for a step that needs a browser sign-in or a secret. | Edits |
update_pixel | Change the label or the test event code of a connected ad platform pixel. | Edits |
update_integration | Change the settings of an integration connected to a site, such as Stripe or Calendly. | Edits |
disconnect_integration | Disconnect an integration such as Stripe or Calendly from a site and return which one was removed. | Deletes |
create_site | Add a new website to a PixelFlow workspace and return the saved site with its site_id. | Edits |
update_site | Change settings on a site (domain, platform, currency, ecommerce flags, or Get Started checklist items) and return the saved site. | Edits |
get_overview | Get tracking totals for one site over a date range: the count of each event, such as Purchase or Lead, revenue, events delivered and failed per pixel, events blocked by consent or bot detection, event counts per day or week, and, for the newest 500 conversions in the range, how many carried a hashed email or phone. | Reads |
get_attribution | Get revenue and conversions for one site over a date range, broken down by traffic source, campaign, ad set, or ad, using PixelFlow's website attribution (the UTM tags and referrer of the converting visit). | Reads |
get_journeys | Get visitor journeys on one site, one row per visitor with an event in the date range. | Reads |
list_events | List the tracked events on one site as rows, up to 100 per call. | Reads |
get_event_payloads | Get the payload (request body) PixelFlow sent to each ad platform for up to 25 events by id. | Reads |
get_blocked_events | List the events PixelFlow did not send to ad platforms on one site because of consent or bot detection, up to 100 per call. | Reads |
list_triggers | List every conversion trigger on one site, including integrations such as Stripe. | Reads |
suggest_triggers | Suggest the conversion triggers a site still needs: which events are tracked today, and one proposal per gap. | Reads |
create_trigger | Create a trigger that sends an event to the site's ad platforms when a visitor submits a form, clicks an element, or loads a page, and return the saved trigger with its trigger_id. | Edits |
update_trigger | Change an existing trigger of type url, click, or submit and return the saved trigger. | Edits |
delete_trigger | Delete a trigger of type url, click, or submit and return the id and type of the removed trigger. | Deletes |
save_blocking_rule | Save the blocking rule for one event on a site, such as Purchase, or for all events (AllEvents). | Edits |
delete_blocking_rule | Delete the blocking rule for one event on a site, such as Purchase, or the AllEvents rule. | Deletes |
close_get_started | Check the site's Get Started checklist and mark as done the items PixelFlow can confirm from its data. | Edits |
The full description, hints, arguments, and result fields of every tool are in TOOLS.md, generated from the server.
Guide: https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp
Connect:
Start:
Custom connectors work on every Claude plan (free plans are limited to one). On Team and Enterprise plans an owner adds the connector first, under Organization settings, then Connectors.
Guide: https://code.claude.com/docs/en/mcp
Connect:
claude mcp add --transport http --scope user pixelflow https://api.pixelflow.so/mcp
Start:
Guide: https://developers.openai.com/api/docs/mcp
Connect:
Start:
Connect:
Start:
Guide: https://cursor.com/docs/mcp
Connect:
"pixelflow": {
"url": "https://api.pixelflow.so/mcp" }
Start:
Connect:
codex mcp add pixelflow --url https://api.pixelflow.so/mcp
Start:
Guide: https://docs.lovable.dev/integrations/custom-mcp
Connect:
Start:
Chat connectors are personal to you and are not part of your published app. If MCP server is greyed out, a workspace admin has turned custom servers off.
Connect:
Start:
Works with Gemini CLI, VS Code, Windsurf, Zed and anything else that speaks MCP over HTTP.
PixelFlow never asks you to paste a token, a key or a password: you sign in with your normal login and click Allow. Once connected, the tool shows under AI tools in your Pixel
Nur der Anfang wird gezeigt; den Rest findest du im Repo