MCP YouTube Transcript
An MCP server retrieving transcripts of YouTube videos
作者による説明(英語の原文)
Server-side conversion tracking for Meta, TikTok, etc. Set up tracking and ask about events.
この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。
このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。
使っているAIアプリを選んで、設定をコピーしてください。
必要なもの
どのアプリを使っていますか?
上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。
ウェブ、デスクトップ、モバイルのClaudeで使えます:
https://api.pixelflow.so/mcpターミナルでこれを実行します
claude mcp add --transport http pixelflow https://api.pixelflow.so/mcpプロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます
{
"mcpServers": {
"pixelflow": {
"url": "https://api.pixelflow.so/mcp"
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
プロジェクトの .vscode/mcp.json に貼り付けます
{
"servers": {
"pixelflow": {
"type": "http",
"url": "https://api.pixelflow.so/mcp"
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
ChatGPTがつなげるのは、インターネット上のサーバーだけです:
https://api.pixelflow.so/mcpメニューの名前は、プランや時期によって少し違うことがあります。
選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。
この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
このサーバーは、ツール一覧を表示する前にサインインを求めます。
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月6日にチェック
レジストリ名はドメイン pixelflow.so で確認済みです(レジストリがドメインの所有を確認しています)
このリポジトリはまだGitHubから読み取っていません
このリポジトリはまだGitHubから読み取っていません
400ミリ秒で応答(HTTP 401)
OAuthでのサインインに対応しているため、AIアプリがログイン画面へ案内してくれます
まだチェックしていません。エンドポイントをチェックするときにツール一覧を読み取ります
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック3項目のうち3項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
レジストリには必須のキーは載っていません。ただし、最初に使うときにサインインを求めるサーバーもあります。
作者のクラウドで動きます。インストール不要でインターネット経由でつながりますが、送った内容は作者のサーバーを通ります。
GitHubリポジトリの最終更新は–、最新バージョン(2.0.1)がレジストリに届いたのは3 日前です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。URLでつながるので、リモートMCPサーバーに対応したアプリ(開発者モードのChatGPTなど)でも使えます。
同じカテゴリには:MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer
同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。
カードの見方:★ GitHubスターi3つの柱:レビュー · チェック · 利用状況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、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
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
冒頭だけを表示しています。続きはリポジトリで読めます