Publish to Dev.to from Claude Cowork

Claude Cowork can publish and schedule Dev.to articles through Postiz. Add the Postiz connector to Cowork once, then point it at a Markdown draft on your desktop and name the title, tags, cover image, and organization. Cowork uploads the cover, sets a canonical URL when you are cross-posting, and schedules the article from the Claude app without a terminal.

Setup Guide

Please make sure there is always a human in the loop.

How to publish to Dev.to from Claude Cowork

Add Postiz to Claude Cowork once as a connector, then ask for Dev.to articles in plain language. Cowork calls Postiz for you and confirms what it scheduled.

Setup, then just ask

# One-time setup in Claude Cowork (no terminal)
# Cowork tab > Customize > Connectors > + Add custom connector
#   Name: Postiz
#   URL:  https://mcp.postiz.com/mcp-oauth-dynamic
# Sign in to Postiz and approve access

# Then just ask Claude Cowork:
> Publish my article on Dev.to with
  a cover image and tags, tomorrow at 9am

Claude Cowork: Done! Your Dev.to post is scheduled.

What can Claude Cowork do on Dev.to?

Claude Cowork can use every Dev.to option that Postiz exposes. Describe the result you want and Cowork picks the matching settings.

👨‍💻

Developer Articles

Publish technical articles with full Markdown support including code blocks, syntax highlighting, and embedded content.

🏢

Organization Posting

Publish articles under your Dev.to organization. Share content on behalf of your team or company with a single setting.

🖼

Cover Images

Upload and attach eye-catching cover images to your articles. Stand out in the Dev.to feed with visual content.

🔗

Canonical URLs

Set canonical URLs to link back to your original content. Perfect for cross-posting from your personal blog without SEO penalties.

🏷

Smart Tagging

Add up to 4 tags per article to reach the right developer audience. Tags drive discoverability on the Dev.to platform.

📅

Scheduled Publishing

Schedule articles for future publication with precise timestamps. Plan your developer content calendar ahead of time.

How does Claude Cowork publish to Dev.to?

You describe what you want in plain language and Claude Cowork handles the Postiz calls for you. Here is how a typical conversation goes.

Find Your Dev.to Integration

Ask Claude Cowork whether your Dev.to account is connected. It also checks which options the platform supports.

Example conversation

> Is my Dev.to account connected to Postiz?

Claude Cowork: Yes — your Dev.to account is connected
  and ready. Want me to post something?

Prepare Your Content

Write your article in Markdown. Dev.to supports rich formatting including headers, code blocks with syntax highlighting, images, and liquid tags.

Example conversation

> Draft a Dev.to post about our new
  feature launch

Claude Cowork: Here's a draft for Dev.to:
  "We just shipped something big..."
  Want me to add media and schedule it?

Publish Your Article

Create a post with your article content, title, cover image, tags, and optional organization and canonical URL settings.

Example conversation

> Yes — add screenshot.png and schedule
  it for tomorrow at 9am

Claude Cowork: Done! Scheduled on Dev.to for
  tomorrow at 9:00 AM.

Which Dev.to settings can Claude Cowork apply?

Mention any of these in plain language and Claude Cowork sets them for you. These are the Dev.to options it can apply to any post.

Field	Type	Required	Description
`__type`	string	Yes	Must be "devto"
`title`	string	Yes	Article title (min 2 characters)
`main_image`	object	No	Cover image: {id: string, path: string}
`canonical`	string	No	Original URL for canonical link
`organization`	string	No	Organization ID to publish under
`tags`	array	No	Up to 4 tags: [{value: string, label: string}]

Common Configurations

Ask Claude Cowork for any of these common Dev.to publishing scenarios and it applies the matching settings.

Simple Developer Article

Just ask

> Post it with: Simple Developer Article

Claude Cowork: Got it. Applying:
  title: 10 TypeScript Tips You Need to Know
  tags: TypeScript, JavaScript, Web Dev, Programming

Organization Post with Cover Image

Just ask

> Post it with: Organization Post with Cover Image

Claude Cowork: Got it. Applying:
  title: Introducing Our New AI Scheduling Tool
  main_image: id=img-abc123, path=https://uploads.postiz.com/launch-cover.png
  organization: my-org-id
  tags: AI, Show Dev, Productivity

Cross-Posted Article with Canonical URL

Just ask

> Post it with: Cross-Posted Article with Canonical URL

Claude Cowork: Got it. Applying:
  title: How We Reduced Build Times by 80%
  canonical: https://engineering.mycompany.com/build-times
  tags: DevOps, CI/CD, Performance

