mixpost-mcp-server
Related Servers
Alternatives to mixpost-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables managing social media accounts, profiles, posts, and media via Zernio's API through natural language.51 npmMIT

@posteahora/mcpofficial
AlicenseAqualityCmaintenanceEnables AI agents to create, schedule, and publish social media posts across Instagram, X/Twitter, LinkedIn, Threads, Facebook, and other platforms via the PosteAhora API.1520 npmMIT- AlicenseAqualityBmaintenanceProvides AI assistants with access to the RecurPost API to manage social media accounts, schedule posts, and organize content libraries. It enables users to automate recurring posts, track engagement metrics, and generate social media content through natural language.1033 npm1MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to publish, schedule, and manage social media posts across X (Twitter), Instagram, and Threads through the Sociona API. Supports immediate posting, scheduling, analytics, and account management with natural language commands.612 npmMIT
- AlicenseNot gradedqualityFmaintenanceProvides full Sprout Social API coverage for AI-powered social media management, enabling analytics, inbox messages, listening, publishing, media uploads, and support cases through natural language.95 npm2MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to upload and schedule videos, images, carousels, and text posts across 17 social platforms, read analytics, and reply to comments through a hosted OAuth connection.MIT
TDQS
Scored across 20 tools
Most tools target distinct resource-action pairs (posts, tags, media, accounts). The only potential confusion is between mixpost_schedule_post and mixpost_add_post_to_queue, but their descriptions clarify the difference (specific time vs. queue placement). Overall, tool boundaries are clear.
All tools follow a consistent mixpost_<verb>_<noun> pattern using snake_case and a common prefix. Verbs like list, get, create, update, delete are used uniformly across resources, making the API predictable and easy to navigate.
With 20 tools, the server is slightly heavy but appropriate given the breadth of the domain (posts, media, tags, accounts). The tool count reflects the need for CRUD operations on multiple resources without becoming excessive or unwieldy.
The tool surface provides thorough coverage for posts (create, update, approve, schedule, queue, delete, bulk delete) and full CRUD for tags. Minor gaps exist, such as missing account management (creation/deletion) and media upload, but these are likely handled outside the MCP server scope.