Dev.to tools in your terminal
Over MCP, scheduling and analytics show up as first-class tools. Over the CLI, every command returns JSON that Claude Code can chain reliably for Dev.to.
Queue Dev.to articles from your terminal. Claude Code drives postqueen over MCP or the CLI, so scheduling happens in the session you already have open.
Register the postqueen MCP server once and Dev.to scheduling becomes a tool Claude Code can call. The plain CLI works too.
MCP supported# Add the postqueen MCP serverclaude mcp add --transport http postqueen \ https://api.postqueen.ai/mcp/YOUR_API_KEY # Then ask in your session:# "Queue three Dev.to articles for this# week, mornings at 9"Over MCP, scheduling and analytics show up as first-class tools. Over the CLI, every command returns JSON that Claude Code can chain reliably for Dev.to.
Tell Claude Code when your readers are most active and it schedules articles into that window on Dev.to, day after day, without reminders.
Claude Code hands postqueen the full draft, formatting included, and it lands on your Dev.to profiles as complete articles, ready for readers.
Ask Claude Code 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.
Claude Code 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 Claude Code can pull the results after.
Claude Code 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 Claude Code'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 Claude Code 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.
There is no single magic hour, and anyone who promises one is guessing. Dev.to readers are developers spread across every time zone, so pick a window that matches your core audience, keep the cadence steady, and adjust based on how your own articles perform. Scheduling makes it easy to test different windows without being online.
Yes. Write the article once in postqueen and send it to Dev.to and your other blog channels in one pass, with per-platform tweaks before publishing. Set the canonical URL on the Dev.to copy so search engines credit the original post on your own site.
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.