PostKing MCP Server
Related Servers
Alternatives to PostKing MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server to manage social media accounts from AI assistants, enabling post creation, scheduling, publishing, and media uploads across multiple platforms.1321 npm1MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for AI-driven social media automation, enabling campaign scheduling, content management, and TikTok posting through high-level tools.46 npmMIT
- AlicenseAqualityCmaintenanceMCP server for QPost that lets AI agents schedule and publish video/image posts to YouTube, TikTok, and Instagram via QPost's REST API.736 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server for managing social media posts across multiple platforms using the Postiz API. Supports creating, updating, deleting posts, and generating videos.35 npm3MIT
- FlicenseAqualityDmaintenanceAn MCP server that automatically generates technical blog posts using AI (Gemini and Claude), supporting various input types, styles, and collaborative workflow.10-
- AlicenseNot gradedqualityBmaintenanceA hosted MCP server that lets AI assistants schedule and publish social media posts across Instagram, TikTok, X, LinkedIn, YouTube, Pinterest, Facebook, Telegram, Threads, and Bluesky. It provides tools for managing accounts, posts, media, and analytics, including post previewing before publishing.1MIT
TDQS
Scored across 243 tools
Despite detailed descriptions, many tools occupy overlapping roles: generate_side_page and seo_generate_side_page are near-duplicates, list_jobs/list_operations/get_job offer three ways to inspect async work, and upload_asset overlaps with the upload_asset_begin/chunk/finish flow. An agent selecting from 243 tools will frequently face ambiguous choices.
Names are mostly snake_case verb_noun, but conventions shift across and within domains: seo_roadmap_get vs seo_list_roadmap vs get_seo_roadmap, list_blogs vs list_publications, and unprefixed tools like whoami and health break the pattern. It is readable but not a coherent naming system.
243 tools is far beyond a reasonable MCP surface, forcing massive context consumption and making it hard for an agent to even notice the right tool. This is an extreme scope mismatch for a single server regardless of how many features PostKing has.
Coverage is remarkably broad: posts, blogs, SEO pipeline, landing pages, side pages, assets, competitors, storylines, knowledge, and billing all have lifecycle support. Minor gaps exist, such as no direct update-post-content tool and asymmetries between soft-delete/restore flows, but they are workarounds rather than dead ends.