MCP YouTube Transcript
An MCP server retrieving transcripts of YouTube videos
作者提供的说明(英文原文)
Ask about any customer and get one matched record across CRM, billing, support and product data.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://mcp.outlit.ai/mcp在终端中运行这条命令
claude mcp add --transport http outlit https://mcp.outlit.ai/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"outlit": {
"url": "https://mcp.outlit.ai/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"outlit": {
"type": "http",
"url": "https://mcp.outlit.ai/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://mcp.outlit.ai/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过域名 outlit.ai 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
在 1403 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.1.0)于昨天进入注册中心。
支持 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、图片和脚本已被移除。链接会离开本站。
Outlit helps customer-success teams protect and grow long-tail revenue. It connects customer data, monitors for churn risk and expansion opportunities, and brings attention items with supporting evidence to your team.
Start with the product guides for guided setup and your first attention item. For programmatic access, use the developer and agent guide.
This repository contains the public SDK and developer integration packages for Outlit: browser, server, CLI, tool contract, and Pi packages for sending customer signals to Outlit and querying customer context from agent workflows. It is not the hosted remote MCP server implementation; use the canonical Outlit-owned discovery endpoints below for MCP, API, and agent metadata.
This monorepo contains these packages under the @outlit scope:
Use these canonical resources for citations, schema-driven clients, and agent setup instead of copying generated specs or server metadata into this repository:
| Surface | Canonical URL | Purpose |
|---|---|---|
| Documentation | https://docs.outlit.ai | Product guides plus SDK, CLI, API, MCP, and customer context documentation |
| Docs index for agents | https://docs.outlit.ai/llms.txt | Machine-readable map of documentation pages |
| Product resource index | https://www.outlit.ai/llms.txt | Agent-facing map of SDK packages, docs, API contracts, MCP, CLI, Pi, and skills |
| OpenAPI spec | https://docs.outlit.ai/openapi.json | Canonical OpenAPI contract for public API and ingest surfaces |
| API catalog | https://www.outlit.ai/.well-known/api-catalog | Linkset for API, MCP, OAuth, docs, and support discovery |
| AI catalog | https://www.outlit.ai/.well-known/ai-catalog.json | Agentic Resource Discovery catalog for Outlit API, MCP, skills, and SDK resources |
| MCP Registry listing | https://registry.modelcontextprotocol.io/v0.1/servers?search=ai.outlit/outlit | Official MCP Registry search surface for ai.outlit/outlit |
| MCP server metadata | https://mcp.outlit.ai/.well-known/mcp/server.json | Runtime metadata for the hosted remote MCP server |
| MCP server card | https://mcp.outlit.ai/.well-known/mcp/server-card.json | Runtime discovery card for the hosted remote MCP server |
| MCP docs | https://docs.outlit.ai/ai-integrations/mcp | Connect remote MCP clients with workspace URLs and OAuth |
| Agent skills | https://docs.outlit.ai/ai-integrations/skills | Official outlit and outlit-sdk skill installation guidance |
The hosted MCP server and OAuth metadata live on mcp.outlit.ai; this SDK repo is the public package and developer integration surface.
Choose the package that matches the integration surface:
| Package | Install | Use when |
|---|---|---|
@outlit/browser | npm install @outlit/browser | Browser apps, React, Next.js, Vue, Nuxt, SvelteKit, Angular, Astro, and script-tag tracking |
@outlit/node | npm install @outlit/node | Node.js servers, API routes, jobs, webhooks, CLIs, desktop main processes, and native JavaScript runtimes |
@outlit/core | npm install @outlit/core | Lower-level custom SDK implementations that do not need browser or Node runtime helpers |
@outlit/cli | npm install -g @outlit/cli | Terminal access to Outlit customer intelligence and setup workflows |
@outlit/tools | npm install @outlit/tools | Custom API or agent integrations that need typed Outlit tool gateway contracts and client helpers |
@outlit/pi | npm install @outlit/pi | Pi agents that need Outlit customer intelligence tools and skill guidance |
| Rust crate | cargo add outlit | Rust backends, CLIs, and Tauri backends |
Tracking SDK examples:
# For browser applications
npm install @outlit/browser
npm install @outlit/node
npm install @outlit/core
import { Outlit } from '@outlit/browser'
const outlit = new Outlit({ publicKey: 'pk_xxx', trackPageviews: true, trackForms: true, })
// Identify a user outlit.user.identify({ email: 'user@example.com', traits: { name: 'John Doe' }, customerId: 'cust_123', // Your app's account/workspace/customer ID customerTraits: { plan: 'pro' }, })
// Track events outlit.track('button_clicked', { button_id: 'signup', page: '/homepage', })
// Track meaningful product activity. Core derives lifecycle stages from // ordinary events, including your selected activation event. outlit.track('onboarding_completed', { flow: 'self_serve' })
import { init, track, user } from '@outlit/browser'
// Initialize once at app startup init({ publicKey: 'pk_xxx' })
// Then use anywhere track('page_viewed', { page: '/home' }) user().identify({ email: 'user@example.com', customerId: 'cust_123', // Your app's account/workspace/customer ID }) track('subscription_upgraded', { plan: 'pro' })
import { OutlitProvider, useOutlit } from '@outlit/browser/react'
// Wrap your app function App() { return (
) }
// Use in components function MyComponent() { const { track } = useOutlit()
return ( track('onboarding_completed')}> Click me
) }
import { Outlit } from '@outlit/node'
const outlit = new Outlit({ publicKey: 'pk_xxx', })
// Track server-side events (requires identity) outlit.track({ customerId: 'cust_123', // Your app's account/workspace/customer ID eventName: 'api_request', properties: { endpoint: '/api/users', method: 'GET', status: 200, }, }) // customerId-only track events are valid immediately. // When you later call identify() with the same customerId and an email, // Outlit can link that account/workspace to the customer resolved from email.
// Identify a user outlit.user.identify({ email: 'user@example.com', traits: { plan: 'pro' }, customerId: 'cust_123', // Your app's account/workspace/customer ID customerTraits: { plan: 'pro' }, })
// Track ordinary product events. Billing status comes from verified // integrations such as Stripe, not authoritative SDK commands. outlit.track({ customerId: 'cust_123', eventName: 'subscription_upgraded', properties: { plan: 'pro' }, })
// Flush events before shutdown await outlit.flush()
@outlit/piThis project uses a modern monorepo setup with the following tools:
# Install dependencies
bun install
bun run build
bun run test
bun run lint
bun run typecheck
bun run format
outlit-sdk/
├── .github/workflows/ # CI/CD workflows ├── examples/ │ └── pi-agents/ # Example Pi agents using @outlit/pi ├── packages/ │ ├── browser/ # Browser SDK with React bindings │ ├── cli/ # Outlit CLI │ ├── core/ # Shared types and utilities │ ├── node/ # Node.js SDK │ ├── pi/ # Pi package for Outlit tools │ ├── tools/ # Customer intelligence tool contracts │ └── typescript-config/ # Shared TypeScript configs ├── package.json # Root package with workspace config ├── bun.lock # Bun lockfile ├── turbo.json # Turbo build configuration └── biome.json # Biome linter/formatter config
When making changes that should be released, create a changeset:
bunx changeset
This will prompt you to:
The changeset file will be committed with your PR and used to generate changelogs on release.
ci.yml) - Runs on PRs: lint, typecheck, build, testrelease.yml) - Runs on main: publish canary to npm + CDN, create version PR or publish stable releasesverify-cdn-auth.yml) - Manual only: checks Workload Identity Federation exchange and CDN read access; the optional verify_write input writes then deletes one tiny test object under __compliance_checks/Stable releases are intentionally separate from SDK source merges. See docs/release-coordination.md for the Version Packages checklist and the required Core-production-before-stable-SDK order for coordinated contracts.
For maintainers setting up the repository:
| Secret | Description |
|---|---|
NPM_TOKEN | npm access token with publish permission for @outlit scope |
CDN deploys authenticate to Google Cloud via Workload Identity Federation instead of a stored service account key. Maintainers configure these repository variables:
| Variable | Description |
|---|---|
GCP_WORKLOAD_IDENTITY_PROVIDER | Full WIF provider resource name (projects/ /locations/global/workloadIdentityPools/ /providers/ ) |
GCP_SERVICE_ACCOUNT | Deploy service account email with Storage Object Admin on cdn.outlit.ai bucket |
@outlit packagesNPM_TOKEN secret in GitHubgithub-actions-cdn-deploy)cdn.outlit.ai bucket只显示了开头部分;其余内容请在仓库中阅读