Postking MCP server

PostKing MCP Server

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 (loginstart, logincomplete, 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:

1. Open Claude Desktop → Settings (gear icon) → Developer → Edit Config
2. This opens claudedesktopconfig.json in your default editor
3. Paste the following and save:

{
  "mcpServers": {
    "postking": {
      "command": "npx",
      "args": ["-y", "postking-mcp"]
    }
  }
}

1. Restart Claude Desktop

Option B — Edit the config file directly:

Open ~/Library/Application Support/Claude/claudedesktopconfig.json (macOS) or %APPDATA%\Claude\claudedesktopconfig.json (Windows) in any text editor, paste the same JSON above, and save.

Once restarted, tell Claude: "Login to PostKing"

Claude Code (CLI)

claude mcp add postking -- npx -y postking-mcp

Hermes

npm i -g postking-mcp
hermes mcp add postking --command postking-mcp

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:

1. Tell Claude: "Login to PostKing"
2. Claude calls login_start → shows a URL and short code
3. Visit the URL in your browser, log in, approve
4. Tell Claude: "Done"
5. 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.

Shortened. The full README is on GitHub.