Skip to main content
Glama
markaestro

Markaestro

Official
by markaestro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Markaestro

No user-submitted related servers found.

    Related Servers

    • Ayrshare MCP Server

      vanman2024
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables posting and managing content across 13+ social media platforms with scheduling, analytics, AI generation, and approval workflows through natural language.
      2
      MIT

    • atlas-social-mcp

      chrismole310
      A
      license
      A
      quality
      D
      maintenance
      AI-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.
      6
      MIT
    • AdaptlyPost by adaptlypost

      AdaptlyPostofficial

      adaptlypost
      A
      license
      A
      quality
      A
      maintenance
      Gives 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.
      12
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 34 tools

    Disambiguation4/5

    Most tools have distinct resource+action targets (posts, media, evergreen queues, jobs). The four analytics tools (get_analytics, list_post_analytics, get_post_analytics_history, get_evergreen_analytics) and the create_post/create_posts/bulk_posts/update_post cluster overlap somewhat, but descriptions clearly scope each to a level (account vs per-post list vs single-post history) or operation, so misselection is limited.

    Naming Consistency4/5

    Strong, predictable verb_noun convention throughout (list_posts, get_post, create_post, update_post, delete_post, activate_evergreen_queue, refresh_analytics). The few deviations (bulk_posts, mark_post_posted, preview_evergreen_queue) are still readable and don't significantly break the pattern.

    Tool Count3/5

    34 tools is on the heavy side and clearly above the ideal 3-15 range. The breadth is partially justified by several genuine sub-domains (posts, media, evergreen lifecycle, analytics, jobs), but the analytics and post-creation clusters in particular could be consolidated.

    Completeness5/5

    Covers full lifecycle: post CRUD plus bulk create/reschedule, media upload/list/get, complete evergreen queue lifecycle (create/update/activate/pause/resume/preview/runs/analytics), multi-level analytics with refresh, job runs, brand profile, channel rules, destinations, and products. Only trivial gaps (e.g. no media delete), so no real dead ends for the stated domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources