Dev.to MCP servers in 2026.No official one, and the open-source ones skip the AI label.

The kinds of Dev.to MCP serverHow each one gets to your account.

What Dev.to's API lets a server doThe rules every server works within.

• An API key, no OAuthEach person generates a key in Settings, Extensions, under DEV Community API Keys. It acts as the whole account, with no scopes and no expiry, which is why every Dev.to MCP server asks for one.
• PostingPOST /api/articles with the title, the Markdown body, a cover URL and up to 4 tags as an array, letters and digits only. There's no image upload for keys, so images must already be online.
• AI disclosureai_disclosure_level takes no_ai, some_ai or fully_autonomous, and the article shows it. dev.to/llms.txt asks API clients to send it accurately; left out, the article shows Not Disclosed.
• What the API can't doPost comments, which are read-only, delete an article, or upload media. Writes are limited to 1 a second per key.

In Claude Code, Cursor or any MCP clientOne hosted server, OAuth or an API key.

The server lives at https://api.breakreach.com/mcp and speaks Streamable HTTP, so there is nothing to install. Clients that handle OAuth sign you in; others send an API key from Settings → API & MCP.

claude mcp add --transport http breakreach https://api.breakreach.com/mcp

{
  "mcpServers": {
    "breakreach": {
      "url": "https://api.breakreach.com/mcp",
      "headers": { "Authorization": "Bearer br_YOUR_API_KEY" }
    }
  }
}

Step-by-step setup for each client: Claude Code, Cursor, Codex and OpenClaw.

What to askThree requests that work on Dev.to today.

• “Turn my roast logger notes into a Dev.to article for tomorrow 9 AM, tagged python and raspberrypi”
• “Cross-post our latest blog article to Dev.to with the blog as the original, marked AI-assisted”
• “How many views and reactions did my last three Dev.to articles get?”