Postoria MCP Server
OfficialRelated Servers
Alternatives to Postoria MCP Server
No user-submitted related servers found.
Related Servers
- 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-
- AlicenseAqualityBmaintenanceEnables interaction with Postiz for social media scheduling, content management, and analytics through MCP-compatible clients, with write and delete operations gated by environment variables.2058 npm2MIT
- AlicenseAqualityCmaintenanceMCP server for the Post for Me API, enabling publishing, scheduling, editing, deleting, and analyzing social media posts across 9 platforms from any MCP client.2711 npm1MIT
- AlicenseAqualityAmaintenanceEnables agents and scripts to drive a social publishing account through remote or local MCP tools: drafting, scheduling, approving and publishing posts, running durable background jobs with file attachments, and reading or editing Brand Memory, assets, and standing agents. Hosts can connect over OAuth with no API key, or run the stdio variant with a key for local disk tools.651MIT
- AlicenseAqualityCmaintenanceEnables MCP clients to publish, edit, delete, comment on, and reshare posts; upload images, videos, and documents; and access optional reaction, engagement, and company-Page tools when authorized.10MIT

@fopost/mcpofficial
AlicenseAqualityCmaintenanceEnables managing social media posts, accounts, and AI-powered content features from any MCP client, including scheduling, publishing, analysis, and AI caption generation.14119 npmMIT
TDQS
Scored across 14 tools
Each tool maps to a distinct resource/action: workspaces, social accounts, queues, media, and posts are cleanly separated. The three media intake paths (local file, URL, signed-URL slot) are differentiated by their descriptions, so an agent should be able to select correctly.
Tools consistently follow a snake_case verb_noun pattern (get_, list_, create_, delete_, publish_, schedule_, add_, upload_, import_, complete_). Minor variations like publish_post_now and add_post_to_queue are still predictable and fit the overall convention.
14 tools is well within the ideal 3-15 range and covers all major workflows: discovery, media ingestion, post creation, retrieval, and deletion. No tool feels redundant, and the count matches the server's domain.
The core post lifecycle is covered: create (now/scheduled/queued), read (get/list), and delete, plus media upload and workspace/account/queue discovery. Obvious gaps are an update/edit endpoint for posts and media listing/deletion, but these are not fatal to common workflows.