Lemmy tools in your terminal
Over MCP, scheduling and analytics show up as first-class tools. Over the CLI, every command returns JSON that Claude Code can chain reliably for Lemmy.
Queue Lemmy posts from your terminal. Claude Code drives postqueen over MCP or the CLI, so scheduling happens in the session you already have open.
Register the postqueen MCP server once and Lemmy scheduling becomes a tool Claude Code can call. The plain CLI works too.
MCP supported# Add the postqueen MCP serverclaude mcp add --transport http postqueen \ https://api.postqueen.ai/mcp/YOUR_API_KEY # Then ask in your session:# "Queue three Lemmy posts for this# week, mornings at 9"Over MCP, scheduling and analytics show up as first-class tools. Over the CLI, every command returns JSON that Claude Code can chain reliably for Lemmy.
Tell Claude Code when your communities are busiest and it schedules posts into that window on Lemmy, day after day, without reminders.
Claude Code targets the exact communities you choose and keeps every submission reviewable, so you can check each one against community rules first.
Ask Claude Code for drafts only. They sit on the postqueen calendar unscheduled, so you can edit them and pick the time yourself, and nothing reaches your community members on Lemmy until you do.
Claude Code calls postqueen to list your connected communities and sees what Lemmy supports, so drafts start from real capabilities, not guesses.
Give it the brief. The agent writes Lemmy-shaped posts and proposes publish times that match when your community members are around.
Look over the queue on the postqueen calendar and change anything you want. postqueen publishes each post at its time, and Claude Code can pull the results after.
Claude Code reads these limits from postqueen before it composes, so a draft that would be rejected never reaches the queue.
Scheduling, AI drafts, analytics and team roles, in one guide.
Over MCP, registered once in Claude Code's own config so the Lemmy tools are there in every session. It also runs commands, so the CLI covers the same Lemmy posts when you would rather script them; both use the same API key.
Yes. Give it exact slots or a rule like mornings at nine and it sets publish times on the posts it creates, keeping your communities active on a steady rhythm.
Only if you ask it to. Tell it to save drafts and nothing is scheduled: the posts wait on the calendar until you set a time. Tell it to schedule, and they go out at the times you can see, which is the setup most people move to once they trust the output.
Yes. postqueen connects 30 channels, so Claude Code can turn the same brief into Lemmy posts plus adapted versions for every other channel you run.
No. The agent uses your regular API key and plan limits: unlimited posts on every plan, and channel counts from 5 on Creator up to uncapped on Ultimate.
Both. Select several Lemmy communities and postqueen files a separate submission in each one, which is exactly how a Lemmy cross-post works, and the same draft can also go to Reddit, Mastodon or any of the 30 supported channels with per-platform wording. Space multi-community posts out rather than firing them in the same second: instances rate limit new posts, and moderators notice a wall of identical submissions. Because Lemmy federates over ActivityPub, Mastodon accounts can already follow a Lemmy community and see the post without a second submission.
Yes. The built-in assistant drafts titles and Markdown bodies from a short prompt and rewrites anything you highlight, and nothing publishes until you schedule it. Keep it grounded and specific: Lemmy communities are small and read closely, so generated filler gets spotted fast. Agents like Claude Code or OpenClaw can prepare a whole queue through the MCP server.
Queue this week's posts in minutes, or hand the whole thing to your favorite AI. postqueen keeps publishing either way.
Seven days free. Cancel in one click from settings.