How to post to Dev.to from Claude.Two minutes, no API key.

Why run Dev.to from a conversationClaude writes, Breakreach publishes.

A DEV article usually starts as something you already wrote: a blog post, a README, the notes from a fix. The work left is the copy for DEV: a title, four tags that pass its rules, the cover, the link back to your blog. Handing that to the assistant with a date turns the cross-post into one sentence, and the same request can share it on X and LinkedIn.

Nothing runs on your machine. Once a post is scheduled, it publishes from our servers, so Claude can be closed and your laptop can be off.

What you can post to Dev.toAnd how to ask for each.

• ArticleThe first line is the title, up to 128 characters, and the rest is the body in Markdown, sent as you wrote it: ## headings, lists, links and code blocks. A body that starts with a --- line is changed so Dev.to doesn't read it as front matter.Publish these notes as a Dev.to article
• Cover and photosThe first photo is the cover, which Dev.to shows above the title and suggests at 1000 × 420. Up to 9 more photos are added after the text. A video isn't sent: put it on YouTube and add {% youtube … %} on its own line, and Dev.to embeds it.Use the roastery photo as the cover
• Tags, original address, AI labelUp to 4 tags, cleaned to letters and digits, so node.js becomes nodejs. The address where the article first ran, as its canonical URL. And how much AI wrote it, which Dev.to shows on the article as No AI, AI-assisted or Fully Autonomous.Tag it python and raspberrypi, with our blog post as the original
• Draft on Dev.toAsk for a draft on Dev.to and the article waits unpublished in your DEV dashboard, to finish and publish there.Save it as a draft on Dev.to, I'll publish it from there

Let Claude write the Dev.to postThen say what to change.

DEV readers are developers, and they skim for the code and the result. Give the assistant your notes and ask for a title that says what you built or learned, ## sections, and a code block when there's code. Say how much it wrote: DEV asks for the AI label to be accurate, and its guidelines rule out AI-assisted articles that promote a business, a program or a course.

Schedule it instead of posting nowOr let it take the next free slot.

Name a time and the post is scheduled in your workspace's time zone. Or skip the time: use my next free slot puts it in the first open slot of your posting schedule, which is weekdays at 11 AM and 4 PM until you change it in Breakreach. Scheduled Dev.to posts go out from Breakreach's servers, so the conversation, the app and your laptop can all be closed.

After it's publishedStats, edits and deletions.

How it did

Views, reactions and comments for each article, read from Dev.to's analytics, plus your followers count. Ask how did my last Dev.to article do? and the numbers come back in the chat. A draft left on Dev.to has no counts.

Edit or delete it

Until it goes out, you can change anything from the conversation: move it to Friday, change the caption, turn it back into a draft. A failed post can be fixed and rescheduled the same way. Once it's published, the connector can't edit or delete it on Dev.to, and deleting it in Breakreach only takes it off the calendar, so edit or remove a published post in your DEV dashboard, where you can also edit it.

What Dev.to requiresAnd the limits to know.

• A DEV Community account and an API key you generate on dev.to, under Settings, Extensions, DEV Community API Keys. Name it Breakreach; you can revoke it there anytime.
• The first line of your text becomes the article's title, up to 128 characters.
• Text alone is fine. Photos are optional, and videos aren't sent, since Dev.to has no upload for apps.
• The first photo becomes the cover image; up to 9 more are added after the text. Videos aren't sent.

What it can't do yet

• Videos: Dev.to has no upload for apps, so the article goes out without it.
• Organizations and series: articles go out under your own account, on their own.
• Comments: Breakreach counts them but doesn't read or answer them.
• Dev.to's own schedule: Breakreach publishes at the time from its servers, so the article doesn't wait on DEV as scheduled.

Three things people do with it

• Cross-post a blog article to DEV with your blog as the canonical URL, so search engines credit the original
• Turn a fix you just shipped into a short DEV article with the code, tagged and scheduled for Tuesday morning
• See which of your last articles got the most views and reactions, and write the next one like them

A safe routine for a teamDrafts first, then the calendar.

• Ask for drafts, not postsSay save it as a draft and nothing is scheduled. Drafts land in the Breakreach calendar, where the team can read them, and schedule the draft for Thursday at 9 AM turns one into a post.
• Review in the calendarEvery Dev.to post, from Claude, the API or the app, sits on the same calendar with its time, account and media. Open one to edit it or move it.
• Name the brandWith several workspaces, the connector uses your first one unless you name another, so say which brand the post is for.
• Approve each postSet Claude to ask before it acts (details below), so nothing is published without someone clicking allow.
• Know when something failsA post that hits a temporary error is retried up to three times over 30 minutes. If it still fails, it's marked failed in the calendar with a notification, and you can fix and reschedule it from the chat.
• Revoke access anytimeDisconnect the connector in Claude and the assistant can't post any more. Posts already scheduled stay in the calendar until you cancel them.

Using the connector in ClaudePlans, confirmations, phones.

• Which plans have itConnectors from Claude's directory work on every plan, Free included. On Team and Enterprise, an Owner first adds the connector for the organization in Organization settings → Connectors, then each member signs in with their own account.
• Confirmations before postingClaude asks before using a tool, with Allow once or Always allow. In Customize → Connectors → Breakreach → Tool permissions you can set each tool to Always allow, Needs approval or Blocked: for example, reading posts always allowed and creating posts needing approval. Research mode can call connector tools without asking.
• Web, desktop and phoneConnectors work on claude.ai, in the desktop apps and in the iOS and Android apps. Add Breakreach on the web or desktop, and it's available on your phone the next time you log in.
• DisconnectingIn Customize → Connectors, select Breakreach: Disconnect signs Claude out, and Remove in the menu takes it off your account. Posts already scheduled in Breakreach still go out.

Sources, checked September 2026: Use connectors, Getting started with connectors, Connector directory.

Other ways to post to Dev.to from ClaudeAnd when they're the better choice.

• Dev.to's own schedulingIn DEV's editor, the post options have a Schedule Publication date and time, and the Publish button becomes Schedule. Better when the article is already written in DEV's editor. Forem source
• Dev.to's RSS importDEV can import the posts of your blog's RSS feed as drafts, with your blog as the canonical URL if you choose. Better when every post on your blog should land on DEV, and you'll publish each one there. DEV settings
• PostizPostiz publishes Dev.to articles from its app and its MCP server, with a cover, tags, a canonical URL, and an organization if you post as one, which Breakreach doesn't. Postiz docs
• Copy and pasteAsk the assistant for the article, then paste it in DEV's editor. Free and fine for one article, but the cover, the tags and the timing are yours to set.

When it doesn't workThe fixes for what people run into.

• “Dev.to didn't accept the API key”The key was revoked or mistyped. On dev.to, open Settings, Extensions, generate a new key under DEV Community API Keys, and connect Dev.to again in Breakreach with it. The same DEV account keeps its scheduled posts.
• “Title has already been used in the last five minutes”Dev.to refuses the same title twice within five minutes. The first article probably went out: check your DEV dashboard before you retry, or change the title.
• “Canonical url has already been taken”Another published article on DEV already points to that address, often an earlier cross-post or an RSS import of your blog. Unpublish the older copy or remove the original address, then retry.
• My video isn't in the articleDev.to has no video upload for apps, so Breakreach sends the article without it. Put the video on YouTube and add {% youtube https://youtu.be/… %} on its own line in the text: Dev.to embeds it.