Publish posts to every platform, check platform rules, manage drafts and approvals, read analytics.
Runs on your machine from its package; the steps are below.
At most: moves money, runs code or commands, deletes data, or sends messages for you.
Odel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Run
npx -y @lazyrelay/mcp-server
MCP client config
{
"mcpServers": {
"lazyrelay": {
"command": "npx",
"args": [
"-y",
"@lazyrelay/mcp-server"
]
}
}
}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, and Slack — 17 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
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 and listed in the official MCP Registry as io.github.gosswerner1-max/lazyrelay-mcp-server.
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.