Hashnode updates beside your code
Cursor's agent can read the repo and the changelog, then turn them into scheduled Hashnode articles over MCP without you leaving the editor.
Schedule Hashnode 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 Hashnode scheduling as a native tool.
MCP supported{ "mcpServers": { "postqueen": { "url": "https://api.postqueen.ai/mcp/YOUR_API_KEY" } }}# Then ask: "Schedule our Hashnode articles"Cursor's agent can read the repo and the changelog, then turn them into scheduled Hashnode articles over MCP without you leaving the editor.
Tell Cursor when your readers are most active and it schedules articles into that window on Hashnode, day after day, without reminders.
Cursor hands postqueen the full draft, formatting included, and it lands on your Hashnode blogs 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 Hashnode until you do.
Cursor calls postqueen to list your connected blogs and sees what Hashnode supports, so drafts start from real capabilities, not guesses.
Give it the brief. The agent writes Hashnode-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 Hashnode tools are there in every session. It also runs commands, so the CLI covers the same Hashnode 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 Hashnode 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.
Hashnode includes its own analytics dashboard, so you can see how each article performs with readers there. postqueen adds the cross-channel view: publish history, queue status and how the article fits into the rest of your calendar.
Usually the personal access token was revoked or regenerated, the connected blog was deleted or renamed, or a required field like the title is missing. postqueen shows the API response on the failed post so the fix takes seconds, then you 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.