KCKimi Code+Dribbble

Post to Dribbble from Kimi Code

Kimi Code can publish shots on Dribbble through ClipSpeed. Add the ClipSpeed server with one config block, sign in, and then ask Kimi Code to publish shots, pick the time, and apply Dribbble's settings, without leaving the Kimi Code CLI. Dribbble 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: Kimi Code shows the plan and asks before anything is public. Posting today: YouTube, TikTok, Instagram, X (Twitter) and LinkedIn.

Kimi Code

Publish the dashboard shot Tuesday 10am with a title and five tags. Preview first.

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

via ClipSpeed · Dribbble

Also try

How to post Dribbble from Kimi Code

Add ClipSpeed as an HTTP MCP server in Kimi Code's configuration, complete the sign-in, and the tools appear. Connect Dribbble in ClipSpeed, then describe the post. Setup takes about a minute.

setup once, then just ask

# One-time setup: Kimi Code MCP config
{
  "mcpServers": {
    "clipspeed": { "url": "https://api.clipspeed.ai/mcp" }
  }
}

# Then ask Kimi Code:
> Publish the dashboard shot Tuesday 10am with a title and five tags
Kimi Code: Preview — nothing booked yet. Dribbble — 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 Dribbble in the ClipSpeed app, or ask Kimi Code for a connect link: it is private, valid for ten minutes, and Dribbble signs you in itself.

What can Kimi Code do on Dribbble?

On Dribbble, Kimi Code can publish shots with a title, description and tags. Every booking runs through the same rules as the ClipSpeed app.

Image and Video posts

Dribbble takes image and video through ClipSpeed. Video: MP4 up to 24 seconds on Dribbble. Image: JPG, PNG or GIF at 4:3, 1600×1200 recommended.

10,000 characters, checked at booking

Dribbble's own arithmetic. Too long is refused with the real count, never trimmed at send time. Titles are required and cap at 50.

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 Dribbble 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 as native video on Dribbble. No download, no re-upload.

Pacing and numbers

Planned: Image posts on Dribbble are at least 240 minutes apart, up to 2 a day. After a post goes out, Kimi Code can read back views and engagement where Dribbble provides them.

How does Kimi Code post to Dribbble 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 Dribbble channel

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

Is my Dribbble account connected to ClipSpeed?

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

Draft a Dribbble post about the launch with the best clip from the demo.

Here's the draft (8000/10,000): "…" Clip 2 (score 88) attached. 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: • Dribbble — Tue, 9:00 AM · id 7c2… Times are in America/New_York.

Dribbble settings reference

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

Field	Type	Required	What it does on Dribbble
`platforms`	string[]	Yes	Include `"dribbble"`. Up to ten platforms per call; each books its own slot.
`title`	string	Yes	Up to 50 characters.
`text`	string	No	The description.
`hashtags`	string[]	No	Up to 20 tags.
`media_url`	string	Yes	A 4:3 image, or a video up to 24 seconds.
`scheduled_at`	ISO 8601	No	Exact or refused with the next open slot.
`preview`	boolean	No	Plan only.

Common Dribbble configurations

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

Shot from a design export

Publish the dashboard shot Tuesday 10am with a title and five tags

Got it. Applying: title · hashtags: 5 · media_url

Generated 4:3 mockup

Generate a 4:3 mockup of the app on a desk and publish it

Got it. Applying: generate_image → media_url

Short video shot

Publish the 15-second UI animation

Got it. Applying: media_url: MP4 under 24 s

Preview

Plan a shot a week for the month, show me first

Got it. Applying: preview: true

Example prompts for Dribbble in Kimi Code

Type these into the Kimi Code CLI. Kimi Code calls ClipSpeed and confirms before publishing.

Just ask

Post Dribbble with a scheduled time

Publish the dashboard shot Tuesday 10am with a title and five tags. Keep the text under 10,000 characters. Preview first.

Clips first

Cut the clips, then post the best

Clip this link, keep the top three by viral score, and schedule them to Dribbble at 11am, 3pm and 7pm tomorrow with titles written from each hook. Show me the plan before booking.

Manage

Check and adjust the Dribbble calendar

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

Dribbble limits and gotchas to know

Dribbble enforces a few rules that Kimi Code and ClipSpeed respect automatically, but knowing them helps you phrase requests.

Shots are 4:3; 1600×1200 is the recommended size. Video shots are capped at 24 seconds.
A title up to 50 characters is required.
Publishing requires a Dribbble account with shot-posting access.
Dribbble is on ClipSpeed's roadmap, not the next rail. Bookings are refused plainly until it posts.
Pacing is tight: two shots a day.

Rule	Dribbble
Accepts	Image, Video
Text limit	10,000 characters
Title	50 characters, required
Links in the caption	Kept in the description
Pacing	Planned: Image posts on Dribbble are at least 240 minutes apart, up to 2 a day.
Formats	Image: JPG, PNG or GIF at 4:3, 1600×1200 recommended. Video: MP4 up to 24 seconds on Dribbble. Aspect: 4:3
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 caption from the transcript, and books the clips on Dribbble. 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. 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 Dribbble. The caption, the time and the file are approved together.

The other half nobody else has

Generate the image or video, 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 or a short video 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; video posts as MP4, MOV or WebM up to 1 GB.

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.

MCP config

{
  "mcpServers": {
    "clipspeed": {
      "url": "https://api.clipspeed.ai/mcp"
      // or: "headers": { "Authorization": "Bearer csai_live_..." }
    }
  }
}

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

# Dribbble: image/video · text 10,000 · title 50 required

Post to Dribbble and other platforms from Kimi Code

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

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

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

Post to Instagram from Kimi Code →Pin to Pinterest from Kimi Code →Post to X (Twitter) from Kimi Code →Post to LinkedIn from Kimi Code →Upload to YouTube from Kimi Code →Every platform for Kimi Code →Dribbble scheduler features →

Also works with

CLPost to Dribbble from Claude →CHPost to Dribbble from ChatGPT →CCPost to Dribbble from Claude Code →CDPost to Dribbble from Claude Desktop →

Dribbble and Kimi Code: frequently asked questions

How do I post to Dribbble 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 Dribbble 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 Dribbble rules, drafts within them, shows the plan and books on your yes. Dribbble is on the roadmap; until the badge changes, the booking is refused with a plain message.

What can Kimi Code post to Dribbble through ClipSpeed?

Publish shots with a title, description and tags. Dribbble takes image and video posts; a text-only request is refused with a message naming what it accepts. Text is limited to 10,000 characters. A title is required and is capped at 50 characters.

Which Dribbble settings can Kimi Code control?

The fields in the settings reference above: title, text, hashtags, 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 Dribbble API key or developer account?

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

How many Dribbble posts a day can Kimi Code schedule?

Planned: Image posts on Dribbble are at least 240 minutes apart, up to 2 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 Dribbble 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 Dribbble 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.