
Postking Mcp
io.github.bitsandteaPublished by GitHub account bitsandteav1.1.7Updated Oct 28, 2026
PostKing MCP server for managing brands, generating posts, scheduling content, and publishing blogs.
Overview
PostKing MCP lets an assistant manage brands, generate and schedule social posts, write and publish blogs, and run SEO and marketing plans through a PostKing…
- What you can do
- Authenticate and inspect the account: device login, logout, profile and credit balance
- Manage brands: list, create, onboard from a website, set active brand, publishing platforms and content language
- Create and schedule social content: generate or draft posts, approve, schedule, reschedule, cancel, delete, bulk-fill a date range, view the calendar, reply on X
- Repurpose content and rewrite it with voice profiles; manage connected social accounts and Reddit subreddit pools and rewrites
- Write and publish blogs: publications, articles, SEO fields, CTAs, authors, categories, imports, publishing to external platforms
- Run SEO/GEO pipelines, landing and side pages, storylines, competitor analysis…
- When to use it
- Useful when you want an assistant to run marketing content end to end inside PostKing: drafting and scheduling social posts, writing and publishing blog articles, or planning SEO and campaign roadmaps. It suits teams already using PostKing rather than one-off writing tasks.
- Requirements
- A PostKing account; authentication is required, via OAuth bearer token on the remote HTTP endpoint or a device login flow on the local stdio transport. Runs as a remote endpoint or locally through npx with Node.js. No environment variables or headers are declared.
Installation
In SourceWeft
- Open Postking Mcp in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.bitsandtea%2Fpostking-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"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
Source: README.md at commit 31969f2
Tools
0Version history
1- v1.1.7LatestSep 16, 2026
Score
75% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.