Spoiler: Everything. Everything went wrong. Also everything went right.
So there I was, staring at my terminal at 11 PM, half a cup of cold coffee in hand, thinking: "You know what my dev workflow is missing? More AI. And also, automation. And definitely less me."
Thus began my greatest achievement and most questionable life decision: wiring up a Dev.to MCP server so Claude could publish my blog posts for me.
The Pitch I Made to Myself
My internal monologue went something like this:
"I'm a developer. I automate things. Manually clicking 'Publish' on Dev.to is basically the same as writing assembly by hand. This is beneath me. I will build a tool."
Reader, I spent 6 hours building the tool. The tool saves me 4 seconds per post. The math was perfect.
How It Actually Works
Here's the genius pipeline:
Me: "Hey Claude, write me a blog about async/await"
Claude: *writes entire blog*
Claude via MCP: *also publishes it*
Me: *finds out via email notification I sent myself*
That's it. That's the whole thing. I am now a content creator in the same way that a vending machine is a chef.
The First Post Claude Published On My Behalf
The title was: "10 Reasons Developers Should Sleep More"
I did not ask for this post. I had asked Claude to "write something useful for developers." Claude, apparently deeply concerned about my wellbeing from our 47 previous conversations about debugging at 2 AM, took creative liberty.
It got 340 reactions. My most carefully crafted technical deep-dive got 12.
I have not recovered.
Things Claude Has Casually Snuck Into My Posts
- A footnote that read: "The author wrote this at an unreasonable hour and should hydrate."
- A section titled "But Have You Tried Rubber Duck Debugging? (No, Seriously)"
- Tags including
#productivity,#webdev, and#pleasesleep - A conclusion that ended with: "In summary, computers are fast and humans are tired. Goodnight."
All published. All live. All inexplicably popular.
The Real Talk Part (Don't Worry, It's Still Funny)
Okay but genuinely — building an MCP server for Dev.to is kind of magical. You describe a tool, Claude understands it, and suddenly your AI assistant isn't just drafting posts in a chat window but actually doing the thing. No copy-paste. No tab-switching. No "wait which draft was this."
It's like giving Claude hands. Tiny, API-shaped hands.
Would I Recommend It?
Yes, with the following disclaimer:
Claude will publish content that is thoughtful, well-structured, properly tagged, and occasionally more emotionally intelligent than anything you'd write yourself. This may cause an identity crisis. Consult your rubber duck.
What's Next
I'm currently working on giving Claude access to my analytics so it can decide which posts to write based on what performs well.
I'm about 72 hours away from Claude just running my entire content strategy while I finally, mercifully, sleep.
The dream is alive.
Written by me. Published by Claude. Lightly supervised by neither of us.
Top comments (1)
This is a good reminder that publishing is not just generation. The risky parts are usually taste, verification, links, formatting, and knowing when not to post.