AMAny MCP client+DEVDev.to

Publish to Dev.to from Any MCP client

Any MCP client can publish articles on Dev.to through ClipSpeed. Add the ClipSpeed connector, sign in, and then ask Any MCP client to publish articles, pick the time, and apply Dev.to's settings, without leaving any client that speaks the Model Context Protocol. Dev.to is on the roadmap on ClipSpeed's rail; this page describes how it works and says so.

On the roadmapVerified end to end

Start for $1 Setup guide

Keep a human in the loop: Any MCP client shows the plan and asks before anything is public. Posting today: YouTube, TikTok, Instagram, X (Twitter) and LinkedIn.

Any MCP client

Turn docs/release-notes.md into a Dev.to article, tag it javascript and webdev, publish Tuesday 9am. Preview first.

Preview — nothing booked yet. Would schedule on: • Dev.to — title · text (Markdown) Times are in America/New_York. Book it?

via ClipSpeed · Dev.to

Also try

How to publish Dev.to from Any MCP client

Add the URL as an HTTP (streamable) MCP server. If the client can open a browser, sign in with OAuth. If it cannot, send an Authorization: Bearer header with a ClipSpeed API key. Connect Dev.to in ClipSpeed, then describe the post. Setup takes about a minute.

setup once, then just ask

# One-time setup: your client's MCP settings
https://api.clipspeed.ai/mcp

# Then ask Any MCP client:
> Turn docs/release-notes.md into a Dev.to article, tag it javascript and webdev, publish Tuesday 9am
Any MCP client: Preview — nothing booked yet. Dev.to — title. Book it?

The transport is streamable HTTP. There is nothing to install locally and nothing to update.

Add https://api.clipspeed.ai/mcp as an HTTP MCP server in your client.
Browser available: complete the ClipSpeed sign-in when the client opens it.
No browser: generate a key under Account → API & Integrations and send Authorization: Bearer csai_live_… on every request.
Connect Dev.to in the ClipSpeed app, or ask Any MCP client for a connect link: it is private, valid for ten minutes, and Dev.to signs you in itself.

Developer reference: the Any MCP client MCP page.

What can Any MCP client do on Dev.to?

On Dev.to, Any MCP client can publish Markdown articles with tags, a cover image and a series. Every booking runs through the same rules as the ClipSpeed app.

Text and Image posts

Dev.to takes text and image through ClipSpeed. Image: a cover image by URL.

Limits checked at booking

articles have no body limit; up to four tags. Titles are required and cap at 128.

Exact time or refused

Name the minute and Any MCP client books it, or you are told why not and offered the next open slot. A booked Dev.to post is never moved behind your back.

Preview before anything posts

preview: true runs the whole booking and writes nothing. Any MCP client shows the plan, with each slot and the day's remaining cap, and books only on your yes.

Clips cut in the same chat

Submit a video or stream link, get captioned 9:16 clips with a viral score, and post the best moment's hook on Dev.to with a link to the clip. No download, no re-upload.

Pacing and numbers

Planned: Text posts on Dev.to are at least 120 minutes apart, up to 3 a day. After a post goes out, Any MCP client can read back views and engagement where Dev.to provides them.

How does Any MCP client post to Dev.to through ClipSpeed?

You describe what you want in plain language and Any MCP client makes the ClipSpeed calls. A typical conversation has three beats.

Find your Dev.to channel

Ask Any MCP client whether Dev.to is connected. It calls list_channels and reads platform_settings, so it also knows what Dev.to accepts and the limits before you write a word.

Is my Dev.to account connected to ClipSpeed?

Dev.to is on the roadmap on ClipSpeed; I can't book there yet. Your YouTube channel is connected if you'd like to use that.

Compose within the rules

Describe the post. Any MCP client drafts within Dev.to's limits; mention a clip or a file and it attaches it.

Draft a Dev.to post about the launch.

Here's the draft: "…" Want me to schedule it?

Schedule or publish

Name a time, or say now. The slot is booked exactly or refused with the next open one, and the reply carries the id you can cancel or edit by.

Yes — tomorrow at 9am.

Scheduled on: • Dev.to — Tue, 9:00 AM · id 7c2… Times are in America/New_York.

Dev.to settings reference

These are the schedule_post fields that apply to Dev.to. Mention any of them in plain language and Any MCP client sets them; the server checks them at booking. Fields marked planned land with the Dev.to release.

Field	Type	Required	What it does on Dev.to
`platforms`	string[]	Yes	Include `"devto"`. Up to ten platforms per call; each books its own slot.
`title`	string	Yes	Up to 128 characters.
`text`	string	Yes	The article body in Markdown.
`hashtags`	string[]	No	Up to four Dev.to tags.
`series`	string	Planned	A series name to attach the article to.
`media_url`	string	No	The cover image.
`scheduled_at`	ISO 8601	No	Exact or refused with the next open slot.
`preview`	boolean	No	Plan only.

