Social Post Flow
com.socialpostflow由 socialpostflow.com 發布官方發布者v1.0.0更新於 Oct 30, 2026
Schedule and publish social media posts to Facebook, X, LinkedIn, Instagram, Threads and more.
概覽
遠端 MCP 伺服器,讓助理在 Facebook、X、LinkedIn、Instagram、Threads 等平台排程並發佈社群貼文。
- 可以做什麼
- 建立文字、連結、圖片、Story、Pin 或 TikTok/Google 等類型的貼文,可同時指定多個已連結帳號
- 以立即發佈、指定未來時間,或加入佇列開頭/結尾的方式排程
- 列出已連結的社群帳號,並依貼文類型篩選
- 列出、檢視與刪除貼文,包括在發佈前取消已排程的貼文
- 查看已驗證帳號的個人資料、訂閱狀態與統計數據
- 適用情境
- 適合讓助理在對話中草擬、排入佇列並跨多個平台發佈社群內容,或不必開啟網頁應用程式就能管理既有的排程貼文。
- 執行需求
- 透過 streamable HTTP 連線的遠端端點,使用 OAuth 登入;需要具備 API 存取權限的 Social Post Flow 帳號。搭配的 CLI(MCP 伺服器本身不需要)需 Node.js 18 或更新版本,以及個人存取權杖,可透過 SOCIALPOSTFLOW_API_TOKEN 環境變數提供或由其 setup 指令儲存。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Social Post Flow,將其新增到工作區。
- 連接 所需的 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
- 為需要使用其工具的對話啟用該服務。
Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
交給代理程式安裝
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/com.socialpostflow%2Fmcp/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。其他 MCP 客戶端
把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。
{
"mcpServers": {
"social-post-flow": {
"type": "http",
"url": "https://app.socialpostflow.com/mcp"
}
}
}README
Social Post Flow CLI
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.
Pick your install
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.
Install as a Claude Code plugin
The plugin bundles the MCP server config and a Claude-native skill in one install:
Or, once approved in the community marketplace:
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.
Install as a skill
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/):
Multi-agent install (Cursor, Codex, Warp, Cline, OpenCode, etc.):
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.
Install as a CLI
Globally via npm:
Or run directly via npx without installing:
Or clone the repo and run the script directly (zero dependencies):
Requires Node.js 18 or later (for built-in fetch).
Authentication
You need a Social Post Flow account with API access. Grab your personal access token from your profile page, then:
This verifies the token against the API and saves it to ~/.socialpostflow/credentials.json (chmod 600).
Alternatively, set the environment variable:
Quick start
Commands
spf post options
See agent-skill/socialpostflow/SKILL.md for the full post-type rules (what each type requires and forbids).
All output is JSON
Every command writes JSON to stdout. Errors write JSON to stderr with a non-zero exit code:
Environment variables
Examples
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
Troubleshooting
"Not authenticated" — Run spf setup --key <token> 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.
License
MIT — see LICENSE.
Links
- Social Post Flow: socialpostflow.com
- API documentation: socialpostflow.com/documentation/api
- MCP documentation: socialpostflow.com/documentation/mcp
- WordPress Plugin: wordpress.org/plugins/social-post-flow
- Issues / feedback: github.com/socialpostflow/socialpostflow-cli/issues
來源:README.md,提交 1781c3b
工具
0版本歷史
1- v1.0.0最新Oct 30, 2026
評分
已滿足適用檢查項的 85%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通必需25 分
- 已宣告認證方式必需10 分
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分