postifys-mcp
Related Servers
Alternatives to postifys-mcp
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityDmaintenanceEnables comprehensive social media management through Oktopost's REST API, including campaign creation, content scheduling, post management, workflow approvals, employee advocacy, and media asset handling across connected social profiles.60 npmMIT- FlicenseNot gradedqualityDmaintenanceEnables interaction with the Postiz social media management platform through MCP tools. Supports creating and managing posts, retrieving integrations, and accessing account information through multiple transport protocols.2-

@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.1513 npmMIT- FlicenseNot gradedqualityDmaintenanceEnables AI agents to create, schedule, and manage social media posts across 10 platforms via a unified API.-

Postoria MCP Serverofficial
AlicenseAqualityCmaintenanceEnables MCP-compatible clients to create, schedule, queue, inspect, and delete Postoria posts through the Postoria Public API.1418 npm1MIT- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible assistants to manage social publishing workflows, including creating drafts, uploading media, scheduling, publishing, and monitoring delivery.205 npmApache 2.0
TDQS
Scored across 17 tools
Most tools pair a specific action with a distinct resource, so post status vs media status and publish vs upload are clear. The main ambiguity is cq_overview overlapping with cq_list_tables and cq_list_jobs, but names and descriptions mostly keep boundaries clear.
All tools share the postifys_ prefix and snake_case, with a mostly consistent verb_noun pattern. Minor deviations like postifys_ping, postifys_media_upload, postifys_cq_overview, and create_or_update_job do not seriously hurt readability.
17 tools is slightly above the ideal range but justified by two clear subdomains: direct publishing/media preparation and content queue management. Each tool has a concrete purpose, though the count feels a bit heavy overall.
The core publish flow is well covered with connections, media upload, publish, and status polling. Content queue coverage is notably incomplete: items can be added, imported, and listed but not updated or deleted, and tables/jobs lack delete operations.