How-To Guide
How do you automate Instagram with Claude?
Connect Claude to Instagram once, then let a connector publish, schedule and report on the loop you review, inside the account, format and rate rules it sets.
By the Superdirector editorial team. Meta's publishing documentation, Anthropic's connector documentation and the competitor guides named in this article were read November 14, 2026.
At a glance
How do you automate Instagram with Claude?
Claude itself cannot publish to Instagram, so automation is always two layers: Claude as the control layer that reads sources, drafts captions and reads results, and an MCP connector as the publisher that touches Instagram. Connect once, prove one post end to end with your approval on the first runs, then let the connector's scheduling carry the cadence. Meta's rules underneath, professional accounts, public-URL media, 24-hour containers and the posted rate caps, bind every automated path.
- The connector decides what automation is possible: its tool list is what you are really buying, from publish-only servers to ones that also carry comments, DM rules and reporting.
- Meta's own pages set the floor: professional accounts only, media at a public address, containers that expire after 24 hours unpublished, and 24-hour posting caps stated as both 100 and 50 on different official pages.
- Keep reads free, keep publications behind approval until the loop is proven, and require a visible result on every run, because silence is not proof that anything posted.
Directory and custom connectors share one runtime, so the choice is review and discovery, not capability. Original diagram based on Anthropic's connector documentation read November 14, 2026.
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.
What automation can and cannot run on Instagram through Claude
Claude cannot reach Instagram by itself. Every honest guide on this topic starts there, because the automation question only makes sense once the two layers are named. Claude is the control layer: it reads a source, drafts a caption, picks the media and timing, and reads back results. The connector is the performer: it holds the Instagram connection, uploads media, calls the publishing API and carries scheduling and reporting. One competitor guide puts the same split in one line: the agent makes the posts while a scheduler only queues finished ones.
Four jobs are worth automating, and a connector buys you some subset of them. First, preparation and publishing: reading your source, drafting the caption, and submitting the post through the API after you approve. Second, comments: reading and replying, where the connector exposes those tools. Third, standing DM rules: keyword replies that keep running after the conversation ends, within Meta's messaging limits. Fourth, reporting: pulling post performance back into the same conversation so the next brief starts from evidence. Most connectors cover one or two of these; the tool list is what you are really buying.
- What can run hands-off after setup: listing accounts, reading comments and stats, listing scheduled posts, and reading run logs. Nothing public changes in any of those.
- What should wait for you: publishing, commenting, sending a DM, taking a DM rule live, and anything that deletes a post, schedule or rule.
- What never runs: DM outreach to people who never contacted you, because Meta only permits replies to people who commented or messaged first.
Two limits belong in the same breath. Claude does not make the pictures: on the direct path the connector uploads what you give it, and some connectors bring generation on their own side, asked for by name. And automation is not a growth promise. One Claude Code practitioner says it plainly: automation makes the process repeatable, but it cannot promise followers, reach, or engagement. The rest of this guide shows how to build the repeatable part honestly.
Choose how Claude reaches Instagram
Claude connects to outside services through MCP servers, and Anthropic supports two ways to add one. A directory connector is listed after Anthropic's review, so it is discoverable in the connector browser and can even be suggested in chat. A custom connector is one you add by pasting the server URL, and custom connectors are never suggested in chat. Both run on the same runtime, so the choice is about who reviewed the server and how you find it, not about capability.
There is no official Meta posting server to point at. A November 2026 repo note about the current MCP landscape puts it in one line: Meta's official MCP servers cover ads, developer tools and WhatsApp Business, not posting. So Instagram automation through Claude always rides on a connector someone else built and hosts, or on an Instagram app you build and review yourself through the Meta developer flow. The Meta-app route costs weeks and carries ongoing token and hosting work; the hosted-connector route costs an authorization and the connector's own terms.
| Route | What it buys | What it costs you |
|---|---|---|
| Hosted publishing connector, added from the directory or by URL | Publishing, scheduling and often reporting through one authorization; no developer app of your own | The connector's tool set and terms decide everything; Meta API access lives with them |
| Your own Meta developer app and Graph API workflow | Full control of every call and token | App review, permissions, media hosting and maintenance are yours |
| Read-only analytics connector | Safe reads for measurement and reporting | No publishing at all; pairing it with a publisher is on you |
Before connecting anything, check four things on the connector's own documentation: which formats it publishes (images, carousels, Reels, Stories), whether it schedules or only publishes now, whether comments and DM rules are exposed at all, and whether results can be read back into the conversation. A connector that cannot publish will make every later step a dead end, and one that publishes but cannot schedule turns your cadence into a manual ritual.
Anthropic allows custom connectors on Free, Pro, Max, Ultra, Team and Enterprise plans, with Free limited to one custom connector. One slot is enough for a hosted Instagram publisher, so plan tier is not the blocker. On Team and Enterprise, an owner adds the connector for the organization before individuals can enable it.
Connect once and confirm the right account
This section happens once; everything after it repeats. In Claude, open Customize and Connectors, then add the connector from the directory or paste the server URL as a custom connector. Authorization runs on the service's own screens through OAuth, which grants access without Claude ever seeing your actual password. Approve only the permissions the workflow needs; a connector that only schedules existing media does not need generation tools enabled.
Connect the Instagram account itself inside the connector's own app, not inside Claude. The approval page connects whichever account the browser you approve in is signed into, so log into the intended Instagram account first. If the tool can publish to other networks too, one connection usually binds one account per platform, and agencies need the right workspace selected before the account is bound.
Then ask Claude to read the connection back before any publishing prompt. A prompt like "list the Instagram accounts available through this connector and return only the account name and ID, publish nothing" confirms the right brand is bound and gives you an exact account name to paste into later prompts. Connector guides that publish for a living make this the first instruction they teach, and the reason is simple: a good post on the wrong profile is still a bad post.
Write the identifiers down while you are here: the workspace or account ID, the IANA time zone you will schedule in, and the folder or library where approved media lives. Tomorrow 9 AM means different things when your account, workspace and current location sit in different regions, and every recurring setup later depends on these three strings being fixed.
Automate one post end to end, with the formats checked
Start with a source, not a blank prompt. The strongest practitioner workflow in this family gives Claude one named document and requires every factual claim to come from it, with the draft stopping at review files before anything publishes. In a chat-connector workflow the same discipline is one sentence: name the account by ID, give the media location, and say "prepare, show me the exact post, and publish nothing". The draft stage earns attention; the publish call spends it.
The loop itself is six stations: a source, a draft you can read, a preview that shows the exact account, media and caption, your yes, the publish call, and a verification step that confirms the post went live with its URL. Ask for caption options before asking for a publish request, so creative exploration happens without approval requests; connectors read the prepared post back before sending, and the best ones refuse to send if anything changed after you saw the preview.
| Format | What Meta's API documents | What connectors add |
|---|---|---|
| Single image | JPEG only, media at a public address, alt_text available on image posts, filters and shopping tags unsupported | Connectors document a 2,200-character caption limit and some accept a Drive share link |
| Carousel | Up to 20 images or videos in one carousel container, cropped to the first image's aspect ratio, counts as one post | Most hosted connectors cap carousels at 2 to 10 items and treat order as the payload |
| Reel | A video container with media_type REELS publishes as a reel; public video URL required | Cover images and feed-sharing flags are connector features; some accept 3 seconds to 15 minutes |
| Story | A STORIES media type exists in Meta's publishing documentation | Support varies: one connector limits API Stories to Business accounts with no caption field, another lists Stories as not supported |
Check the format rules before the first automated run, not after it fails. Meta's publishing API only accepts JPEG images, which surprises no one until a first run uploads a PNG. Carousels crop every slide to the first image's shape, so a 9:16 cover inside mixed-orientation slides reshapes the whole post. Story publishing is where connector surfaces diverge most, so if Stories are part of the cadence, verify the connector supports Business-account Story publishing and that the text carries inside the creative itself.
Six stations from source to verified post, with a rejection path from verification back to draft. Original diagram of the one-post loop, based on the connector workflows read November 14, 2026.
Turn the tested post into a schedule that repeats
One proven post is the gate. Connector guides that run this as a business all say the same thing: do not automate an unproven process, because automation repeats your process, and an uncertain source, style or caption pattern gets repeated faster. Spend the first week on manual runs of the loop above, then let the schedule take over the parts that are actually routine.
Three shapes of repetition work, and they combine. The batched session: sit down once a week, ask Claude for several post ideas against one source each, take or choose the media, and schedule them all in one sitting; the rest of your week stays free. The queue: connectors that publish into your weekly posting slots, so a finished draft lands in the next open slot instead of a hand-picked time. The cloud task: a recurring scheduled task that drafts on a cadence from a shared or watched folder, handing you the drafts for review.
Where the state lives decides what runs while you sleep. Connector-based tasks and files stored in your Claude account can run while your computer is off; a task that reads a folder on your desktop needs the desktop app open. Scheduled posts sit in the connector's queue and go out at their times whether or not your laptop is on, which is exactly why the queue belongs to the connector and not to a chat window.
Start the recurring habit at one reviewed post per day rather than three across platforms, because a slower cadence is easier to diagnose when something breaks. Require a confirmation after every run, successful or failed: what published, on which account, with what media and caption, plus the post URL when the API returns one. Silence is not proof that the automation worked, and an expired connection can quietly break days of scheduled content before anyone notices.
Set the approval rules before anything goes public
Decide the permission split deliberately, because a scheduled post and a live DM rule go out under your name. The reading actions run freely: list my accounts, read comments, read stats, list scheduled posts, read run logs. The public actions wait for approval: publishing, commenting, sending a DM, taking a DM rule live, and anything that deletes. That split, read actions free and public actions gated, is the one practitioners agree on.
Claude's own settings carry this. The permission setting in the message box decides whether Claude asks before each tool call; practitioners describe its paid-plan default as auto, and switching it to manual makes every publishing call wait for the person. Anthropic's formal guidance matches: only click Allow always for a server and tool you trust to run unsupervised. Research mode deserves its own warning, because Claude can invoke connector tools there without asking again, so Anthropic advises disabling write-capable tools before running it.
The approval contract is about bytes, not vibes: the post that ships should be the exact preview you saw. Connectors differ in how hard they enforce it. One shows a preview with the exact text per platform and refuses to publish when anything changed since you looked, sending a new preview to ask again. Another reads the exact post back, platform, media and caption, and publishes only after your confirm. Both are the same promise: no silent substitutions between your yes and the API call.
Scheduled preparation is not unattended publishing. A scheduled workflow that still waits for a review at execution time is safe by default; a queue configured to publish without a chat-side check is a different decision, and it belongs to people who have already reviewed the loop for weeks. When that decision is made, modern setups grant it to the account rather than clicking it per post: standing posting permission lives at the account level, and the operator's review moves to receipts and run logs instead of a checkbox in every thread.
Revoke cleanly too. Disconnecting the connector in Claude's settings or in the service's security settings takes the access back at any time, which makes the approval split reversible. If a run looks wrong mid-week, the weekly run-log review is the moment to find it: ask which rules fired, which failed, and read the errors before changing anything.
Read actions run freely while publishing and DMs wait for approval, and proven queues can hold permission at the account level. Original diagram of the permission split, based on Anthropic's connector guidance read November 14, 2026.
Fix the failures that stop the loop
The failures repeat across every connector, because underneath one API sets the rules. The table below pairs each common break with its cause and the fix that actually moves the run.
| Failure | Cause | Fix |
|---|---|---|
| Publish denied outright | A personal Instagram account; the API publishes professional accounts only | Switch to Business or Creator in the Instagram app; it is free and keeps your content |
| Media download error | Instagram's servers fetch the media at publish time, so private links and local paths fail | Host the file at a public address or upload it into the connector's storage |
| Image rejected | The publishing API accepts JPEG only | Convert to JPEG before upload; alt_text applies to image posts, not video surfaces |
| Container expired | A container left unpublished passes its 24-hour life and returns EXPIRED | Publish soon after the container is created; retry with a fresh container if the connector exposes it |
| Post live, caption missing | A partial success: the media published while the caption did not attach | Treat the returned config_issue as a reconcile signal, then fix the caption manually or republish |
| Post on the wrong account | The approval bound whichever account the browser session had signed into | Disconnect, sign into the intended account, reconnect, and relist connected accounts before the next post |
| Posts at the wrong hour | A timezone was left implicit, so account, workspace and device regions disagreed | State an IANA time zone such as America/New_York in every scheduling prompt |
| Nothing published, no error | A silent failure, often an expired connection or a disabled permission | Require success and failure confirmations on every run and read the run log weekly |
| Posting stalls late in the month | The 24-hour API caps: 100 posts in the publishing guide, 50 in the endpoint reference, carousels as one post | Check the content_publishing_limit endpoint, then slow the queue; a connector's own caps can be tighter |
One habit prevents most repeats: read the error before changing the workflow. Connector run logs name the rule that fired and the endpoint that refused, and a fix aimed at the wrong layer, editing prompts when the account type was the problem, wastes the review trust you built in the previous section.
Keep the loop yourself or hand the account over
By this point the automation is real: a connector bound to the right account, formats checked, one post proven end to end, approvals set. The last decision is about time, not technology. Wiring and running this loop yourself is a hands-on task with a standing review job attached; every week you are the editor who reads the drafts, checks the run log and answers for what published. Practitioners who run this at scale still review every piece before it goes out, because automation removes the busywork and keeps the judgment.
If you keep the loop, Superdirector's Starter plan is $29 a month for MCP access and hands-on asset creation from Claude or ChatGPT: direct the tasks, approve the posts, and glue the cadence together with the scheduling tools your connector provides. That plan deliberately carries no native repeated channel workflows, so the recurring habits in this article stay yours to run.
If the posting should happen whether or not you are at the desk, our Growth plan is $199 a month for one customizable AI-run account. It watches your niche, prepares carousels and X posts in your brand's direction, and publishes eligible Instagram carousels and single link-free X text posts under standing posting permission granted at the account level, so the cadence does not wait on a per-post click. In both cases the honest scope stands: the service operates the account and carries most content creation and regular posting; it does not manufacture outcomes. Automation makes the process repeatable, as the practitioner above put it, but it cannot promise followers, reach, or engagement, and whoever owns the account keeps owning what it should sound like.