Skip to main content
Glama
gosswerner1-max

LazyRelay MCP Server

by gosswerner1-max
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to LazyRelay MCP Server

No user-submitted related servers found.

    Related Servers

    • postlayer-connect

      pokakrisztian2
      A
      license
      A
      quality
      D
      maintenance
      A local MCP server that enables AI assistants to post to social media platforms (LinkedIn, X, Bluesky, Mastodon, Reddit, etc.) using your own app credentials, with encrypted token storage and no middleman.
      5
      MIT

    • ilo

      iannuttall
      A
      license
      Not graded
      quality
      A
      maintenance
      A local-first MCP server for social publishing on X (Twitter), enabling draft management, scheduling, and posting via CLI or AI agents.
      41 npm
      5
      MIT

    • linkedin-mcp

      aneesh-a7
      A
      license
      Not graded
      quality
      C
      maintenance
      A personal-use remote MCP server that lets you post to LinkedIn, queue/schedule drafts, and pull your own post analytics from Claude.
      13 npm
      MIT

    • Outpost

      andrezani
      A
      license
      Not graded
      quality
      D
      maintenance
      Social media API and MCP server for AI agents that enables publishing to X, Instagram, LinkedIn, Reddit, Bluesky, and Threads from a single endpoint.
      67 npm
      MIT

    • meta-threads-mcp

      MetaThreads
      A
      license
      A
      quality
      C
      maintenance
      Unofficial MCP server for Meta's Threads API. Enables LLMs like Claude to publish posts, manage replies, and track insights through the Model Context Protocol.
      15
      MIT

    • crosspost-mcp

      Aleksey-Panf
      A
      license
      A
      quality
      C
      maintenance
      MCP server that lets AI agents cross-post content to Telegram, Discord, Mastodon, Bluesky, and Reddit — using free APIs only.
      3
      2
      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.2/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: account listing, post scheduling, scheduled post listing, deletion, analytics, and mentions. No two tools overlap in purpose, and the dependency between list_connected_accounts and schedule_post is clearly documented.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern: list_, schedule_, delete_, get_. The verbs are specific to each action and the objects are clear, making the set predictable and easy to navigate.

    Tool Count5/5

    Six tools is a well-scoped size for a social media scheduling server. Each tool covers a necessary function without redundancy or bloat, and the count feels appropriate for the domain.

    Completeness4/5

    The core lifecycle is covered: list accounts, schedule, list scheduled, delete pending posts, plus analytics and mentions. A minor gap is the lack of an update/reschedule tool, but deleting and recreating a post is a viable workaround, so the surface is otherwise solid.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources