Claude writes the title and description for your video, you pick public, unlisted or private, and it uploads to your channel now or on schedule once you approve.
Free for 2 social accounts. No card, no API key.
On a phone? Add it once in claude.ai in your browser, not the Claude app. It then works in the app too.
Free plan works. It allows one custom connector.
Write the title and description for this video of our autumn menu, in our usual voice.
Read your last 15 YouTube postsHere's a draft in the tone of your recent posts. It goes out only once you confirm.

Our autumn menu is in. Three new dishes, one returning favourite, and the pumpkin soup we have been testing since August. Tables for Friday are open now.
Yes, through a connector.
Claude can upload videos to YouTube through Antwork, a hosted Model Context Protocol (MCP) connector. You add Antwork's server URL as a custom connector in Claude, connect your YouTube channel once on Google's own sign-in screen, and from then on Claude writes the title and description, then publishes or schedules your video from inside the conversation, as public, unlisted or private. There is no Google Cloud project to create, no YouTube Data API to enable and no OAuth client to configure, because Antwork runs the server. Antwork's Google project has passed YouTube's API compliance audit, which matters here: YouTube locks uploads from unaudited projects to private, so a video you publish as public through Antwork is actually public.
Copy one into Claude to try it. Claude always shows you the post before anything is scheduled or published.
Claude 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.