Skip to main content
Glama
Sign In
LazyRelay MCP Server

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.
      17 npm
      MIT

    • Outpost

      andrezani
      A
      license
      Not graded
      quality
      C
      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.
      108 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

    A3.6/5.0

    Scored across 27 tools

    Disambiguation4/5

    Most tools target a distinct resource+action, and the descriptions actively disambiguate the risky pairs (update_post vs reschedule_post, schedule_post vs schedule_draft vs publish_post_now). The main cluster—schedule_post, create_draft, schedule_draft, publish_post_now—shares a lot of surface area, but each has a stated distinguishing rule.

    Naming Consistency5/5

    Every tool uses a consistent snake_case verb_noun pattern (list_connected_accounts, schedule_post, revoke_review_link, reply_to_post_feedback). No camelCase or mixed verb styles appear anywhere in the set.

    Tool Count3/5

    27 tools is on the heavy side for a scheduling/publishing server, even accounting for multi-platform support and review workflows. Each tool is defensible, but the set could likely be trimmed by consolidating the draft/schedule/reschedule family.

    Completeness4/5

    The post lifecycle (draft → schedule → approve → pause/resume → publish → delete), analytics, mentions, and client review links are all covered. Minor gaps: replying to comments is explicitly out of scope, and snippets/posting slots/accounts are read-only with no create/update/delete.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources