PostWire
Related Servers
Alternatives to PostWire
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceSocial media scheduling and publishing for AI agents. 17 validation-first tools to post to X, LinkedIn, Instagram, TikTok, YouTube, Reddit, Discord, Telegram, and more through one connected workspace.74 npm98MIT

AdaptlyPostofficial
AlicenseAqualityAmaintenanceGives AI agents the ability to schedule and publish social media posts to Instagram, TikTok, YouTube, X, LinkedIn, Facebook, Pinterest, Threads, and Bluesky. Create, schedule, and bulk-plan posts with per-platform captions, then check per-platform results and retry failures.12MIT- FlicenseNot gradedqualityDmaintenanceEnables AI agents to create, schedule, and manage social media posts across 10 platforms via a unified API.-
- AlicenseAqualityBmaintenanceSchedule, manage, generate, and analyze social posts across 11 networks (Instagram, TikTok, X, LinkedIn, YouTube, Facebook, Pinterest, Threads, Bluesky, Mastodon, Telegram) from any AI agent — 13 tools covering scheduling, media upload, AI caption generation, best-times, analytics, listening, and comments.1331 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to write, schedule, publish, and measure social media posts across LinkedIn, Bluesky, Mastodon, and YouTube, plus manage media and queue slots, through one OAuth URL with no install or API key. It also covers retrying, cancelling, restoring posts and reading analytics, with reversibility safeguards around irreversible publishing.MIT
- AlicenseAqualityBmaintenanceOfficial MCP server for PostEverywhere (posteverywhere.ai/social-media-scheduler). Let Claude, ChatGPT, Cursor or any MCP client schedule and publish posts to 13 platforms: Instagram, TikTok, YouTube, LinkedIn, Facebook, X, Threads, Pinterest, Bluesky, Telegram, Discord, WordPress and Google Business Profile. 40 tools: best-time scheduling, threads, cross-posting, campaigns, analytics.33126 npm5MIT
TDQS
Scored across 22 tools
Several clusters overlap: generate_posts, replicate_top_post, and plan_week all produce content (plan_week also schedules), while schedule_post, bulk_schedule, and create_recurring_post all queue posts in different ways. Account/brand inspection also overlaps, since my_account already returns brands and connected accounts that list_brands and get_upgrade_link/get_x_credits separately expose. The very detailed descriptions mostly disambiguate them, but an agent could still hesitate between tools in these clusters.
Names are consistently snake_case and almost all follow a verb_noun pattern (list_platforms, create_brand, schedule_post, get_post_status). A few deviate, notably my_account (noun phrase) and bulk_schedule (adjective_noun), but these are still readable and predictable.
22 tools is on the heavy side, but the server spans a broad domain: publishing, scheduling, bulk/recurring posting, media upload, video generation/quality checks, analytics, and billing/X credits. Each tool covers a distinct capability, so the surface is large but not padded.
Core flows are covered (publish, schedule, cancel, status, brands, connect links, media, analytics), but lifecycle gaps remain: no update/edit of a scheduled or recurring post, no list/manage recurring posts, no brand update/delete, and no disconnect-account tool. Agents can work around some by canceling and recreating, but these are notable missing operations.