
Postking Mcp
io.github.bitsandtea由 GitHub 帳號 bitsandtea 發布v1.1.7更新於 Oct 28, 2026
PostKing MCP server for managing brands, generating posts, scheduling content, and publishing blogs.
概覽
PostKing MCP 讓助理透過 PostKing 帳號管理品牌、生成並排程社群貼文、撰寫與發佈部落格,並執行 SEO 與行銷計畫。
- 可以做什麼
- 登入並檢視帳號:裝置登入、登出、個人資料與點數餘額
- 管理品牌:列出、建立、從網站自動產生品牌檔案,設定目前品牌、發佈平台與內容語言
- 創作與排程社群內容:生成或撰寫貼文、核准、排程、改期、取消、刪除、批次填滿日期區間、檢視行事曆、在 X 上回覆
- 內容再利用與語氣改寫,管理已連結的社群帳號以及 Reddit 子版池與改寫
- 撰寫與發佈部落格:出版物、文章、SEO 欄位、CTA、作者、分類、匯入及推送到外部平台
- 執行 SEO/GEO 流程、落地頁與附屬頁、storyline 行銷計畫、競品分析、知識庫、品牌事實、受眾、趨勢與範本
- 適用情境
- 適合希望助理在 PostKing 內端到端完成行銷內容的情境:起草並排程社群貼文、撰寫並發佈部落格文章,或規劃 SEO 與行銷活動路線圖。較適合已在使用的 PostKing 團隊,而非一次性的寫作任務。
- 執行需求
- 需要 PostKing 帳號;必須驗證,遠端 HTTP 端點使用 OAuth bearer token,本機 stdio 傳輸使用裝置登入流程。可作為遠端端點執行,也可透過 npx 在本機執行(需 Node.js)。未宣告任何環境變數或標頭。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Postking Mcp,將其新增到工作區。
- 連接 所需的 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
- 為需要使用其工具的對話啟用該服務。
Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
交給代理程式安裝
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/io.github.bitsandtea%2Fpostking-mcp/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。其他 MCP 客戶端
把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。
{
"mcpServers": {
"postking": {
"type": "http",
"url": "https://mcp.postking.app/mcp"
}
}
}README
PostKing MCP Server
[npm version] [License: MIT] [MCP]
The official Model Context Protocol server for PostKing — an AI-powered content platform for social media scheduling, blog publishing, and brand management.
Connect Claude (Desktop, Cursor, or any MCP client) to your PostKing account and manage your entire content operation through conversation — generate posts, schedule them, repurpose URLs into social content, write and publish blog articles, generate landing pages and side pages, run SEO / GEO research and drafting, manage your asset library and weekly posting schedule, handle domains and API keys, and more.
The server exposes 291 tools across 33 modules — full parity with the postking-cli.
Transport note: All 291 tools are registered on both transports, including on the remote HTTP transport (
mcp.postking.app). The 4 authentication tools (login_start,login_complete,logout,whoami) stay registered there too — they just explain the OAuth bearer-token model instead of running a device-code flow, since that transport is already authenticated before any tool call happens.
Quick start
Claude Desktop
Option A — Via the GUI:
- Open Claude Desktop → Settings (gear icon) → Developer → Edit Config
- This opens
claude_desktop_config.jsonin your default editor - Paste the following and save:
- Restart Claude Desktop
Option B — Edit the config file directly:
Open ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows) in any text editor, paste the same JSON above, and save.
Once restarted, tell Claude: "Login to PostKing"
Claude Code (CLI)
Hermes
Then in Hermes: "Login to PostKing".
Cursor / other MCP clients
Use the same npx -y postking-mcp command in your client's MCP server config.
Login flow
No API keys to copy. PostKing uses a device login flow:
- Tell Claude: "Login to PostKing"
- Claude calls
login_start→ shows a URL and short code - Visit the URL in your browser, log in, approve
- Tell Claude: "Done"
- Claude calls
login_complete→ saves your token to~/.postking/credentials.json
You never need to log in again. The token is permanent.
What you can do
Authentication
Available on stdio/local transport only. Remote HTTP transport authenticates via OAuth bearer token before the session is created.
Brands
Content themes
Social posts
Repurpose
Voice profiles
Social accounts
Reddit is a repurpose-to-Reddit workflow, not a scheduled publishing medium. Flow: reddit_generate_pool → reddit_get_pool → reddit_suggest → reddit_rewrite → reddit_list_posts.
Blog
SEO / GEO
Canonical flow: seo_add_seeds → seo_generate_keywords → seo_categorize → seo_generate_clusters → approve clusters → seo_generate_roadmap → review briefs → seo_approve_briefs (auto-fires article generation) → poll get_job → audit & publish.
Landing pages
Weekly schedule
Visuals (asset library)
Post visuals (cards & carousels)
Jobs (async poller)
API keys (self-service)
Domains
Writing tools
Storylines (marketing plans)
Canonical flow: storyline_create → storyline_clarify (loop) → storyline_generate_brief (poll) → storyline_get → storyline_edit_brief → storyline_confirm_brief → storyline_generate_strategy (poll) → curate line items → storyline_estimate → storyline_execute (poll).
Competitors (intelligence)
Canonical flow: competitor_probe → competitor_probe_status → competitor_probe_classify → competitor_add (poll) → competitor_analyze (poll) → competitor_list → competitor_get_comparison/recompute → competitor_get_overview/generate_overview (poll). Namespace: competitor_* (distinct from seo_competitor/seo_gap).
Knowledge base
Canonical flow: knowledge_list → knowledge_get → knowledge_create (poll get_job) → knowledge_update → knowledge_delete.
Brand truth
Atomic facts/observations about a brand (hard facts, audience truths, strategy notes, negative space, content insights, topics) used to ground generation. Brand truths are maintained by PostKing's own model — callers never write name/description/content/type/tags/personaScope directly. Canonical flow: brand_truth_list → brand_truth_get → brand_truth_create (LLM extraction decides what to store) → brand_truth_update (LLM-mediated correction, or pin toggle) → brand_truth_delete (soft) → brand_truth_restore if needed.
Audience / ICP
The brand's audience intelligence (ideal customer profile) mined from its website + onboarding. Canonical flow: get_audience → preview_audience_edit (discover valid sections) → edit_audience (async LLM ai-edit; poll get_job).
Trends and content templates
Canonical flow: trends_list → template_extract OR (template_list + template_pick) → template_create → existing post-generation tools. Note: trends_list is account-scoped (no brand required).
Billing (agent wallet + subscription)
Canonical flow (one-off): billing_list_packs → billing_topup → (Stripe Link or browser) → billing_wallet (poll until balance rises). Subscription: billing_list_tiers → billing_subscribe → (human or first-invoice Link) → subscription activates automatically.
Search performance & AI visibility
Canonical flow: search_sources (is a connector even live?) → search_performance (SEO clicks/impressions/CTR/position) → search_ai_visibility / search_ai_citations (AI-answer-engine visibility) → search_worklist ("do this next", synthesized from all of the above).
Dashboard
Guided prompts
The server ships with built-in prompts accessible from the prompt picker in Claude Desktop:
Example workflows
Repurpose a blog post to LinkedIn and X:
"Repurpose https://myblog.com/my-article for LinkedIn and X, using my brand voice"
Generate and schedule a week of content:
"Generate 7 LinkedIn posts using my growth themes, schedule them daily at 9am starting Monday"
Write and publish a blog post:
"Write a 1500-word post about AI productivity tools, publish it to my blog"
Import and repurpose existing content:
"Import the last 20 posts from https://myblog.com/feed and convert the top 5 into LinkedIn posts"
Requirements
- Node.js 18 or later
- A PostKing account — sign up free at postking.app
Publishing to external platforms
PostKing supports publishing blog articles directly to:
- WordPress (via REST API)
- Medium
- Substack
- Webflow
- Any platform with a publishing connection
Set up connections in your PostKing dashboard under Blog → Publishing Connections, then use publish_blog_article from Claude.
Development
Test locally by pointing Claude Desktop at the built file:
Environment variables
Contributing
Issues and pull requests are welcome. This repo is the MCP client layer only — it calls the PostKing API and exposes tools to any MCP-compatible AI client. If you find a bug, want to add a tool, or improve the prompts, open an issue or PR.
License
MIT
來源:README.md,提交 31969f2
工具
0版本歷史
1- v1.1.7最新Sep 16, 2026
評分
已滿足適用檢查項的 75%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通必需25 分
- 已宣告認證方式必需10 分
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分
請在儲存庫或註冊中心條目中宣告授權條款。