A
licenseNot graded
qualityC
maintenanceManage Threads and Bluesky social media from AI assistants. Schedule posts, check analytics, and automate follow-up replies.
3
MIT
planvortex-mcp
OfficialRelated Servers
Alternatives to planvortex-mcp
- AlicenseAqualityDmaintenanceEnables AI assistants to manage social media accounts and CRM operations, including posting, analytics, inbox management, and customer management.22Apache 2.0
@posteahora/mcpofficial
AlicenseAqualityDmaintenanceEnables AI agents to create, schedule, and publish social media posts across Instagram, X/Twitter, LinkedIn, Threads, Facebook, and other platforms via the PosteAhora API.15213 npmMIT
PostMCP MCP Serverofficial
AlicenseAqualityBmaintenanceEnables AI assistants to manage social media publishing across platforms like LinkedIn, Twitter, Facebook, Instagram, Threads, and Bluesky.728 npmMIT
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to create, schedule, and manage social media posts across 10 platforms via a unified API.-
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to draft, schedule, and publish social media content, generate AI text and image variations, analyze performance, and automate social workflows.MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to schedule and publish social media posts to platforms like Instagram, TikTok, YouTube, LinkedIn, Facebook, X, Threads, and Pinterest using natural language.33774 npm4MIT
@crmsolid/mcp-serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI assistants to manage social DM inboxes and posting calendars across 12 platforms, allowing users to triage messages, draft replies, schedule posts, and pull stats from MCP clients.37 npm5MIT- FlicenseBqualityNot gradedmaintenanceEnables AI assistants to interact with Instagram and Facebook accounts through their APIs, supporting messaging, post management, commenting, and content creation.14-
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to launch community growth campaigns, boost posts with real engagement, and manage content campaigns via ProductClank, with OAuth and credit-based billing.11MIT
TDQS
A3.9/5.0
Scored across 31 tools
Disambiguation4/5
Most tools have clearly distinct resource+action scopes, and the verbose descriptions actively steer selection (e.g. 'prefer get_dashboard_summary over stitching tools together'). However, the analytics cluster (get_dashboard_summary, get_publication_stats, get_top_publications, get_account_metrics) and the overloaded word 'plan' (get_plan_use for the billing plan vs get_planner_templates/list_ai_plans/get_ai_plan for AI content plans) create real room for misselection.
Naming Consistency5/5
Every tool is snake_case and follows a predictable verb_noun pattern: list_*, get_*, create_*, update_*, retry_*, upload_*, send_*, reply_to_comment, hide_comment, mark_comment_read. The convention is applied uniformly across all 31 tools with no mixing of styles.
Tool Count3/5
31 tools is on the heavy side even for a broad social-media-management platform spanning publishing, AI generation, inbox, messaging, analytics and limits. Each tool appears to earn its place rather than being redundant, but the sheer count raises selection load for an agent.
Completeness5/5
Coverage is exceptionally thorough: full publication lifecycle (list/get/create/update/retry plus media upload and destinations), AI-plan lifecycle, comment and review moderation, private messaging, analytics at post/account/dashboard granularity, plus limits, capabilities and account-connection flows. The only absent operation (delete) is explicitly a deliberate design constraint, not a gap.
Maintenance
ActivityMaintained
ResponsivenessNo issues