Kick tools in your terminal
Over MCP, scheduling and analytics show up as first-class tools. Over the CLI, every command returns JSON that Claude Code can chain reliably for Kick.
Queue Kick clips and updates from your terminal. Claude Code drives postqueen over MCP or the CLI, so scheduling happens in the session you already have open.
Register the postqueen MCP server once and Kick scheduling becomes a tool Claude Code can call. The plain CLI works too.
MCP supported# Add the postqueen MCP serverclaude mcp add --transport http postqueen \ https://api.postqueen.ai/mcp/YOUR_API_KEY # Then ask in your session:# "Queue three Kick clips for this# week, mornings at 9"Over MCP, scheduling and analytics show up as first-class tools. Over the CLI, every command returns JSON that Claude Code can chain reliably for Kick.
Tell Claude Code when your followers are most active and it schedules clips into that window on Kick, day after day, without reminders.
Video uploads travel through the same postqueen call, so Claude Code ships Kick clips and updates with real media attached and the publish time already set.
Ask Claude Code for drafts only. They sit on the postqueen calendar unscheduled, so you can edit them and pick the time yourself, and nothing reaches your followers on Kick until you do.
Claude Code calls postqueen to list your connected channels and sees what Kick supports, so drafts start from real capabilities, not guesses.
Give it the brief. The agent writes Kick-shaped clips and updates and proposes publish times that match when your followers are around.
Look over the queue on the postqueen calendar and change anything you want. postqueen publishes each post at its time, and Claude Code can pull the results after.
Claude Code reads these limits from postqueen before it composes, so a draft that would be rejected never reaches the queue.
Scheduling, AI drafts, analytics and team roles, in one guide.
Over MCP, registered once in Claude Code's own config so the Kick tools are there in every session. It also runs commands, so the CLI covers the same Kick clips and updates when you would rather script them; both use the same API key.
Yes. Give it exact slots or a rule like mornings at nine and it sets publish times on the clips it creates, so your followers see them at the right moment.
Only if you ask it to. Tell it to save drafts and nothing is scheduled: the clips wait on the calendar until you set a time. Tell it to schedule, and they go out at the times you can see, which is the setup most people move to once they trust the output.
Yes. postqueen connects 30 channels, so Claude Code can turn the same brief into Kick clips and updates plus adapted versions for every other channel you run.
No. The agent uses your regular API key and plan limits: unlimited posts on every plan, and channel counts from 5 on Creator up to uncapped on Ultimate.
A Kick account and an OAuth connection to a channel you own. Kick runs a developer portal where app credentials are issued, and postqueen uses that official path rather than scraping the site. You can revoke the authorization from Kick at any time.
Yes, and it is the highest-leverage thing to automate here. Clips are short, which makes them the easiest asset to reuse across networks: send one to TikTok, YouTube and X from a single composer with a caption per platform. They come out of a landscape stream though, so a vertical crop is worth doing before it reaches Shorts or TikTok. Each network receives a native upload, not a link back to Kick.
Queue this week's posts in minutes, or hand the whole thing to your favorite AI. postqueen keeps publishing either way.
Seven days free. Cancel in one click from settings.