Skip to main content
Glama
boreales

mcp-plus-tard

by boreales
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-plus-tard

No user-submitted related servers found.

    Related Servers

    • Markaestro by markaestro

      Markaestroofficial

      markaestro
      A
      license
      A
      quality
      B
      maintenance
      Schedule, publish, and measure social posts on Facebook, Instagram, TikTok, LinkedIn, Threads, Pinterest, and X for one brand or many.
      34
      MIT

    • ViralHunt MCP

      ViralHunt-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables finding trending content across social networks and scheduling/publishing posts with full lifecycle management.
      405 npm
      MIT

    • posthive

      AstaBlackClove
      A
      license
      A
      quality
      A
      maintenance
      Schedule and manage social media posts across 13 platforms (Bluesky, Threads, Instagram, LinkedIn, Mastodon, YouTube, Facebook, Pinterest, Telegram, Nostr, X/Twitter, Discord, Tumblr and more). OAuth 2.0 + PKCE, 10 tools, draft-first workflow for AI agents.
      10
      19
      AGPL 3.0

    • Timeline MCP Server

      derekalia
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to manage scheduled social media posts and content automation across multiple platforms (X/Twitter, Reddit, LinkedIn, Instagram, TikTok, YouTube). Supports organizing campaigns into tracks, scheduling posts with natural language, and automating content workflows with local SQLite storage.
      7
      6 npm
      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
    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

    A4.3/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a unique, non-overlapping purpose: validate_api_key checks authentication, list_accounts retrieves connected accounts, schedule_post creates a post, register_user creates a user, and get_user retrieves user details. No confusion between tools.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in lowercase with underscores (validate_api_key, list_accounts, schedule_post, register_user, get_user). The naming style is uniform and predictable.

    Tool Count5/5

    With 5 tools, the server offers a focused set of operations for a social media scheduling service. Each tool addresses a distinct need without redundancy, fitting well within the typical 3-15 tool range.

    Completeness3/5

    The server covers core operations (validation, listing, scheduling, user management) but lacks tools for retrieving, updating, or deleting scheduled posts. This is a notable gap for a scheduling domain, preventing full lifecycle management.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources