Post to Social Media from Cursor

Connect LazyRelay's MCP server to Cursor and schedule, check, and verify social posts right from the same chat you're coding in.

What you can ask Cursor

• "Schedule a post announcing this release to X and LinkedIn for Friday at 10am."
• "What's already queued this week?"
• "Did the launch-day post actually go live on every platform?"
• "Pull my post analytics for the last 30 days."

The part most AI-agent schedulers skip

Most integrations stop at the API call — the agent asks for a post, the API says 200 OK, and that's treated as done. It isn't. Rate limits, silent moderation holds, and platform-side failures can all eat a "successful" request. LazyRelay's list_scheduled_posts tool returns real Proof-of-Publish status, so you can ask Cursor to check whether a post actually went live, not just whether the request was accepted.

Setup

1. In your LazyRelay dashboard, go to API Keys (top nav) and create a new key. Requires a paid plan — Starter and up. Copy it now, it's only shown once.
2. In Cursor, add an MCP server — either through Cursor's Settings → MCP panel, or by editing your MCP config file (.cursor/mcp.json for a single project, or Cursor's global MCP config to make it available everywhere):

   {
     "mcpServers": {
       "lazyrelay": {
         "command": "npx",
         "args": ["-y", "@lazyrelay/mcp-server"],
         "env": {
           "LAZYRELAY_API_KEY": "lzr_live_your_key_here"
         }
       }
     }
   }

3. Reload Cursor. LazyRelay's tools should now be available to the agent.

Prefer nothing running locally?

LazyRelay also runs a hosted MCP server. Use a url field instead of command/args — Cursor handles the sign-in the first time it connects, no API key needed:

{
  "mcpServers": {
    "lazyrelay": {
      "url": "https://lazyrelaylazyrelay-backend.onrender.com/mcp"
    }
  }
}

Full tool reference (list_connected_accounts, schedule_post, list_scheduled_posts, delete_scheduled_post, get_analytics_summary, get_mentions) at lazyrelay.com/docs.