NAnanoclaw+WPWordPress

Publish to WordPress from nanoclaw

nanoclaw can publish posts on WordPress through ClipSpeed. Add the ClipSpeed server with one config block, sign in, and then ask nanoclaw to publish posts, pick the time, and apply WordPress's settings, without leaving a small self-hosted agent you message from WhatsApp or Telegram. WordPress is on the roadmap on ClipSpeed's rail; this page describes how it works and says so.

On the roadmapStandard MCP route · not yet verified by us

Start for $1 Setup guide

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

nanoclaw

Publish the article on the main site Tuesday 8am under News. Preview first.

Preview — nothing booked yet. Would schedule on: • WordPress — title · text Times are in America/New_York. Book it?

via ClipSpeed · WordPress

Also try

How to publish WordPress from nanoclaw

nanoclaw has no browser for OAuth, so it uses a ClipSpeed API key in a header. Generate the key, add the server, restart. Connect WordPress in ClipSpeed, then describe the post. Setup takes about a minute.

setup once, then just ask

# One-time setup: nanoclaw MCP config
{
  "mcpServers": {
    "clipspeed": {
      "url": "https://api.clipspeed.ai/mcp",
      "headers": { "Authorization": "Bearer csai_live_..." }
    }
  }
}

# Then ask nanoclaw:
> Publish the article on the main site Tuesday 8am under News
nanoclaw: Preview — nothing booked yet. WordPress — title. Book it?

nanoclaw sits in the compatible tier: same protocol as the verified clients, not yet driven end to end by ClipSpeed.

Generate a key in ClipSpeed under Account → API & Integrations.
Add the clipspeed server with the URL and Authorization header to nanoclaw's MCP configuration.
Restart nanoclaw and message it: list my ClipSpeed channels.
Connect WordPress in the ClipSpeed app, or ask nanoclaw for a connect link: it is private, valid for ten minutes, and WordPress signs you in itself.

Developer reference: the nanoclaw MCP page.

What can nanoclaw do on WordPress?

On WordPress, nanoclaw can publish posts with a featured image, categories and tags to your WordPress sites. Every booking runs through the same rules as the ClipSpeed app.

Text and Image posts

WordPress takes text and image through ClipSpeed. Image: a featured image by URL.

Limits checked at booking

No fixed text limit. Titles are required.

Exact time or refused

Name the minute and nanoclaw books it, or you are told why not and offered the next open slot. A booked WordPress post is never moved behind your back.

Preview before anything posts

preview: true runs the whole booking and writes nothing. nanoclaw 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 WordPress with a link to the clip. No download, no re-upload.

Pacing and numbers

Planned: Text posts on WordPress are at least 60 minutes apart, up to 5 a day. After a post goes out, nanoclaw can read back views and engagement where WordPress provides them.

How does nanoclaw post to WordPress through ClipSpeed?

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

Find your WordPress channel

Ask nanoclaw whether WordPress is connected. It calls list_channels and reads platform_settings, so it also knows what WordPress accepts and the limits before you write a word.

Is my WordPress account connected to ClipSpeed?

WordPress 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. nanoclaw drafts within WordPress's limits; mention a clip or a file and it attaches it.

Draft a WordPress 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: • WordPress — Tue, 9:00 AM · id 7c2… Times are in America/New_York.

WordPress settings reference

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

Field	Type	Required	What it does on WordPress
`platforms`	string[]	Yes	Include `"wordpress"`. Up to ten platforms per call; each books its own slot.
`title`	string	Yes	The post title.
`text`	string	Yes	The body in HTML or Markdown.
`categories / tags`	string[]	Planned	Existing categories and tags on the site.
`site`	string	Planned	Which connected site, when you have several.
`media_url`	string	No	The featured image.
`scheduled_at`	ISO 8601	No	Exact or refused with the next open slot.
`preview`	boolean	No	Plan only.

Common WordPress configurations

Ask nanoclaw for any of these and it applies the matching settings.

Post to one site

Publish the article on the main site Tuesday 8am under News

Got it. Applying: title · text · categories · site

Featured image

Generate a featured image and use it

Got it. Applying: generate_image → media_url

Two sites

Publish on both sites an hour apart

Got it. Applying: two bookings

Preview

Show me the plan first

Got it. Applying: preview: true

Example prompts for WordPress in nanoclaw

Type these into a small self-hosted agent you message from WhatsApp or Telegram, or pass one to routine in a script. nanoclaw calls ClipSpeed and confirms before publishing.

