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, and Tumblr — 12 platforms today. 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 6 tools
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.
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.
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.
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.