Twitch updates beside your code
Cursor's agent can read the repo and the changelog, then turn them into scheduled Twitch clips and updates over MCP without you leaving the editor.
Schedule Twitch clips and updates 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 Twitch scheduling as a native tool.
MCP supported{ "mcpServers": { "postqueen": { "url": "https://api.postqueen.ai/mcp/YOUR_API_KEY" } }}# Then ask: "Schedule our Twitch clips"Cursor's agent can read the repo and the changelog, then turn them into scheduled Twitch clips and updates over MCP without you leaving the editor.
Tell Cursor when your followers are most active and it schedules clips into that window on Twitch, day after day, without reminders.
Video uploads travel through the same postqueen call, so Cursor ships Twitch clips and updates with real media attached and the publish time already set.
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 Twitch until you do.
Cursor calls postqueen to list your connected channels and sees what Twitch supports, so drafts start from real capabilities, not guesses.
Give it the brief. The agent writes Twitch-shaped clips and updates 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 Twitch tools are there in every session. It also runs commands, so the CLI covers the same Twitch clips and updates 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 clips 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 clips 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 Twitch clips and updates 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 schedules your go-live announcements, titles and cross-posted clips, and keeps a history of what went out. Follower counts, concurrent viewers, retention and the rest live in Twitch's own creator dashboard, and postqueen does not try to replace it.
Usually an expired OAuth token, a missing scope, or moderator rights that were removed from the channel. Titles over 140 characters are rejected too. postqueen flags the failed item with the reason so you can reconnect and retry.
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.