Publish to WordPress from Kimi Code
Kimi Code can publish posts on WordPress through ClipSpeed. Add the ClipSpeed server with one config block, sign in, and then ask Kimi Code to publish posts, pick the time, and apply WordPress's settings, without leaving the Kimi Code CLI. WordPress is on the roadmap on ClipSpeed's rail; this page describes how it works and says so.
Keep a human in the loop: Kimi Code shows the plan and asks before anything is public. Posting today: YouTube, TikTok, Instagram, X (Twitter) and LinkedIn.
Also try
How to publish WordPress from Kimi Code
Add ClipSpeed as an HTTP MCP server in Kimi Code's configuration, complete the sign-in, and the tools appear. Connect WordPress in ClipSpeed, then describe the post. Setup takes about a minute.
# One-time setup: Kimi Code MCP config
{
"mcpServers": {
"clipspeed": { "url": "https://api.clipspeed.ai/mcp" }
}
}
# Then ask Kimi Code:
> Publish the article on the main site Tuesday 8am under News
Kimi Code: Preview — nothing booked yet. WordPress — title. Book it?ClipSpeed has not yet run an end-to-end check inside Kimi Code. The server is standard MCP over HTTP.
- Add the clipspeed server with the URL to Kimi Code's MCP configuration (its docs name the file).
- Start Kimi Code; complete the ClipSpeed sign-in, or use an API key header.
- Ask it to list your channels.
- Connect WordPress in the ClipSpeed app, or ask Kimi Code for a connect link: it is private, valid for ten minutes, and WordPress signs you in itself.
What can Kimi Code do on WordPress?
On WordPress, Kimi Code 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 Kimi Code 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. Kimi Code shows the plan, with each slot and the day's remaining cap, and books only on your yes.
Clips cut in the same session
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, Kimi Code can read back views and engagement where WordPress provides them.
How does Kimi Code post to WordPress through ClipSpeed?
You describe what you want in plain language and Kimi Code makes the ClipSpeed calls. A typical conversation has three beats.
Find your WordPress channel
Ask Kimi Code 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.
Compose within the rules
Describe the post. Kimi Code drafts within WordPress's limits; mention a clip or a file and it attaches 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.
WordPress settings reference
These are the schedule_post fields that apply to WordPress. Mention any of them in plain language and Kimi Code 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 Kimi Code for any of these and it applies the matching settings.
Post to one site
Featured image
Two sites
Preview
Example prompts for WordPress in Kimi Code
Type these into the Kimi Code CLI. Kimi Code calls ClipSpeed and confirms before publishing.
Publish WordPress with a scheduled time
Publish the article on the main site Tuesday 8am under News. Preview 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.
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 Kimi Code 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
Kimi Code 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. Kimi Code 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_posttakes 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. Kimi Code 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: Kimi Code 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 Kimi Code?
Kimi Code is Moonshot AI's coding agent for the terminal, built on the Kimi models. It runs tasks in your project and connects to MCP servers. With ClipSpeed registered, it can clip videos, generate media and schedule posts.
How ClipSpeed works with Kimi Code
- Connects over HTTP
- Reads platform rules
- Exact-or-refused booking
preview: true- Same tools everywhere
Kimi Code vs DeepSeek vs Claude Code: Kimi Code (terminal), DeepSeek (terminal / plugin surfaces), Claude Code (terminal). This page is about Kimi Code; the Kimi Code guide compares them.
{
"mcpServers": {
"clipspeed": {
"url": "https://api.clipspeed.ai/mcp"
// or: "headers": { "Authorization": "Bearer csai_live_..." }
}
}
}# 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/aPublish to WordPress and other platforms from Kimi Code
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 Kimi Code guide.
Also works with
WordPress and Kimi Code: frequently asked questions
How do I publish to WordPress from Kimi Code?
Add the clipspeed server with the URL to Kimi Code's MCP configuration (its docs name the file). Start Kimi Code; complete the ClipSpeed sign-in, or use an API key header. Connect WordPress in ClipSpeed (or ask Kimi Code for a connect link; it is private and valid for ten minutes), then describe the post in plain language. Kimi Code 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 Kimi Code 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 Kimi Code 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 Kimi Code 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 Kimi Code talks to ClipSpeed over OAuth. No WordPress developer key, bearer token or password is pasted anywhere.
How many WordPress posts a day can Kimi Code 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 posts go out to WordPress while I am away?
Yes. Once booked, ClipSpeed publishes at the scheduled minute whether or not Kimi Code 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 WordPress from Kimi Code different from DeepSeek?
The booking is identical: the same rules, the same calendar, the same refusals. What differs is where you work. Kimi Code: terminal. DeepSeek: terminal / plugin surfaces, plugin model.