Warpcast updates beside your code
Cursor's agent can read the repo and the changelog, then turn them into scheduled Warpcast posts over MCP without you leaving the editor.
Schedule Warpcast 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 Warpcast scheduling as a native tool.
MCP supported{ "mcpServers": { "postqueen": { "url": "https://api.postqueen.ai/mcp/YOUR_API_KEY" } }}# Then ask: "Schedule our Warpcast posts"Cursor's agent can read the repo and the changelog, then turn them into scheduled Warpcast posts over MCP without you leaving the editor.
Tell Cursor when your followers are most active and it schedules posts into that window on Warpcast, day after day, without reminders.
Images upload in the same postqueen call, so Warpcast 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 Warpcast until you do.
Cursor calls postqueen to list your connected accounts and sees what Warpcast supports, so drafts start from real capabilities, not guesses.
Give it the brief. The agent writes Warpcast-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 Warpcast tools are there in every session. It also runs commands, so the CLI covers the same Warpcast 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 Warpcast 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 a record of every cast you scheduled and when it went out, next to the calendar that produced it. Farcaster data is open by nature, so engagement and follower numbers are easy to read on Warpcast or any Farcaster client, and postqueen focuses on getting casts out on a consistent schedule rather than duplicating those stats.
The usual causes are a revoked signer key, a cast that went over the 1,024 byte limit once emoji were counted, or more than 2 embeds attached. postqueen shows the error on the post so you can fix it and reschedule.
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.