Lemmy commands it can verify
Gemini CLI runs postqueen and reads the JSON back, so it can confirm which Lemmy posts exist and at what times instead of reporting success it did not check.
Queue Lemmy posts from the terminal. Gemini CLI runs every postqueen command and reads the JSON back, so it can check what it scheduled.
Run the postqueen CLI directly, or add the MCP endpoint to your Gemini CLI settings and ask for Lemmy posts in plain language.
MCP supportednpm install -g postqueenexport POSTQUEEN_API_KEY=your_api_key # Or MCP, in your Gemini CLI settings:# { "mcpServers": { "postqueen": {# "url": "https://api.postqueen.ai/mcp/KEY"# } } }Gemini CLI runs postqueen and reads the JSON back, so it can confirm which Lemmy posts exist and at what times instead of reporting success it did not check.
Tell Gemini CLI when your communities are busiest and it schedules posts into that window on Lemmy, day after day, without reminders.
Gemini CLI targets the exact communities you choose and keeps every submission reviewable, so you can check each one against community rules first.
Ask Gemini CLI 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.
Gemini CLI 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 Gemini CLI can pull the results after.
Gemini CLI 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 Gemini CLI'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 Gemini CLI 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.
Yes. Every cloud plan starts with a 7-day free trial with unlimited posts, and you can cancel anytime. If you would rather not depend on a hosted service at all, the open source version is free to self-host.
A Lemmy post is a title plus an optional link or image and an optional Markdown body, and postqueen schedules all of it. Pick the community, write or generate the submission, choose the time and it publishes through your instance. Markdown from the composer, including headings, lists and links, arrives exactly as you wrote it.
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.