How-To Guide
How do you post to social media with Claude?
How to post to social media with Claude: which connectors publish, which platforms they cover, and the first-post checklist.
By the Superdirector editorial team. Connector documentation, the Model Context Protocol introduction and the platform publishing docs were read November 15, 2026. Competitor connector guides from Blotato and Genviral were read the same day. Offer wording follows the live pricing and how-it-works pages read November 15, 2026.
At a glance
How do you post to social media with Claude?
Claude cannot publish to a social platform by itself. A post leaves Claude through a tool that holds your account connection: normally a remote MCP server you add as a custom connector, or an operated service such as Superdirector Growth. The connector performs the publish, and each platform still applies its own API rules, permissions and limits. If you want to work inside Claude, the $29 Starter plan gives you research, ideas and drafts and does not post. If you want an account that publishes eligible Instagram carousels and single X text posts by itself, the $199 Growth plan runs the account after one account-level warning.
- Claude is the control layer. The connector or operated account is the layer that reaches the platform.
- Platform approval stays with the account owner: Meta App Review, a TikTok API audit, YouTube quota and X API credentials do not disappear because a connector is easy to add.
- Match the route to the job: a connector for many platforms from inside Claude, Growth for an operated Instagram and X account.
One draft, three owners for the publish. The fork is the decision: a hosted connector publishes through its own tools, your own app publishes but leaves approval and upkeep with you, and an operated Superdirector account publishes only its Instagram and X output. Original diagram, drawn from the route comparison above; no vendor interface is depicted.
Make it work for your brand
Find it. Remake it. Post it. Superdirector turns the viral formats in your niche into your brand's carousels, X posts and video scripts, and keeps the calendar full.
Decide who does the publishing
Claude is good at the part before publishing: reading a source, shaping an angle, writing a caption and checking a claim. It cannot send that caption to Instagram, TikTok, X, YouTube or LinkedIn on its own. The Model Context Protocol is the open standard that lets an AI application call an outside tool, and a publishing connector uses it to expose actions such as list accounts, upload media, create a post or schedule one.
That division is the whole decision. Claude decides what to say. The connector holds the account authorization and performs the platform call. Claude's custom connector documentation puts the boundary plainly: remote MCP servers give Claude tools it can invoke, and Claude can only access resources that you have given the server permission to access. The connector never needs to hand Claude your password; OAuth grants a scoped permission instead.
One more detail matters for setup. Claude reaches a remote connector from Anthropic's cloud infrastructure, not from your laptop, so the server must be reachable on the public internet over HTTPS port 443. A connector that only works on a private network will fail even if your own browser can open it.
Compare the three routes
There are three honest ways to get a post live, and they put the approval burden in different places.
| Route | What you set up | Who performs the publish | Where it breaks |
|---|---|---|---|
| Hosted MCP connector | Add the connector in Claude, complete OAuth, approve the tools you need | The connector service holds the account and calls the platform API | Its tool list decides which platforms and formats work; its own plan and limits apply |
| Your own API app | Register a developer app per platform, request scopes, pass review or audit, store tokens, expose it to Claude | Your server or code | Approval, token refresh and every platform change are yours to maintain |
| Operated account | Turn on posting for a Superdirector Growth account | Superdirector publishes the account's eligible Instagram carousels and single X text posts | It is not a way to post to every platform from a Claude chat; it runs the account's own Instagram and X output |
Connector guides describe the same split from the vendor side. Blotato's guide says Claude cannot publish to a social platform on its own, and that the MCP server gives it that ability. Genviral's guide calls Claude the control layer while the connector performs the social actions through the permissions you approve. Neither claim makes the platform's own approval disappear; a connector can absorb the setup work, but the API gate still exists underneath.
Connect a publishing connector to Claude
The mechanical setup is short. The review step is the one that prevents a wrong-account post.
- In the connector service, connect the social accounts you actually use. Authorize each account once, and note which workspace or brand it belongs to.
- In Claude, open Customize, then Connectors, and add the remote MCP server URL as a custom connector. The directory route works too when the service is listed.
- Complete OAuth and review the requested permissions. Approve the tools the workflow needs, such as listing accounts, reading media and creating a scheduled post. Leave generation or inbox tools off when you do not need them.
- Ask Claude to list the connected accounts. An empty list means the connector is working but no account is attached yet.
- Create one scheduled post, not an immediate one. Put the account name, asset, caption and an explicit time zone in the request, then inspect the scheduled result before it goes live.
A free Claude account can hold one custom connector, so choose the service before you fill that slot. On a Team or Enterprise plan an owner may need to add the connector before members can connect it. If the connector appears connected but every call fails, check the account selection and the tool permissions before rebuilding anything.
Match the post to each platform's rules
A connector can hide the setup, but it cannot erase the platform's gate. Read the gate before you promise a client or a founder that a post will go live today.
| Platform | What API publishing requires | Limit or guard to expect |
|---|---|---|
| A professional account; an app serving accounts it does not own needs Meta App Review and Business Verification (publishing docs) | 100 API-published posts per account in a 24-hour moving period; media must be reachable on a public server | |
| TikTok | The Content Posting API, the video.publish scope, and an audit before public reach (get started) | Unaudited clients post to private viewing only; unaudited clients can let at most 5 users post in a 24-hour window |
| YouTube | An authorized videos.insert call through the YouTube Data API (videos.insert) | One unit from the Video Uploads quota bucket per upload; files up to 256GB |
| The Posts API with w_member_social for a person or w_organization_social plus a company page role (Posts API) | Organization posting is restricted to permitted page roles | |
| X | An app and credentials from the developer console; the API uses pay-per-usage pricing (API overview) | Your plan and the endpoint's rate limits decide throughput |
These rules also explain why a connector may schedule a post for one network and refuse another. The connector's tools are built around the platform's accepted format and required fields. A TikTok post carries privacy and interaction declarations; an Instagram post needs a professional account; a YouTube upload spends quota. Ask the connector to list its tools when a format matters, and test the exact format you plan to use.
Check what the workflow cannot do yet
The fastest way to lose trust is to describe a connector as a complete social manager. Name the limits before the first run.
- Claude still cannot publish without a tool. If the connector is removed, the account connection lapses, or the plan ends, the posting path stops.
- A connector publishes the formats its tools expose. Scheduling may be covered while comment replies, DMs or analytics are not, and the gap differs by service and by platform.
- Approval is not instant. Meta App Review, TikTok's audit and a new developer app's setup take time, and TikTok keeps unaudited posts private until its audit passes.
- Media has to be fetchable. Instagram's publishing guide expects media on a publicly accessible server, so a file sitting only on your desktop is not enough for an API publish.
- Account and time-zone mistakes are real. Confirm the workspace, the destination account and an explicit time zone such as America/New_York before scheduling, especially when one person manages several brands.
- No universal daily cap exists. Each platform sets its own limit, so a schedule that fits Instagram may still hit a TikTok or YouTube ceiling.
Read the right column before the price comparison. A connector can schedule and list accounts, but Claude still needs a tool to publish, platform approval is not instant, and only the formats a connector exposes will post. Original diagram, drawn from the limits list above.
Choose between the $29 and $199 boundaries
Superdirector sells two different jobs, and the boundary is easier to hold once you say it plainly. The $29 Starter plan is described as all you need in Claude or ChatGPT to find and remake viral ideas. It is the research and drafting layer. If you connect Claude, Codex or Claude Code to Superdirector, the product reads public Reels, TikToks and profiles from a link and cannot post.
The $199 Growth plan is the operated layer. It makes posts, carousels and video scripts and fills the month. On Growth, once posting is turned on for an account, its eligible Instagram carousels and single X text posts publish by themselves. Turning it on shows one warning that names the account, the public effect and the cost, and after that there is no separate approval for each post; you can turn it off at any time. That is account-level standing permission, not a per-post review queue.
So the choice is not which plan is better. It is whether you want to keep working inside Claude and use a connector for the platforms you name, or whether you want an account whose Instagram and X output runs on its own. Read the live pricing and how it works pages before you choose, because plan terms and supported destinations can change.
Run a first-post checklist
One controlled first post teaches more than a week of setup reading. Use this order.
- Write the post in Claude with the account's real voice and an approved asset. Do not let the connector invent a claim, price or testimonial.
- Ask the connector to list the accounts and read back the exact destination name. A wrong-account post is an expensive mistake.
- Schedule the post for a time you can watch, with the time zone written out. Check the asset, caption, hashtags and any platform-specific setting in the scheduled result.
- Confirm that a successful run reports the account, asset and post status, and that a failed run reports an error; silence is not proof it worked.
- After the first post is live, check the platform's own view. A connector's success message is not the same proof as the published post on the account.
- Widen the schedule only after one successful and one failed run have both been observed.
That discipline is what makes the difference between a demo and an account you can leave alone. Claude can carry the writing. The connector or operated account carries the publish. The platform still carries the rules.