Skip to main content
Glama
gosswerner1-max

LazyRelay MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LAZYRELAY_API_KEYYesLazyRelay API key from Settings -> More -> API Keys -> Create key

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_connected_accountsA

List every social media account connected to this LazyRelay account, with platform, display name, and the id needed by schedule_post.

schedule_postA

Schedule a post to one connected social account. Call list_connected_accounts first to get a valid socialAccountId — post to multiple platforms by calling this once per account.

list_scheduled_postsA

List this account's upcoming and recent posts, with status (pending/posted/failed) and Proof-of-Publish verification.

delete_scheduled_postA

Cancel a pending scheduled post before it goes out. Has no effect on a post that's already gone out.

get_analytics_summaryA

Get post counts, verified-live rate, per-platform breakdown, and engagement totals (likes/comments/shares/views, where each platform exposes them) for a recent window.

get_mentionsA

Get recent comments on this account's posts, on the platforms that support reading comments (Facebook, Instagram, Mastodon, Bluesky, YouTube).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 6 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityActive
ResponsivenessNo issues