Just ask

Publish WordPress with a scheduled time

Publish the article on the main site Tuesday 8am under News. Preview first.

Clips first

Cut the clips, then post the hook

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

Manage

Check and adjust the WordPress calendar

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

WordPress limits and gotchas to know

WordPress enforces a few rules that nanoclaw and ClipSpeed respect automatically, but knowing them helps you phrase requests.

Works with self-hosted WordPress through the REST API and an application password you create on the site; ClipSpeed never asks for your admin password in chat.
Categories and tags must exist on the site.
WordPress is on ClipSpeed's roadmap, not the next rail. Bookings are refused plainly until it posts.
Pages are not a target; posts are.
Planned pacing: five posts a day an hour apart.

Rule	WordPress
Accepts	Text, Image
Text limit	No fixed limit
Title	No title field
Links in the caption	Kept
Pacing	Planned: Text posts on WordPress are at least 60 minutes apart, up to 5 a day.
Formats	Image: a featured image by URL. Aspect: any
Status	On the roadmap; described here, not yet bookable

What Postiz-style schedulers cannot do

Cut the clips first

nanoclaw 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. nanoclaw picks by score, writes the post from the transcript, and books the best moments as links on WordPress. 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. nanoclaw 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 WordPress. 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: nanoclaw 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 nanoclaw?

nanoclaw is a minimal open-source personal agent in the OpenClaw family: it runs on your own machine, takes instructions from WhatsApp or Telegram, and can call MCP servers. With ClipSpeed configured with an API key, a message to your agent can clip a video and schedule posts.

How ClipSpeed works with nanoclaw

Connects over HTTP with a Bearer key
Reads platform rules
Exact-or-refused booking
preview: true for plans it messages you
Same tools everywhere

nanoclaw vs OpenClaw vs Hermes Agent: nanoclaw (your machine; whatsapp, telegram), OpenClaw (your machine; many channels), Hermes Agent (your server). This page is about nanoclaw; the nanoclaw guide compares them.

nanoclaw MCP config

{
  "mcpServers": {
    "clipspeed": {
      "url": "https://api.clipspeed.ai/mcp",
      "headers": { "Authorization": "Bearer ${CLIPSPEED_API_KEY}" }
    }
  }
}

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

# WordPress: text/image · text n/a

Publish to WordPress and other platforms from nanoclaw

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

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

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

Publish to Medium from nanoclaw →Publish to Dev.to from nanoclaw →Publish to Hashnode from nanoclaw →Post to LinkedIn from nanoclaw →Post to Facebook from nanoclaw →Every platform for nanoclaw →WordPress scheduler features →

Also works with

CLPublish to WordPress from Claude →CHPublish to WordPress from ChatGPT →CCPublish to WordPress from Claude Code →CDPublish to WordPress from Claude Desktop →

WordPress and nanoclaw: frequently asked questions

How do I publish to WordPress from nanoclaw?

Generate a key in ClipSpeed under Account → API & Integrations. Add the clipspeed server with the URL and Authorization header to nanoclaw's MCP configuration. Connect WordPress in ClipSpeed (or ask nanoclaw for a connect link; it is private and valid for ten minutes), then describe the post in plain language. nanoclaw reads the WordPress rules, drafts within them, shows the plan and books on your yes. WordPress is on the roadmap; until the badge changes, the booking is refused with a plain message.

What can nanoclaw post to WordPress through ClipSpeed?

Publish posts with a featured image, categories and tags to your WordPress sites. WordPress takes text and image posts.

Which WordPress settings can nanoclaw control?

The fields in the settings reference above: title, text, categories / tags, site, media_url, scheduled_at, preview. Mention any of them in plain language ("unlisted", "tomorrow at 9", "preview first") and nanoclaw sets the matching field before it books.

Do I need a WordPress API key or developer account?

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

How many WordPress posts a day can nanoclaw schedule?

Planned: Text posts on WordPress are at least 60 minutes apart, up to 5 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 nanoclaw post to WordPress from a script or a cron job?

Yes. nanoclaw's headless mode (routine) runs one prompt and exits, and the ClipSpeed server registered on that machine does the booking. On a runner with no browser, authenticate with a ClipSpeed API key header. Keep preview on so the run reports a plan before it books.

Is posting to WordPress from nanoclaw different from OpenClaw?

The booking is identical: the same rules, the same calendar, the same refusals. What differs is where you work. nanoclaw: your machine; whatsapp or telegram. OpenClaw: your machine; many channels, more integrations.