MCP YouTube Transcript
An MCP server retrieving transcripts of YouTube videos
作者提供的说明(英文原文)
Schedule and publish social media posts to Facebook, X, LinkedIn, Instagram, Threads and more.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://app.socialpostflow.com/mcp在终端中运行这条命令
claude mcp add --transport http socialpostflow https://app.socialpostflow.com/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"socialpostflow": {
"url": "https://app.socialpostflow.com/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"socialpostflow": {
"type": "http",
"url": "https://app.socialpostflow.com/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://app.socialpostflow.com/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过域名 socialpostflow.com 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
在 390 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.0.0)于8天前进入注册中心。
支持 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、图片和脚本已被移除。链接会离开本站。
Social media automation for AI agents — schedule posts across 12+ networks programmatically.
A zero-dependency Node.js CLI wrapper around the Social Post Flow API. Designed for use with AI agents (Claude Code, Cursor, Windsurf, Codex, OpenAI SDKs) and for shell scripting / CI workflows.
Supports: Facebook, X (Twitter), LinkedIn, Instagram (Feed + Stories), Threads, Pinterest, TikTok, Mastodon, Bluesky, Telegram, Google Business Profiles, and more.
| Using | Use this |
|---|---|
| Claude Code | The plugin (see *Install as a Claude Code plugin* below) — ships the MCP server pre-wired |
| Claude Desktop, ChatGPT Desktop | The MCP server (one-click connect, no setup) |
| Cursor, Codex, Warp, Cline, OpenCode, other agents | The skill (see *Install as a skill* below) |
| Shell scripts, CI/CD, your own tooling | The CLI (see *Install as a CLI* below) |
You can use the skill and the CLI together. The skill teaches the agent *how* to use Social Post Flow; the CLI is what the agent actually runs.
The plugin bundles the MCP server config and a Claude-native skill in one install:
/plugin marketplace add socialpostflow/claude-marketplace
/plugin install socialpostflow@socialpostflow
Or, once approved in the community marketplace:
/plugin marketplace add anthropics/claude-plugins-community
/plugin install socialpostflow@claude-community
On first use, Claude Code opens a browser for you to sign in with your Social Post Flow account and approve access — no personal access token needed.
Note: If you install the plugin, don't also add the MCP server manually in Claude Desktop settings — you'll register the same endpoint twice. Pick one.
Adds the Social Post Flow skill to your agent so it can compose and schedule posts in natural language. This is the CLI-driven skill (agent shells out to spf). Claude Code users should install the plugin above instead — it uses the MCP server, no CLI needed.
Single-command install (any agent that reads `~/.claude/skills/`):
mkdir -p ~/.claude/skills/socialpostflow && \
curl -L https://raw.githubusercontent.com/socialpostflow/socialpostflow-cli/main/agent-skill/socialpostflow/SKILL.md \ -o ~/.claude/skills/socialpostflow/SKILL.md
Multi-agent install (Cursor, Codex, Warp, Cline, OpenCode, etc.):
npx skills add socialpostflow/socialpostflow-cli
When prompted, pick the agents you want to install for.
Then ask your agent things like:
"Post this text to my X and LinkedIn accounts."
"Schedule a Monday motivation post for 9am next week."
"Queue up these three blog promos across all my channels."
The agent learns from agent-skill/socialpostflow/SKILL.md, which documents the post types, scheduling model, and common workflows.
Globally via npm:
npm install -g socialpostflow-cli
Or run directly via npx without installing:
npx socialpostflow-cli --help
Or clone the repo and run the script directly (zero dependencies):
git clone https://github.com/socialpostflow/socialpostflow-cli.git
cd socialpostflow-cli node scripts/socialpostflow.js --help
Requires Node.js 18 or later (for built-in fetch).
You need a Social Post Flow account with API access. Grab your personal access token from your profile page, then:
spf setup --key spf_xxxxxxxxxxxxxxxx
This verifies the token against the API and saves it to ~/.socialpostflow/credentials.json (chmod 600).
Alternatively, set the environment variable:
export SOCIALPOSTFLOW_API_TOKEN=spf_xxxxxxxxxxxxxxxx
# List your connected social profiles
spf profiles
spf post -c "Hello world!" -i 42
spf post -c "Big announcement coming soon" -i 42,87,103
spf post -c "Happy Monday!" -i 42 --schedule-type scheduled -s "2026-07-20T09:00:00Z"
spf post -c "Quick tip..." -i 42 --schedule-type queue_end
spf posts --status posted --order-by posted_at --order desc
spf delete 12345
| Command | Description |
|---|---|
spf setup --key | Verify and store a personal access token. |
spf whoami | Show the authenticated user's profile, subscription state, and stats. |
spf profiles [--post-type T] | List connected social profiles. Optionally filter by post type. |
spf posts [--status S] [--profile-id N] | List posts. Filter by status or profile. |
spf post -c "..." -i id1,id2 [options] | Create a post (see options below). |
spf show | Show details of a single post. |
spf delete | Delete a post. Stops it publishing if scheduled. |
spf post options| Flag | Description |
|---|---|
-c, --content | Post text. Required unless --type story. |
-i, --profile-ids | Comma-separated profile IDs (required). |
-t, --type | Post type: text (default), link, image, story, pin, tiktok, google. |
-m, --media | Comma-separated public image/video URLs. |
-u, --url | URL to attach (required for --type link). |
--first-comment | First-comment text. Not supported on Mastodon, TikTok, Telegram, Google. |
--schedule-type | immediate (default), queue_end, queue_start, scheduled. |
-s, --scheduled-at | ISO 8601 timestamp (required when --schedule-type=scheduled, must be in future). |
See agent-skill/socialpostflow/SKILL.md for the full post-type rules (what each type requires and forbids).
Every command writes JSON to stdout. Errors write JSON to stderr with a non-zero exit code:
PROFILES=$(spf profiles)
TWITTER_ID=$(echo "$PROFILES" | jq -r '.data[] | select(.provider=="x") | .id')
spf post -c "Hello from a shell script" -i "$TWITTER_ID"
| Variable | Default | Description |
|---|---|---|
SOCIALPOSTFLOW_API_TOKEN | — | Your API token. Alternative to spf setup. |
SOCIALPOSTFLOW_API_URL | https://app.socialpostflow.com/api | Override the API base URL (useful for testing). |
See examples/ for shell scripts demonstrating common workflows:
post-everywhere.sh — post the same content to all connected text-capable profilesschedule-week.sh — schedule a week's worth of posts using the queuegithub-actions.yml — publish a blog post announcement from a GitHub Action"Not authenticated" — Run spf setup --key or set SOCIALPOSTFLOW_API_TOKEN.
"HTTP 401 from API" — Your token is invalid. Get a valid token from https://app.socialpostflow.com/profile.
"HTTP 422 from API" — Validation error. The details payload tells you which field failed. Common causes: invalid post_type/schedule_type combination, scheduled time in the past, missing required media_urls for image/story/pin/tiktok posts.
"HTTP 429 from API" — Daily post limit reached for that profile. The user needs to wait or upgrade their plan.
MIT — see LICENSE.