Full-Featured Article

Just ask

> Post it with: Full-Featured Article

Claude Cowork: Got it. Applying:
  title: Building a Real-Time Dashboard
  main_image: id=img-xyz789, path=https://uploads.postiz.com/dashboard.png
  canonical: https://myblog.dev/real-time-dashboard
  organization: my-team-id
  tags: React, WebSockets, Tutorial, JavaScript

What is Claude Cowork?

Claude Cowork is Anthropic's agentic assistant for knowledge workers. It runs in the Claude desktop app on macOS and Windows (and on the web) on paid Claude plans, uses the same agentic architecture as Claude Code without a terminal, and can read local files, use connectors, and run multi-step tasks such as publishing to Dev.to through Postiz. It is not the same as Claude Code (the terminal agent) or the Postiz connector in Claude.ai; read the full comparison on the Claude Cowork hub.

💻

Desktop Native

Claude Cowork runs directly on your desktop, connecting to your local files and apps. No dashboard tabs or terminal needed to manage your social media workflow.

🔗

App Integrations

Connects to Google Drive, Gmail, DocuSign, and more. Pull content from your existing tools and publish it to social media seamlessly.

🤖

Autonomous Tasks

Schedule recurring tasks with cron jobs. Claude Cowork can publish your Dev.to articles on a schedule without you having to ask each time.

How Postiz Works with Claude Cowork

Postiz is an MCP server, and Claude Cowork supports custom connectors over remote MCP. Add the Postiz link once in Customize, then Connectors, sign in with OAuth, and Cowork sees the Postiz tools for listing channels, uploading media, scheduling Dev.to articles, and reading analytics. No API key or terminal is needed.

✓Open the Cowork tab, then Customize, then Connectors, and add a custom connector named Postiz
✓Paste the Postiz MCP link and sign in to Postiz when prompted (OAuth, no API key)
✓Cowork discovers the Postiz tools automatically, including your connected Dev.to channel
✓Ask in plain language; Cowork chains upload, settings, and scheduling steps for you
✓Prefer the Postiz skill and CLI? Install the postiz-agent plugin instead and authenticate with postiz auth:login

Connect Postiz to Claude Cowork

# Option 1: custom connector (recommended, full toolset)
Cowork > Customize > Connectors > +
  Name: Postiz
  URL:  https://mcp.postiz.com/mcp-oauth-dynamic
  Sign in to Postiz and approve

# Option 2: official connector (posting + scheduling)
claude.ai/directory/postiz > Connect

# Option 3: Postiz skill + CLI (terminal)
npm install -g postiz
postiz auth:login

How do Dev.to workflows run in Claude Cowork?

Two ways: ask Cowork directly in the desktop app, where it can read the content from your local files, or set up a scheduled task that runs in the cloud on a timetable you choose.

From your desktop files

Local folders, Google Drive, no terminal

Point Claude Cowork at a document or media file on your computer and tell it where and when to publish. It reads the file, uploads media through Postiz, applies the Dev.to settings, and schedules the result for your Dev.to account.

Claude Cowork

You: Publish ~/Writing/webhooks.md on Dev.to
  tomorrow at 9am with cover.png, tags
  webdev, javascript, tutorial

Claude Cowork: Reading webhooks.md...
  1. Uploaded cover.png via Postiz
  2. Title and 3 tags set
  3. Scheduled for 9:00 AM

  Done! Cross-post to Hashnode as well?

Scheduled tasks

Recurring Dev.to articles without a cron server

Type /schedule in any Cowork task to make it recurring. Scheduled tasks run in the cloud with the connectors you have set up, so your computer does not need to be awake for Cowork to publish to Dev.to on time.

Claude Cowork scheduled task

/schedule

"Every Thursday at 9am, publish the oldest Markdown draft in ~/Writing/devto to Dev.to with a cover image and up to 4 tags, then move it to ~/Writing/published."

Claude Cowork will, on each run:
  1. Read the source file or folder
  2. Draft the Dev.to content
  3. Schedule it through Postiz
  4. Report back what it did

Why Claude Cowork + Postiz for Dev.to

Cowork brings the desktop context and the scheduling; Postiz brings the Dev.to publishing, media handling, and analytics. Together they replace a scheduler dashboard with a conversation.

✓No terminal: Postiz is a connector in the Claude app, added once
✓Reads Dev.to articles content from local folders and connected apps like Google Drive
✓Scheduled tasks run in the cloud on a timetable you set
✓Cross-posts Dev.to content to other Postiz channels in one request
✓Uses the same Postiz account, channels, and calendar as your dashboard and other agents

