Bluesky updates beside your code
Cursor's agent can read the repo and the changelog, then turn them into scheduled Bluesky posts over MCP without you leaving the editor.
Schedule Bluesky posts without leaving your editor. Cursor's agent drives postqueen over MCP or the CLI, right beside the code you are shipping.
Drop the MCP config into your project and Cursor's agent gets Bluesky scheduling as a native tool.
MCP supported{ "mcpServers": { "postqueen": { "url": "https://api.postqueen.ai/mcp/YOUR_API_KEY" } }}# Then ask: "Schedule our Bluesky posts"Cursor's agent can read the repo and the changelog, then turn them into scheduled Bluesky posts over MCP without you leaving the editor.
Tell Cursor when your followers are most active and it schedules posts into that window on Bluesky, day after day, without reminders.
Images upload in the same postqueen call, so Bluesky posts arrive with their media in place instead of a bare link.
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 followers on Bluesky until you do.
Cursor calls postqueen to list your connected accounts and sees what Bluesky supports, so drafts start from real capabilities, not guesses.
Give it the brief. The agent writes Bluesky-shaped posts and proposes publish times that match when your followers are around.
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.
Cursor 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 Cursor's own config so the Bluesky tools are there in every session. It also runs commands, so the CLI covers the same Bluesky 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, so your followers see them at the right moment.
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 Cursor can turn the same brief into Bluesky 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.
postqueen keeps your Bluesky publishing history next to the calendar, so you can track your own cadence and reschedule more of what resonated. Live likes, reposts and follower counts stay on Bluesky itself, where the AT Protocol surfaces them.
Usual suspects are a revoked or mistyped app password, media that exceeds Bluesky's size limits, or a temporary server outage. Reconnect the account or resize the media and schedule the post again.
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.