Dev.to Blog Publisher MCP Server

A custom Model Context Protocol (MCP) server that lets Claude publish markdown blog posts directly to Dev.to — no copy-pasting into the Dev.to editor required.

Built with FastMCP and the Dev.to API.

Overview

This server exposes a single MCP tool, publish_blog_to_devto, which any MCP-compatible client (like Claude Desktop) can call to create an article on your Dev.to account. Pair it with the official filesystem MCP server and you can ask Claude to:

"Read blog.txt from my drafts folder, refine the content, and publish it to Dev.to as a draft with relevant tags."

Claude reads the file, cleans up the writing, and calls this server to publish it — all in one conversation, no manual formatting.

Related MCP server: cnblogs-mcp

Features

• Publish articles as drafts or live

• Set title, tags, series, canonical URL, and cover image

• Uses your personal Dev.to API key — the key never leaves your machine except to call Dev.to's own API

Requirements

• Python 3.10+

• uv for package management

• A Dev.to API key (Settings → Extensions → DEV Community API Keys)

• Claude Desktop or another MCP-compatible client

Setup

1. Clone and install dependencies

git clone https://github.com/Dineshv0311/devto-mcp-server.git
cd devto-mcp-server
uv sync

2. Configure your API key

Copy the template and fill in your key:

cp .env.template .env

Then edit .env:

DEVTO_API_KEY=your_devto_api_key_here

⚠️ .env is listed in .gitignore — never commit your real API key.

3. Test the server standalone (recommended)

Before wiring it into Claude Desktop, verify the server works using the MCP Inspector:

uv run mcp dev dev-server.py

This opens a local web UI where you can call publish_blog_to_devto directly and inspect the raw request/response — useful for catching issues before debugging through a chat interface.

4. Connect it to Claude Desktop

Open your Claude Desktop config file:

• Windows: %APPDATA%\Claude\claude_desktop_config.json

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Add this server inside the top-level mcpServers key:

{
  "mcpServers": {
    "devto": {
      "command": "C:\\path\\to\\uv.exe",
      "args": ["--directory", "C:\\path\\to\\devto-mcp-server", "run", "dev-server.py"]
    }
  }
}

💡 On Windows, use the full path to uv.exe (find it with where.exe uv) — Claude Desktop doesn't always inherit your shell's PATH.

Fully quit and reopen Claude Desktop (check it's not lingering in the system tray) and confirm the server shows as running under Settings → Developer → Local MCP servers.

Usage

Once connected, talk to Claude normally:

"I have a file blog.txt in my drafts folder — refine its content and publish it to Dev.to as a draft with tags: mcp, ai, python."

Tool: publish_blog_to_devto

Tip: publish with published: false first to review the draft on Dev.to before making it live.

Project Structure

devto-mcp-server/
├── dev-server.py         # MCP server + publish_blog_to_devto tool
├── devto-test.py         # Standalone test script for the Dev.to API call
├── example-config.json   # Example Claude Desktop config snippet
├── .env.template         # Template for required environment variables
├── pyproject.toml        # Project dependencies (managed by uv)
└── README.md

Troubleshooting

ModuleNotFoundError: No module named 'mcp.server.fastmcp' There's an unrelated package squatting the mcp name on PyPI. Pin the real SDK explicitly:

uv remove mcp
uv add "mcp[cli]>=1.2.0,<2.0.0"

Server doesn't show up in Claude Desktop Double-check devto is nested inside mcpServers in the config, not a sibling key. Fully restart Claude Desktop.

uv not found after installing Close and reopen your terminal so it picks up the updated PATH.

Dev.to API returns 422 Unprocessable Entity Usually means a duplicate title/slug already exists on your account. Try a slightly different title.

License

MIT — see LICENSE