
Scribefy
io.github.MKirovBG由 GitHub 账号 MKirovBG 发布v0.3.5更新于 Oct 24, 2026
Search YouTube, get video metadata, and extract timestamped transcripts for AI workflows.
概览
让助手搜索 YouTube、读取视频元数据与相关视频,并提取带时间戳的字幕,字幕提取按积分计费。
- 可以做什么
- Scribefy 将 Scribefy API 封装为本地 stdio MCP 服务器,提供四个工具。extract_transcript 提取 YouTube 视频字幕,返回包含标题、频道、时长、语言和带时间戳分段 Markdown。search_videos 执行 YouTube 关键词搜索,get_video_metadata 返回标题、频道、时长、观看量、上传日期和可用字幕轨道,get_related_videos 返回“接下来播放”列表。仓库还附带一个 Agent Skill,描述搜索、筛选、提取、引用的工作流程。
- 适用场景
- 适合助手需要处理 YouTube 内容的场景:总结或引用某个视频、在提取前查看有哪些字幕语言,或跨多个视频做主题调研。免费工具可先筛选候选视频,再决定是否花积分提取字幕。
- 运行要求
- 通过 npx 在本地运行,需要 Node 20 或更高版本。需要 Scribefy 账户并订阅 API + MCP 套餐(说明为每月 25 美元)以获取 SCRIBEFY_API_KEY 环境变量;没有密钥也能安装,但工具无法使用。SCRIBEFY_API_BASE 可选,用于覆盖默认 API 地址。需要能访问 Scribefy API 的网络。
安装
在 SourceWeft 中
- 打开 控制台中的 Scribefy,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
scribefy-mcp
MCP server for Scribefy — extract YouTube transcripts from Claude Desktop, Cursor, Windsurf, ChatGPT custom GPTs, or any other MCP-compatible client.
Live now — set it up in a minute below, or try the web app at scribefy.app.
Why
Most YouTube transcript tools live in browser extensions or one-off web UIs. This wraps Scribefy's API into the MCP standard so your AI assistant can pull a transcript whenever a user pastes a YouTube link — no manual copy-paste, no separate tabs.
Requirements
- Node 20+
- A Scribefy account on the API + MCP plan ($25/mo) for an API key. You can install without a key first — the MCP host registers the server cleanly and you'll get a friendly nudge when you try to use a tool — then add your key from scribefy.app/dashboard to start extracting.
Setup
Claude Desktop
Open the config file (Settings → Developer → Edit Config):
Restart Claude Desktop. The extract_transcript tool appears in the available-tools panel.
Cursor
Settings → Cursor Settings → MCP → Add new MCP server:
Windsurf
~/.codeium/windsurf/mcp_config.json:
Anywhere else
Any MCP host that supports stdio transport: spawn npx -y scribefy-mcp with SCRIBEFY_API_KEY in the env. The server speaks the standard MCP JSON-RPC over stdin/stdout.
Tools exposed
Four tools. Three are free (research toolkit); only extract_transcript charges credits.
extract_transcript
Pulls the transcript of a YouTube video.
Returns: Markdown with title, channel, duration, language, and the transcript split into segments with timestamps.
Cost: 1 credit (≤15 min) → 8 credits (2 h+). Cached transcripts are free.
search_videos
Free-text YouTube search.
Returns: Markdown list of title / channel / duration / views / URL for each result.
Cost: Free.
get_video_metadata
Title, channel, duration, view count, upload date, and available caption tracks. Does not pull the transcript.
Returns: Markdown summary plus a list of every caption track (authored ✏ or auto-generated ⚙) with its language code.
Cost: Free. Use this to inspect a video before deciding whether to extract, or to discover which caption languages are available.
get_related_videos
YouTube's "Up next" feed for a video.
Returns: Same shape as search_videos.
Cost: Free.
Tools coming in a future release
list_channel_videos and get_video_comments were planned for 0.3.0 but are deferred to 0.4.0 while we wait for upstream youtubei.js to publish fixes for YouTube's 2026 response-shape changes. Channel listing fails with HTTP 400 at the InnerTube layer, and info.getComments() is no longer attached to parsed VideoInfo. Both will return as soon as the library catches up.
Skills
The repo ships an Agent Skill (a SKILL.md your assistant loads on demand) that teaches it how to use these tools well — vet candidates with the free tools before spending credits, prefer authored captions, lean on the free transcript cache, and cite answers with timestamps.
skills/youtube-research— the YouTube research workflow: search → vet metadata → extract selectively → synthesize with[mm:ss]citations.
To use it in Claude Code, copy the folder into your project's .claude/skills/ (or ~/.claude/skills/ to have it everywhere). Open Plugins-compatible hosts detect it straight from the repo.
Configuration
Troubleshooting
SCRIBEFY_API_KEY is required
Make sure the env block is set in your MCP host's config and the host actually loads it. Some hosts strip env vars by default — check their docs.
Scribefy rejected the API key
Either the key is wrong, the key was revoked, or your subscription is no longer on the API + MCP plan. Check scribefy.app/dashboard.
Not enough credits
The tool returns the remaining balance and the cost in the error message. Top up at scribefy.app/pricing.
The tool doesn't show up in my MCP client
After editing the config, fully restart the client (not just the chat window). Tail the client's logs if available — most show MCP stderr there. The server prints scribefy-mcp: ready once it boots.
License
MIT
来源:README.md,提交 f1c81d8
工具
0版本历史
1- v0.3.5最新Sep 16, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分