postforme-mcp-server
Related Servers
Alternatives to postforme-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to post, schedule, thread, delete, and analyze social media posts across platforms like X, Bluesky, LinkedIn, and Instagram through a single MCP interface.107 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to write social posts in a brand's voice for up to four platforms, schedule or cancel them, list brands and channels, and read results, all with human approval before anything is published. Connects via OAuth or API key so posts can be planned and managed from Claude, ChatGPT, Cursor, and other MCP clients.MIT
- AlicenseNot gradedqualityDmaintenanceEnables generating, scheduling, and publishing social media posts via Claude or an agent through the MCP protocol.24 npmMIT

Chat33 MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents and MCP clients to publish and schedule posts across eight social networks, answer Instagram and Facebook DMs and comments, and build comment-to-DM automations through a hosted remote endpoint.MIT- AlicenseCqualityBmaintenanceEnables posting, scheduling, and analyzing social media content across 16+ platforms through MCP clients like Claude Desktop, Claude Code, and Cursor.55157 npmMIT
- AlicenseNot gradedqualityCmaintenanceSocial media API and MCP server for AI agents that enables publishing to X, Instagram, LinkedIn, Reddit, Bluesky, and Threads from a single endpoint.13 npmMIT
TDQS
Scored across 21 tools
Each tool targets a distinct resource and action: posts, post results, social accounts, media uploads, webhooks, and previews are all clearly separated. Even the list/single pairs like pfm_get_posts vs pfm_get_post_results are differentiated by their purpose and filters.
All tool names follow a consistent pfm_<verb>_<object> pattern using snake_case. Verbs are consistently create, get, update, delete, disconnect, and the objects are descriptive, making the API predictable and easy to navigate.
With 21 tools, the count is slightly high but justified by the server's clear scope covering three subdomains: posts, accounts, and webhooks. Each tool has a specific purpose and the count is not inflated with redundant operations.
The surface provides full lifecycle coverage for posts (create, read, update, delete, list, results, previews, media uploads), accounts (create, read, update, disconnect, auth URL, feed), and webhooks (CRUD). The only minor gap is per-post analytics, but pfm_get_account_feed covers metrics when expanded.