Claude writes the caption and the hook for your video, you choose who can see it, and it goes out now or on schedule from the chat, publicly, through a TikTok-audited app.
Free for 2 social accounts. No card, no API key.
Free plan works. It allows one custom connector.
On a phone? In the Claude app: Settings, Connectors, Add custom connector. Paste the same name and URL.
Free plan works. It allows one custom connector.
Ask Claude things like these. It shows you the post before anything is scheduled or published.
“Write a caption for this clip of the kitchen prep and post it tonight.”

TikTok needs a video on every post. Attach it in the chat, or add it from the draft's link in Antwork.
“Write it like my last few captions, and shorter.”
Claude reads the captions on your recent public videos first, so the draft keeps your tone, length and hashtags.
“Send me the TikTok settings for this draft.”
TikTok asks on every post who can view it and whether comments, duets and stitches are on. You choose, in the chat or in Antwork; nothing is preset.
“Plan four TikToks for next week, every other day.”
Claude lays out the week and tells you what's already queued.
“My post failed to publish. Find out why and retry it.”
A failed post comes back with the reason. Retrying it is one message.
Yes, through a connector.
Claude can post to TikTok through Antwork, a hosted Model Context Protocol (MCP) connector. You add Antwork's server URL as a custom connector in Claude, connect TikTok once on TikTok's own login screen, and from then on Claude writes the caption and hook, schedules and publishes your videos from inside the conversation. Antwork posts through its own TikTok app, which passed TikTok's Direct Post audit on 19 October 2026, and that matters here: TikTok limits apps that have not passed it to private posts, so a do-it-yourself TikTok MCP server on your own developer app can only post videos that nobody else can see.
TikTok MCP servers compared: which can post publicly, and which only read or scrapeClaude checks these before it drafts, so a post does not fail at publish time. They come from the same rules Antwork's publisher enforces.
Each works. They differ in where the work happens and how much you set up.
| Antwork connector | An automation tool | Build your own | |
|---|---|---|---|
| Where you ask | In the Claude chat | In a workflow you build | In your own code |
| Setup | Paste one URL, sign in | Design a scenario per task | Developer app, API access, hosting |
| Writes in your voice | Reads your recent posts | Only what you wire in | Only what you build |
| Schedules and publishes | Yes, from the chat | On the workflow's trigger | If you build it |
| Shows the post first | Every time | Depends on the workflow | Depends on your build |
| Code needed | None | None | Yes |
An automation tool is the better fit when a post should be triggered by something outside the chat, like a new row in a spreadsheet. If you want to ask Claude and see the post, the connector is the shortest path.