Medium updates beside your code
Cursor's agent can read the repo and the changelog, then turn them into scheduled Medium stories over MCP without you leaving the editor.
Schedule Medium stories 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 Medium scheduling as a native tool.
MCP supported{ "mcpServers": { "postqueen": { "url": "https://api.postqueen.ai/mcp/YOUR_API_KEY" } }}# Then ask: "Schedule our Medium stories"Cursor's agent can read the repo and the changelog, then turn them into scheduled Medium stories over MCP without you leaving the editor.
Tell Cursor when your readers are most active and it schedules stories into that window on Medium, day after day, without reminders.
Cursor hands postqueen the full draft, formatting included, and it lands on your Medium publications as complete stories, ready for readers.
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 readers on Medium until you do.
Cursor calls postqueen to list your connected publications and sees what Medium supports, so drafts start from real capabilities, not guesses.
Give it the brief. The agent writes Medium-shaped stories and proposes publish times that match when your readers 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 Medium tools are there in every session. It also runs commands, so the CLI covers the same Medium stories 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 stories it creates, so your readers see them at the right moment.
Only if you ask it to. Tell it to save drafts and nothing is scheduled: the stories 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 Medium stories 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.
Medium's own stats pages show how each story performs with readers, including views and reads. postqueen keeps the operational side: publish history, queue status and the cross-channel calendar, so you always know what shipped where.
The most common causes are an integration token that was revoked or regenerated, a missing title, or more tags than the platform accepts. postqueen shows the error on the affected post so you can correct it and retry in a couple of clicks.
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.