English Français العربية

io.github.gosswerner1-max/lazyrelay-mcp-server

Official registry Marketing and sales

Publish posts to every platform, check platform rules, manage drafts and approvals, read analytics.

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package @lazyrelay/mcp-server
Claude Code 
claude mcp add lazyrelay-mcp-server -e 'LAZYRELAY_API_KEY=<your lazyrelay_api_key>' -- npx -y @lazyrelay/mcp-server@0.3.3
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "lazyrelay-mcp-server": {
            "command": "npx",
            "args": [
                "-y",
                "@lazyrelay/mcp-server@0.3.3"
            ],
            "env": {
                "LAZYRELAY_API_KEY": "<your lazyrelay_api_key>"
            }
        }
    }
}

Environment variables

  • LAZYRELAY_API_KEY required secret Your LazyRelay API key. Get one from your LazyRelay dashboard: Settings -> More -> API Keys -> Create key.

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

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

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 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.

Frequently asked questions

What is io.github.gosswerner1-max/lazyrelay-mcp-server?

Publish posts to every platform, check platform rules, manage drafts and approvals, read analytics.

How do I install io.github.gosswerner1-max/lazyrelay-mcp-server?

It runs on your machine. In Claude Code: claude mcp add lazyrelay-mcp-server -e 'LAZYRELAY_API_KEY=<your lazyrelay_api_key>' -- npx -y @lazyrelay/mcp-server@0.3.3. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.gosswerner1-max/lazyrelay-mcp-server need an API key?

Yes. It expects LAZYRELAY_API_KEY, which you set in its configuration.

Is io.github.gosswerner1-max/lazyrelay-mcp-server open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains io.github.gosswerner1-max/lazyrelay-mcp-server?

It is published by gosswerner1-max. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.