Can Claude Post to TikTok and Instagram? What Actually Works in 2026

Short answer: yes, Claude can publish to TikTok and Instagram — but not by itself, not on every platform, and not from every account. Claude has no social media access of its own. What it has is the ability to call an external tool, through the Model Context Protocol (MCP). The real question is not “can Claude post”, it’s “which platforms will actually accept a post from a programmatic tool, and under what conditions”. That second question has a much more interesting answer, and almost nobody writes it down honestly.

I’m Giovanni Fu Lin. I built SchedulePost, which ships an MCP server and a ChatGPT app, so I have an obvious stake in this topic. I’m going to use my own tool as the worked example because it’s the one whose internals I can describe precisely. Where the wall is a platform wall rather than a tool wall, I’ll say so — and most of the walls below are platform walls that every competing tool hits in exactly the same place.

What “Claude posts to Instagram” actually means

There’s a misconception worth clearing up first, because it changes what you should search for.

Claude is a language model running in Anthropic’s infrastructure. It cannot open Instagram, it holds no session cookie for your account, and it has no credentials. When someone says “Claude posted my Reel”, what actually happened is a four-step chain:

1. You connected an MCP server to Claude. That server is a small web service run by whoever built the publishing tool. Mine lives at https://schedulepost.fulinlabs.com/api/mcp.
2. You signed in to that server once with OAuth. The server now holds an authorized connection to your Instagram, TikTok, and YouTube accounts — the same kind of connection a scheduling dashboard holds.
3. You typed a sentence. Claude read the list of tools the server exposes, picked one, and called it with the right arguments.
4. The server called Instagram’s Content Publishing API. Instagram published the post.

Claude is step 3. Everything that can go wrong lives in steps 2 and 4. This matters, because it means the answer to “can Claude post to X” is never about Claude’s capability — it’s about whether platform X lets a third-party server publish on your behalf, and what it demands in exchange.

The per-platform reality table

This is the table I wanted to find when I started building publishing integrations, and couldn’t. Every vendor page says “20+ platforms” and stops there. Here is what each platform actually requires, based on the integrations I’ve written and shipped.

Platform	Can an agent publish it?	What the platform demands
TikTok	Public posts: only from an audited app. Otherwise drafts or self-only.	OAuth scopes video.upload and video.publish. Before TikTok audits your app, the API will only accept private or draft posts. TikTok also returns which privacy levels your account allows, per creator — the app has to check before it posts.
Instagram	Yes, from a professional or creator account.	Content Publishing API access, an account linked to a Facebook Page, and Page Publishing Authorization completed. Personal accounts cannot be published to programmatically at all. Media is uploaded to a container that has to finish processing before publish — a slow video means a slow post, not a failed one.
YouTube	Yes, cleanly.	A resumable upload and OAuth. This is the most straightforward integration of the six. Per-day upload quota is the practical limit.
Facebook Pages	Yes, cleanly.	A Page access token. Personal profiles are not the same thing and are far more restricted.
Threads	Yes.	Threads API access via the same Meta app chain as Instagram.
X	Yes.	API access under X’s current paid tiers. Cost, not capability, is the constraint here.
Telegram	Yes, trivially.	A bot token. The least restrictive of the set by a wide margin.

Two lines in that table are where nearly every “AI posts for you” claim quietly breaks.

TikTok is the hard one. TikTok’s Content Posting API distinguishes between uploading to the user’s drafts and posting directly to their feed. Direct posting needs the video.publish scope, and TikTok only grants that to apps that have gone through its audit. Until then, a tool can put a video in your TikTok inbox, and you still open the app and tap post. If a tool promises “Claude posts to TikTok” without mentioning audit status, the honest follow-up question is: does it publish publicly, or does it drop a draft? Those are very different products.

Instagram is the one that surprises people. The blocker is the account type, not the tool. If your Instagram is a personal account, no scheduler on earth can auto-publish to it — not SchedulePost, not Buffer, not Later, not an MCP server. Instagram simply doesn’t expose that capability for personal accounts. I wrote about this failure mode in more detail in auto-publish vs notification schedulers, because it’s the single most common reason a scheduled Reel doesn’t go live.

What the tools actually look like

If you connect an MCP publishing server, Claude sees a list of named tools. Reading that list is the fastest way to judge a tool honestly, because the tool names are a specification you can’t market your way around. SchedulePost’s server exposes nine:

