Markaestro
OfficialRelated Servers
Alternatives to Markaestro
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables posting and managing content across 13+ social media platforms with scheduling, analytics, AI generation, and approval workflows through natural language.2MIT
- FlicenseAqualityCmaintenanceSchedule and manage social media posts across Facebook, Instagram, Twitter/X, LinkedIn, YouTube, TikTok, and Pinterest directly from Claude.10-
- AlicenseAqualityDmaintenanceAI-powered social media posting across 14 platforms. Post to Twitter, Instagram, TikTok, Facebook, LinkedIn, YouTube and more with one command. AI adapts content per platform, schedules posts, and generates 30-day content calendars.6MIT

AdaptlyPostofficial
AlicenseAqualityBmaintenanceGives 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- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to draft, schedule, and publish social media content, generate AI text and image variations, analyze performance, and automate social workflows.MIT
- AlicenseAqualityCmaintenanceEnables publishing to Facebook, Instagram, and YouTube through official APIs using your own OAuth credentials, with support for images, videos, Reels/Stories, and scheduled posts.6MIT
TDQS
Scored across 34 tools
Most tools target a distinct resource+action and the descriptions add rich disambiguation cues (e.g. the four analytics tools explicitly cross-reference each other and explain when to use which). The main risks are near-homograph names like create_post vs create_posts, and list_posts vs list_post_analytics, plus the four analytics reads that require careful reading to separate.
Nearly everything follows a predictable snake_case verb_noun pattern (list_posts, get_post, create_evergreen_queue, activate_evergreen_queue, get_job_run). Minor deviations: bulk_posts drops the verb, and create_posts/create_post differ only by plurality, which is a naming hazard rather than a convention break.
34 tools is heavy for the surface; the broad domain (posts, media, evergreen, analytics, brands, job runs) justifies many, but several could be consolidated (get_job_run/list_job_runs, four analytics tools, preview vs create vs activate evergreen). It sits at the upper bound of what an agent can hold in working memory.
Strong lifecycle coverage: full post CRUD plus publish, bulk actions, batch create, manual-post marking, media upload/read, evergreen queue lifecycle, brands/destinations/job runs, and deep analytics. Gaps are minor: no media deletion, no post duplication, and no channel-connection management (deferred to Markaestro itself by design).