MCP YouTube Transcript
An MCP server retrieving transcripts of YouTube videos
作者提供的说明(英文原文)
Turn a product photo and a brief into a full ad campaign: scripts, stills, client-ready PDF.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://tools.campaignpack.ai/mcp在终端中运行这条命令
claude mcp add --transport http campaignpack https://tools.campaignpack.ai/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"campaignpack": {
"url": "https://tools.campaignpack.ai/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"campaignpack": {
"type": "http",
"url": "https://tools.campaignpack.ai/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://tools.campaignpack.ai/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日
注册名称已通过域名 campaignpack.ai 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
在 272 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(0.1.1)于今天进入注册中心。
支持 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、图片和脚本已被移除。链接会离开本站。
Turn a product photo and a couple of sentences into a finished ad campaign — without leaving Claude, Claude Code or Cursor.
You get a campaign plan, campaign ideas, ad and social scripts, a creator brief, product stills, and a client-ready PDF you could send to a customer.
Everything runs on Campaign Pack's own GPUs. No third-party model provider is in the path, which is why an unreleased product photo can go into it.
Hosted server — there is nothing to install or self-host. This repository is
the connection details and the tool reference.
Settings → Connectors → Add custom connector, and give it:
https://tools.campaignpack.ai/mcp
A browser window asks you to sign in to Campaign Pack and confirm. That is all — no token to copy.
claude mcp add --transport http campaignpack https://tools.campaignpack.ai/mcp
~/.cursor/mcp.json:
{
"mcpServers": { "campaignpack": { "url": "https://tools.campaignpack.ai/mcp", "headers": { "Authorization": "Bearer YOUR_TOKEN" } } } }
Get a token from the account panel at tools.campaignpack.ai → 🔌 Connect → Generate token. Name it after the machine you are putting it on, so you can disconnect that one later without touching the others.
You need a Campaign Pack account either way. Sign up free.
Describe the product to your assistant the way you would to a person, then ask for a campaign. Your assistant writes the brief — that is the point of this being an MCP server rather than a form. The more specific the brief, the better the pack.
I sell a stainless steel water bottle, direct to consumers, keeps drinks cold
for 24 hours. The buyer is a city commuter who already owns a bottle and wants
a better one. Here's the product photo — make me a campaign.
Runs take minutes, not seconds. The assistant starts the job, gets an id back, and polls. You can watch the same run in a browser while it works.
| Tool | What it does |
|---|---|
start_campaign | Start a pack. Returns a job id and a URL to watch it |
check_campaign | Status, recent steps, queue position |
get_pack | The finished folder, the written overview, the PDF |
upload_product_photo | Put a real product photo in your workspace first |
share_campaign | Give a teammate access while the run is still going |
list_campaign_access | Who can see a campaign |
unshare_campaign | Take access back |
answer_approval | Approve or refuse anything the run wants to send outward |
abort_campaign | Stop a run |
| Size | Time | What you get |
|---|---|---|
text | ~1 min | Plan, ideas, scripts, creator brief, PDF |
lite | ~10 min | The above plus two product stills |
The image size edits your photo rather than inventing a product, so upload a real one. Without a photo it refuses, which is deliberate: generated-from-nothing product images are not usable in an ad.
A campaign you start from your own assistant can be followed by a teammate from *theirs*, while it is still running. From their own account they can watch its progress, answer the approval prompts it raises, stop it, and read the finished pack. It is the same campaign in the same folder, not a copy.
Continuing a finished campaign with another turn is a browser job today — the tools here start a campaign and follow it, they do not add turns to one that has already run.
share_campaign(session_id, "teammate@company.com")
They need their own Campaign Pack account — sharing grants access, it does not create one.
answer_approval.