Lemmy updates beside your code
Cursor's agent can read the repo and the changelog, then turn them into scheduled Lemmy posts over MCP without you leaving the editor.
LemmyAutomate Lemmy with Cursor
Schedule Lemmy posts without leaving your editor. Cursor's agent drives postqueen over MCP or the CLI, right beside the code you are shipping.
Quick start
Drop the MCP config into your project and Cursor's agent gets Lemmy scheduling as a native tool.
MCP supported.cursor/mcp.json
{ "mcpServers": { "postqueen": { "url": "https://api.postqueen.ai/mcp/YOUR_API_KEY" } }}# Then ask: "Schedule our Lemmy posts"What Cursor can run on Lemmy
Windows that fit Lemmy
Tell Cursor when your communities are busiest and it schedules posts into that window on Lemmy, day after day, without reminders.
Community rules respected
Cursor targets the exact communities you choose and keeps every submission reviewable, so you can check each one against community rules first.
Drafts until you are ready
Ask Cursor 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.
Three steps to a full queue
Discover Lemmy
Cursor calls postqueen to list your connected communities and sees what Lemmy supports, so drafts start from real capabilities, not guesses.
Draft with Cursor
Give it the brief. The agent writes Lemmy-shaped posts and proposes publish times that match when your community members are around.
Check and publish
Look over the queue on the postqueen calendar and change anything you want. postqueen publishes each post at its time, and Cursor can pull the results after.
What Lemmy allows
Cursor reads these limits from postqueen before it composes, so a draft that would be rejected never reaches the queue.
- Post title
- 3 to 200 characters
- Post body
- Markdown, up to about 10,000 characters
- Attachments
- One link or image per post, with extra images embedded in the Markdown body
- Communities
- Every post belongs to exactly one community, so a cross-post is a separate submission
- Account
- A regular account on a Lemmy instance, with no developer app to register
- Rate limits
- Set per instance, and defaults allow only a few new posts per 10 minutes
LemmyEverything postqueen does on Lemmy
Scheduling, AI drafts, analytics and team roles, in one guide.
F.A.Q.
Frequently asked questions
How does Cursor connect Lemmy to postqueen?
Over MCP, registered once in Cursor'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.
Can Cursor schedule Lemmy posts at exact times?
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.
Will Cursor publish to Lemmy on its own?
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.
Can one brief cover Lemmy and other channels too?
Yes. postqueen connects 30 channels, so Cursor can turn the same brief into Lemmy posts plus adapted versions for every other channel you run.
Does Cursor access cost extra on postqueen?
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.
Why did my scheduled Lemmy post fail?
The usual causes are an expired login on your instance, a community that restricts posting to moderators, an instance rate limit rejecting the submission, or a title over the 200 character maximum. Instance downtime counts too, since a volunteer run server goes offline for maintenance more often than a large corporate API does. postqueen marks the post with the error it got back so you can fix the cause and retry.
Can I run postqueen on the same server as my Lemmy instance?
Yes. postqueen is open source under AGPL-3.0 and ships as a Docker image, so you can run it next to your own instance and keep the whole pipeline on your hardware. Self-hosting is free, and the CLI, REST API, webhooks and MCP server work exactly as they do on the cloud.
Ready to get started?
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.