Common Dev.to configurations

Ask Any MCP client for any of these and it applies the matching settings.

Publish a post from the repo

Turn docs/release-notes.md into a Dev.to article, tag it javascript and webdev, publish Tuesday 9am

Got it. Applying: title · text (Markdown) · hashtags: 2

Series entry

Add it to the 'Shipping ClipSpeed' series

Got it. Applying: series

Cover image

Generate a 1000×420 cover and use it

Got it. Applying: generate_image → media_url

Draft first

Save it as a draft, don't publish

Got it. Applying: preview: true shows the plan; a draft field lands with the release

Example prompts for Dev.to in Any MCP client

Type these into any client that speaks the Model Context Protocol. Any MCP client calls ClipSpeed and confirms before publishing.

Just ask

Publish Dev.to with a scheduled time

Turn docs/release-notes.md into a Dev.to article, tag it javascript and webdev, publish Tuesday 9am. Preview first.

Clips first

Cut the clips, then post the hook

Clip this link, keep the top moment by viral score, and write a Dev.to post from the best moment's transcript, scheduled for tomorrow 9am. Show me the plan before booking.

Manage

Check and adjust the Dev.to calendar

What is scheduled on Dev.to this week? Cancel tomorrow's post and tell me the next open Dev.to slot on Friday.

Dev.to limits and gotchas to know

Dev.to enforces a few rules that Any MCP client and ClipSpeed respect automatically, but knowing them helps you phrase requests.

A title up to 128 characters is required. The body is Markdown with no hard limit.
Four tags maximum, and they must exist on Dev.to.
Dev.to is on ClipSpeed's roadmap, not the next rail. Bookings are refused plainly until it posts.
Canonical URL is a planned field for cross-posting from your own blog.
Pacing is conservative: three articles a day two hours apart.

Rule	Dev.to
Accepts	Text, Image
Text limit	articles have no body limit; up to four tags
Title	128 characters, required
Links in the caption	Kept; Markdown
Pacing	Planned: Text posts on Dev.to are at least 120 minutes apart, up to 3 a day.
Formats	Image: a cover image by URL. Aspect: 1000×420 cover
Status	On the roadmap; described here, not yet bookable

What Postiz-style schedulers cannot do

Cut the clips first

Any MCP client does not need finished video to start. Hand it a YouTube link, a podcast, a stream VOD or a local export. ClipSpeed finds the moments, cuts them to 9:16 with word-by-word captions, scores each one 0 to 100 for shareability, and returns them in the same conversation. Any MCP client picks by score, writes the post from the transcript, and books the best moments as links on Dev.to. Three tool calls, one approval, no download and no re-upload.

Clips arrive with a title written from the hook, a transcript and a viral score, so the agent can choose and caption without watching the footage.
Live streams can be clipped while they are still on air; the agent books the highlights for the next morning before the stream ends.
Every clip is already hosted, so schedule_post takes its id directly. Nothing moves through your laptop.

submit_to_clipspeedPaste the link. ClipSpeed starts the job and returns a project id.

check_clipsPoll with the project id. Back come the finished 9:16 clips with titles, transcripts, viral scores and preview links.

schedule_postPass the clip id, the platforms, a caption and a time. Any MCP client shows the plan with preview: true, you say yes, it books.

generate_image or generate_videoDescribe the shot. ClipSpeed runs it on the model that fits (Seedance, Kling, Veo, Nano Banana Pro, GPT Image and others) and quotes the credits first.

wait_for_generationReturns the hosted result link and a preview the agent can show you.

schedule_post with media_urlThe result link goes straight into the booking on Dev.to. The caption, the time and the file are approved together.

The other half nobody else has

Generate the image, then post it

A product shot for Instagram, a 16:9 announcement graphic for X, a six-second opener before a clip: Any MCP client can make an image with ClipSpeed's image and video models and book the result in the same reply. There is no separate design tool, no export, no upload page. The generated file is hosted, so media_url is the only thing the booking needs.

The price in credits is quoted before anything renders, within the per-generation and daily caps you set in Settings.
Results are previewed in the conversation, so you approve the picture and the post at once.
Images post as JPG, PNG or WebP up to 25 MB; links are kept clickable.

What is Any MCP client?

The ClipSpeed MCP server is a hosted Model Context Protocol server over streamable HTTP. Any client that can add an HTTP MCP server, from Claude and ChatGPT to a self-hosted agent, gets the same tools: list and connect channels, read platform rules, schedule and manage posts, read analytics, clip videos and generate images and video.

How ClipSpeed works with Any MCP client

