Dev.to updates beside your code
Cursor's agent can read the repo and the changelog, then turn them into scheduled Dev.to articles over MCP without you leaving the editor.
Schedule Dev.to articles 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 Dev.to scheduling as a native tool.
MCP supported{ "mcpServers": { "postqueen": { "url": "https://api.postqueen.ai/mcp/YOUR_API_KEY" } }}# Then ask: "Schedule our Dev.to articles"Cursor's agent can read the repo and the changelog, then turn them into scheduled Dev.to articles over MCP without you leaving the editor.
Tell Cursor when your readers are most active and it schedules articles into that window on Dev.to, day after day, without reminders.
Cursor hands postqueen the full draft, formatting included, and it lands on your Dev.to profiles as complete articles, 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 Dev.to until you do.
Cursor calls postqueen to list your connected profiles and sees what Dev.to supports, so drafts start from real capabilities, not guesses.
Give it the brief. The agent writes Dev.to-shaped articles 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 Dev.to tools are there in every session. It also runs commands, so the CLI covers the same Dev.to articles 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 articles 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 articles 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 Dev.to articles 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.
Dev.to shows views, reactions and comments per article on its own dashboard. postqueen keeps the cross-channel picture: what went out, when, and what is queued next, so you can line article publishing up with the rest of your calendar.
The usual causes are an API key that was revoked or regenerated, more than 4 tags on the article, or tag names the platform rejects. postqueen surfaces the API error on the post so you can fix the draft and retry instead of digging through logs.
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.