LazyRelay MCP Server
# LazyRelay
LazyRelay is a social media scheduler built around one idea: publishing shouldn't just look successful, it should be provable. Where most schedulers mark a post "sent" the moment an API call succeeds, LazyRelay's Proof-of-Publish independently verifies the post actually went live before it's marked confirmed. If verification fails, the post is flagged instead of silently marked successful.
Schedule to Facebook, Instagram, TikTok, Pinterest, YouTube, LinkedIn, Threads, Mastodon, Bluesky, Telegram, Discord, Tumblr, WordPress, dev.to, Hashnode, Lemmy, Slack, and X: 18 distribution platforms plus WhatsApp today. X connects with your own X developer keys on any paid plan, and X bills your own developer account for each post. WhatsApp is client messaging (two way chat, approval requests, scheduled broadcasts to opted-in contacts), connected with your own Meta WhatsApp Business credentials. Manage multiple brands from one account, with per-brand caps instead of a separate workspace fee for each one.
**Live product:** [lazyrelay.com](https://lazyrelay.com)
## MCP server
[`mcp-server/`](./mcp-server) is LazyRelay's official Model Context Protocol server, letting AI agents (Claude, Cursor, and others) schedule posts, check analytics, and read mentions directly. Published on npm as [`@lazyrelay/mcp-server`](https://www.npmjs.com/package/@lazyrelay/mcp-server) and listed in the official MCP Registry as `io.github.gosswerner1-max/lazyrelay-mcp-server`.
## About this repository
This is LazyRelay's product monorepo (`backend/`, `frontend/`, `mcp-server/`, and supporting tooling), made public to support MCP registry and directory listings. It's not open source and isn't accepting external contributions — all rights reserved.
TDQS
Scored across 27 tools
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.
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.
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.
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.