Postiz tools Cowork can call

# Discovery
integrationList        # your connected channels
integrationSchema      # Dev.to settings and limits
triggerTool            # live data (boards, flairs, lists)

# Publishing
uploadFromUrlTool      # media upload
integrationSchedulePostTool
postsListTool          # what is scheduled
postSettingsTool

# Custom MCP link only
generateImageTool, generateVideoTool, clippingTool

Also Works with OpenClaw

Postiz works with any AI agent that can run commands or call MCP tools — you ask, the agent does the work. That includes OpenClaw, the open-source personal AI agent, which reads the Postiz skill and runs the CLI rather than connecting over MCP.

🦀

OpenClaw

Open-source AI agent

OpenClaw reads the Postiz skill so it knows what it can do, then autonomously discovers your Dev.to integration, uploads your cover image, applies tags and organization settings, and publishes the article.

OpenClaw

> Publish my React tutorial to Dev.to
  under our org with a cover image,
  tag it with react and webdev

OpenClaw: Done! Scheduled on Dev.to for
  tomorrow at 9:00 AM.

Dev.to + Other Platforms

Publish the same article to Dev.to and other platforms in a single request. Each platform gets its own settings.

Example

> Post "Excited to announce our new feature!" to
  Dev.to and LinkedIn tomorrow at 9am, then schedule
  a daily tip on Dev.to every weekday at 10am

Claude Cowork: Done! Scheduled:
  - Dev.to + LinkedIn: tomorrow 9:00 AM
  - Daily tips on Dev.to: Mon-Fri 10:00 AM

What can you ask Claude Cowork to publish on Dev.to?

Anything you would type into the Postiz dashboard, phrased as a request. These are prompts people actually use for Dev.to.

You say to Claude Cowork	What Postiz does
`Publish ~/Writing/webhooks.md on Dev.to tomorrow at 9am with cover.png and the tags webdev, javascript, tutorial`	Uploads the cover, sets title and tags, schedules the article
`Cross-post our latest blog article to Dev.to with the canonical URL set to our site`	Sets the canonical field to the original URL
`Publish this under our company organization on Dev.to`	Sets the organization ID from your Dev.to organizations

What should you know before posting to Dev.to from Claude Cowork?

Cowork handles these rules for you, but knowing them explains why it sometimes asks a follow-up question before scheduling.

✓title is required and must be at least 2 characters.
✓Up to 4 tags are allowed; Dev.to tags are lowercase words like webdev or javascript.
✓Dev.to articles are written in Markdown, so a local .md draft usually needs no conversion.
✓Set canonical when cross-posting from your own blog so Dev.to credits the original. main_image is uploaded through Postiz first.

Claude Cowork and Dev.to: frequently asked questions

How do I publish to Dev.to from Claude Cowork?

Add Postiz as a custom connector in Cowork (Customize, then Connectors, URL https://mcp.postiz.com/mcp-oauth-dynamic), sign in to Postiz, and ask Cowork to publish a Markdown draft from your desktop. It sets the title and tags, uploads the cover image, and schedules the article. No terminal or Dev.to API key is needed.

Can Claude Cowork cross-post my blog to Dev.to with a canonical URL?

Yes. Tell Cowork the article was first published on your site and give the URL. It sets the canonical field when creating the Dev.to post through Postiz, so search engines credit your original and the Dev.to copy still reaches the Dev.to audience.

Can Cowork publish under a Dev.to organization?

Yes. Name the organization and Cowork sets the organization field to its ID when it creates the post. The article then appears under the organization's profile on Dev.to as well as yours, which is useful for company engineering blogs that several authors contribute to.

Is this different from Dev.to publishing with Claude Code?

The Postiz settings are identical. Claude Code is Anthropic's terminal agent and connects with a claude mcp add command or the Postiz CLI. Claude Cowork is the desktop agent, so Postiz is added as a connector and Cowork can read the Markdown draft straight from a folder.

How many tags can a Dev.to article have?

Up to four. Cowork accepts the tags you name and asks before dropping extras. Dev.to tags drive its topic feeds, so pick established ones such as webdev, javascript, or beginners. Cowork can suggest tags from the draft if you ask.

Related guides

More Claude Cowork platform guides

Dev.to with other tools

Start publishing to Dev.to

Add Postiz to Claude Cowork once and ask for your Dev.to posts in plain language. Free trial, no API key.

Get Started