MCP YouTube Transcript
An MCP server retrieving transcripts of YouTube videos
作者提供的说明(英文原文)
Define, ship & query your analytics tracking from one source of truth, trusted by humans and agents.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://mcp.avo.app/mcp在终端中运行这条命令
claude mcp add --transport http avo https://mcp.avo.app/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"avo": {
"url": "https://mcp.avo.app/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"avo": {
"type": "http",
"url": "https://mcp.avo.app/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://mcp.avo.app/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 avohq 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.0.0)于5个月前进入注册中心。
支持 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、图片和脚本已被移除。链接会离开本站。
mcp-name: io.github.avohq/avo
The Avo MCP server (https://mcp.avo.app/mcp) lets Claude, Codex, Cursor, Gemini, and other MCP clients read and edit your Avo tracking plan. This repo also ships Agent Skills and a Claude Code plugin that guide effective use of the server.
Each skill is a self-contained directory with a SKILL.md (instructions + metadata) and bundled resources. Claude loads them automatically when relevant to guide effective use of the Avo MCP server's tools (describe_tool, search, get, save_items, workflow, and the branch tools).
The Avo MCP server is a remote, OAuth-protected HTTP server at https://mcp.avo.app/mcp. Add it to your MCP client:
Claude Code (CLI)
claude mcp add --transport http avo https://mcp.avo.app/mcp
You'll sign in through the browser on first use. The first time you make a change, you'll also get a one-time read → write re-auth prompt.
Claude.ai / Claude Desktop
Add a custom connector pointing at https://mcp.avo.app/mcp (Settings → Connectors → Add custom connector). Authenticate when prompted.
Cursor and other MCP clients
Add a remote (streamable HTTP) MCP server to your client's config:
{
"mcpServers": { "avo": { "type": "http", "url": "https://mcp.avo.app/mcp" } } }
If you install the Claude Code plugin (below), it registers this server for you — these steps are for connecting the server directly (other clients, or Claude Code without the plugin).
data-designer — Work with an existing Avo tracking planExplore, search, and design against an existing Avo tracking plan: look events / properties / metrics up by name, id, meaning, or structural filter; review, prioritize, and implement branches; design tracking for a new feature or PRD against what already exists; make small branch edits; and combine Avo with a connected data MCP (Amplitude, Mixpanel, PostHog, BigQuery, Snowflake, Databricks, Redshift) to diagnose tracking gaps.
skills/data-designer/data-designer-new-plan — Bootstrap a brand-new Avo tracking planBootstrap a tracking plan from scratch in an empty or near-empty workspace: run a purpose meeting (problems, goals, metrics, key funnels), agree a naming convention, and seed the first categories and start → milestone → complete events with event / user / system properties and constraints — then create a branch.
skills/data-designer-new-plan/This repo is also a Claude Code plugin marketplace. Installing the avo plugin bundles both skills and registers the Avo MCP server (https://mcp.avo.app/mcp) in one step:
claude plugin marketplace add avohq/avo-mcp
claude plugin install avo@avo-mcp
The plugin's layout:
.claude-plugin/marketplace.json — the marketplace manifest (lists the avo plugin).claude-plugin/plugin.json — the avo plugin manifest.mcp.json — registers the Avo MCP serverskills/ — the two skills, auto-discovered when the plugin is installedTo use the skills without the plugin / MCP registration, copy a skill directory into your personal or project skills folder:
cp -R skills/data-designer ~/.claude/skills/data-designer
cp -R skills/data-designer-new-plan ~/.claude/skills/data-designer-new-plan
All writes happen on a branch, never on main; the MCP never merges — merging a branch into main is always a human step in the Avo web app.
The tool definitions the server sends on connect are kept short so that every MCP client sees every tool. The fields each item type accepts are fetched on demand: call describe_tool() for an overview of every tool and describe_tool(tool:"save_items", type:" ", op:" ") for the fields of an item type before writing it. Each save_items item has the shape {op, type, id?, name?, tempId?, fields?} with snake_case item types (event_variant, property_bundle, group_type, …); the camelCase spellings still work but are deprecated.
This repo is the source of truth for these skills. Avo's internal tooling syncs them from here (there's no build step to run in this repo). For the canonical, always-current Avo MCP tool list, see the Avo MCP tools reference.
The contents of this repository — the data-designer and data-designer-new-plan Agent Skills and the plugin manifest and configuration — are released under the MIT License.
This covers only the files in this repository. It grants no rights to the Avo MCP server (https://mcp.avo.app/mcp), the Avo web application, Avo SDKs, or any other Avo software or service — these are separate works, governed by Avo's Terms of Service and your agreement with Avo.