
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 分
请在仓库或注册中心条目中声明许可证。