Streamable HTTP transport; tools are advertised at handshake
list_channels, connect_channel, platform_settings, schedule_post, list_scheduled_posts, update_scheduled_post, cancel_scheduled_post, post_analytics for scheduling
submit_to_clipspeed, check_clips and the live-clipping tools for clipping
generate_image, generate_video, wait_for_generation for creation
Every booking runs through the same rules as the web app

Hosted MCP vs stdio package vs CLI: Hosted MCP server (api.clipspeed.ai), clipspeed-mcp (npm) (your machine, stdio), ClipSpeed CLI (your machine). This page is about Any MCP client; the Any MCP client guide compares them.

generic MCP config

{
  "mcpServers": {
    "clipspeed": {
      "url": "https://api.clipspeed.ai/mcp",
      "headers": { "Authorization": "Bearer csai_live_..." }   // omit for OAuth
    }
  }
}

# Prove the round trip without starting any work:
#   call list_channels → your connected platforms and your time zone

tool list (abridged)

# What the agent reads at connect time (tool descriptions, abridged)
list_channels           Connected platforms, what each accepts, limits, your time zone
connect_channel         A private 10-minute link to connect one platform
platform_settings       Limits, title rules, link handling, pacing per platform
schedule_post           clip_id | text | media_url → platforms[], scheduled_at, preview
list_scheduled_posts    Scheduled, sending, posted, failed — with post links
update_scheduled_post   Edit copy while still scheduled (the time never moves)
cancel_scheduled_post   Cancel; undoable 72 h in the app
post_analytics          Views, likes, comments, shares where the platform gives them
submit_to_clipspeed     Start clipping a video or stream link → projectId
check_clips             Finished 9:16 clips with titles, transcripts, viral scores
generate_image / generate_video / wait_for_generation

# Dev.to: text/image · text n/a · title 128 required

Publish to Dev.to and other platforms from Any MCP client

One request can book the same content to Dev.to and other channels, each keeping its own settings and its own slot. Every platform below has its own Any MCP client guide.

Post the launch to Dev.to and Hashnode tomorrow at 9am, then a daily tip on Hashnode every weekday at 10am. Preview first.

Preview — nothing booked yet: • Dev.to — Tue 9:00 AM (refused: on the roadmap) • Hashnode — Tue 9:00 AM (refused: on the roadmap) • Hashnode daily tips — Mon–Fri 10:00 AM Book it?

Publish to Hashnode from Any MCP client →Publish to Medium from Any MCP client →Publish to WordPress from Any MCP client →Post to LinkedIn from Any MCP client →Post to X (Twitter) from Any MCP client →Every platform for Any MCP client →Dev.to scheduler features →

Also works with

CLPublish to Dev.to from Claude →CHPublish to Dev.to from ChatGPT →CCPublish to Dev.to from Claude Code →CDPublish to Dev.to from Claude Desktop →

Dev.to and Any MCP client: frequently asked questions

How do I publish to Dev.to from Any MCP client?

Add https://api.clipspeed.ai/mcp as an HTTP MCP server in your client. Browser available: complete the ClipSpeed sign-in when the client opens it. Connect Dev.to in ClipSpeed (or ask Any MCP client for a connect link; it is private and valid for ten minutes), then describe the post in plain language. Any MCP client reads the Dev.to rules, drafts within them, shows the plan and books on your yes. Dev.to is on the roadmap; until the badge changes, the booking is refused with a plain message.

What can Any MCP client post to Dev.to through ClipSpeed?

Publish Markdown articles with tags, a cover image and a series. Dev.to takes text and image posts. A title is required and is capped at 128 characters.

Which Dev.to settings can Any MCP client control?

The fields in the settings reference above: title, text, hashtags, series, media_url, scheduled_at, preview. Mention any of them in plain language ("unlisted", "tomorrow at 9", "preview first") and Any MCP client sets the matching field before it books.

Do I need a Dev.to API key or developer account?

No. You connect Dev.to to ClipSpeed once through Dev.to's own sign-in, and Any MCP client talks to ClipSpeed over OAuth. No Dev.to developer key, bearer token or password is pasted anywhere.

How many Dev.to posts a day can Any MCP client schedule?

Planned: Text posts on Dev.to are at least 120 minutes apart, up to 3 a day. When a time is taken, the booking is refused with the next open slot rather than moved. Ask for preview to see a day's plan and the remaining cap before anything is booked.

Can posts go out to Dev.to while I am away?

Yes. Once booked, ClipSpeed publishes at the scheduled minute whether or not Any MCP client is open. For unattended runs that decide what to post, use a headless agent such as Claude Code or Codex with the same account.

Is posting to Dev.to from Any MCP client different from clipspeed-mcp (npm)?

The booking is identical: the same rules, the same calendar, the same refusals. What differs is where you work. Any MCP client: hosted at api.clipspeed.ai. clipspeed-mcp (npm): your machine, stdio, local process; clipping plus clip scheduling.