Tool	What it does
list_accounts	Read your connected accounts and their platforms
list_account_groups	Read your saved groups of accounts
list_scheduled_posts	Read what’s queued and what’s already published
list_post_analytics	Read per-post analytics for a connected account
upload_video	Put media into durable storage, ready to publish
publish_now	Publish immediately to the selected accounts
schedule_post	Publish at an exact time you specify
queue_post	Let the tool choose the next good slot
cancel_scheduled_post	Cancel something already queued

Five of those are read-only, four write. That split is worth looking for in any connector you approve. A server that only exposes one giant do_everything tool is telling you something about how much control you’ll have.

The reason queue_post exists separately from schedule_post is the interesting one for agent work. When you’re talking to an agent you usually don’t want to compute a timestamp — you want to say “add this to the queue” and let the tool place it at the next sensible slot. Agents are good at intent and bad at remembering your timezone. I write more about how those slots get picked in best times to post short-form video.

How to set it up

For Claude: open connector settings, add a custom connector, paste the MCP server URL (https://schedulepost.fulinlabs.com/api/mcp for mine), and complete the OAuth sign-in when prompted. Claude will then list the available tools. Connect your social accounts inside the SchedulePost dashboard first — the MCP server publishes through connections that already exist, it doesn’t create them.

For ChatGPT: the same server backs a ChatGPT app, so the flow is the app install and OAuth rather than a pasted URL. Underneath it’s the same nine tools and the same OAuth resource.

Then just write a sentence. “Upload this video and queue it for TikTok, Instagram, and YouTube.” The agent picks upload_video, then queue_post, and reports back which platforms accepted it. When one platform fails and the others succeed, the response says so per-platform rather than failing the whole batch — which is the behaviour you want, because TikTok rejecting a video shouldn’t stop YouTube from getting it.

The alternatives, fairly

I’m not the only tool in this space, and pretending otherwise would make this page useless to you. As of August 2026 these are the ones that show up when people search for AI-agent publishing:

• Postiz — open-source, and by far the most aggressive in this category. It ships an MCP server, an n8n node, a Make.com integration, an agents CLI, and dedicated integrations for several agent products. Cloud plans run $29 to $99 per month by channel count; self-hosting is free. If you want the broadest agent surface area, this is the one to look at first.
• Mixpost — self-hosted, with MCP on its paid Pro license ($299 one-time). Good fit if data ownership is the priority.
• Blotato, Upload-Post, RobinReach, Outstand — hosted tools that market MCP publishing directly. Worth testing, and worth asking each one the TikTok audit question above.
• Composio, Windsor.ai — connector layers rather than schedulers. They give an agent access to a platform, but the scheduling and queueing logic is yours to build.

Where SchedulePost differs: it’s free, it’s narrow, and it’s built for short-form video specifically rather than general social media management. If you need LinkedIn, Pinterest, Mastodon, Bluesky, or a full content calendar, one of the tools above fits better than mine does. If what you want is “one vertical video, six platforms, from an agent, for nothing”, that’s the case I built for. There’s a fuller head-to-head in SchedulePost vs Buffer and a wider survey in the best tools to schedule TikTok, Reels and Shorts.

What I’d be cautious about

Two things, and I’d rather say them here than have you find them out later.

Publish-now is a loaded gun. An agent that misreads “draft a post about X” as “publish a post about X” has just published to your real audience, and there is no undo on a live post. My own preference — and the way I use my own tool — is to schedule or queue by default, so there’s always a cancellable window between the agent’s decision and the public post. cancel_scheduled_post exists precisely because that window is worth having.

Scoped OAuth is not the same as unlimited access, but read the scopes anyway. When you approve a connector you’re granting a third-party server ongoing publishing rights to your accounts. That’s a real grant. Approve it for tools you’d trust with your dashboard password, revoke it when you stop using them, and prefer servers that separate read tools from write tools so you can see what’s actually possible.

Where this goes next

The honest state of things in August 2026: agent publishing works, it works better than most people expect, and every remaining limit lives at the platform API rather than in the model. TikTok’s audit requirement is the biggest gate. Instagram’s professional-account requirement is the most common surprise. Everything else mostly just works.

If you want to try it, SchedulePost is free — connect your accounts, add the MCP server to Claude or install the ChatGPT app, and ask it to queue something. You can also read how the whole thing fits together on the project page.