How-To Guide
How do you post to Instagram with Claude?
Connect Claude to Instagram through an MCP connector, publish with an approval you control, check the live post, and keep Meta's format and rate rules.
By the Superdirector editorial team.
At a glance
How do you post to Instagram with Claude?
Claude has no Instagram publishing of its own. The workable path is to add an MCP connector that holds the Instagram connection, authorize your professional account with that connector, then ask Claude to write the caption, show you what it will publish, and publish after you approve. Meta's API rules apply underneath: professional accounts only, media at a public address, and a per-account 24-hour posting cap.
- Claude needs a connector; it reaches Instagram through one and never through your password.
- A Business or Creator account linked to the connector is required, with media at a public address.
- Prefer a connector that shows a preview and waits for your yes, then check the post in Instagram.
The three routes differ mainly in who holds Meta's publishing approval. Original diagram, drawn from Meta's content publishing guide and the connector guides cited in this article.
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 needs to be true before Claude can publish to Instagram
Claude cannot reach Instagram on its own. The connection exists somewhere else, and wherever you put it, three things have to be true before a single post can publish.
First, the account is professional. Meta's Content Publishing guide covers posting to Instagram professional accounts, and the connector guides repeat the split: Business accounts can publish images, carousels, Reels and Stories; Creator accounts cover everything except Story publishing through the API; personal accounts are not available through the publishing API at all.
Second, the media sits at a public address. The guide is blunt about this: media must be hosted on a publicly accessible server at the time of the attempt, because Instagram's servers download it during publishing. JPEG is the only image format the API supports. A file on your laptop, or a private link, ends the request with an error.
Third, the connection carries a real authorization. You will sign in through Meta's screens, not by handing a password to a chat window. Anthropic's connector guide describes the flow as OAuth, which grants access to the connected application without Claude ever seeing your actual password.
With those three facts in place, the rest of this guide is mechanics. The table below keeps the two official cap numbers side by side so you can quote either one with its source later.
| Rule | What Meta's own pages say | Where it is written |
|---|---|---|
| Account type | Professional accounts publish; personal accounts do not | Content Publishing guide |
| Media location | Public server, downloaded at attempt time | Content Publishing guide |
| Image format | JPEG only | Content Publishing guide |
| Posting cap | 100 per 24-hour moving period in the guide; 50 in the endpoint reference | Both official pages |
| Container life | An unpublished container expires after 24 hours | Content Publishing guide |
Two official Meta pages state different caps in plain sight. The guide's rate-limit block says Instagram accounts are limited to 100 API-published posts within a 24-hour moving period, and the media_publish endpoint reference's Limitations section says a professional account can only publish 50 posts within a 24 hour moving period. We report both instead of picking a favorite, and any connector you use should read the limits endpoint Meta provides instead of hard-coding either number.
Choose how Claude reaches Instagram
Start with a field observation one guide measured on its own: Meta publishes no official Instagram MCP server. Its only first-party MCP server is for ads, so every Instagram connector you can add to Claude was built by another company on top of Meta's publishing API. That same guide counted 244 entries for an Instagram search inside Claude's connector directory on October 10, 2026, most of which read data and cannot publish.
From there the choice is about who holds Meta's approval. Two routes exist, and a third path exists when neither route is what you actually want.
| Route | Setup | Who holds the connection | Works for |
|---|---|---|---|
| Build your own Meta app | Days, then app review | You, as the developer | A team that wants to own every byte |
| Connect a hosted connector | Minutes | The connector's vendor | Posting from Claude today |
| Operated account at $199 a month | Plan setup | Superdirector under your direction | A channel run for you, not one prompt at a time |
Route one ends where most people hope it does not: business verification and app review gate the publish permission. Blotato's walkthrough of these two routes says its hosted path skips the Meta API, business verification, and OAuth token handling entirely, which is their declared comparison and it matches the official review gate.
Route two is what this guide walks. Inside it, one distinction from Anthropic's own documentation matters: a directory connector has been reviewed by Anthropic, while a custom connector is any server added by URL with no Anthropic review, per their own comparison page. Custom connectors are never suggested to you in chat, and an install link only fills in a form; it does not bypass your own review of what you are connecting.
Plan access is generous: custom connectors work on Free, Pro, Max, Ultra, Team and Enterprise plans, with Free limited to one custom connector. The connection itself is brokered by Anthropic's cloud, which is why the server must be reachable on public HTTPS port 443 even when you chat from your laptop.
Connect the connector in Claude and authorize Instagram
The connector lands in Claude one of two ways, and the vendor's own page should settle which. If the service is listed in Claude's connector directory, open Customize, choose Connectors, find the card, and click Connect; Anthropic's custom connector guide gives the exact screens. If it is not, use Add custom connector and paste the server URL the vendor documents.
On Claude Code the same step is one command. Postlefy's guide, for example, names its server at postlefy.com/api/mcp, and the general pattern looks like this, with the vendor's URL in the last position:
claude mcp add --transport http <connector-name> <server-url>After the connector is registered, authorize the Instagram account with the connector's vendor, not with Claude. The vendor carries the Meta OAuth flow and holds the resulting connection. Two checks keep mistakes cheap: complete Meta's authorization on the account you meant to use, and list the accounts Claude can see before trusting it.
- Add the connector to Claude, from the directory or by URL, as the vendor documents.
- Connect Instagram inside the vendor's settings through Meta's authorization screens.
- Ask Claude to list the accounts it can see through the connector, and match the name and account ID.
- Approve only the permissions your workflow needs; a connector can read, publish, or both.
Developer-grade toolkits follow the same shape at more length. Composio's Claude Code page walks generating a scoped server URL, adding it with one command, restarting Claude Code so the tools register, and authenticating on first use. The restart step is the one people skip, because Claude Code only registers connector tools at startup.
Genviral's version of this step earns a special mention for honesty: it tells you not to approve permissions blindly, because adding a connector is not the same as granting every tool inside it. If you only intend to schedule existing media, you do not need the generation tools.
Ask Claude to write the post, approve it, and confirm it went live
One post, end to end, teaches the workflow better than any comparison table. Start with a single image you are allowed to publish, a caption you can verify, and the account you listed in the last section.
Markifact's walkthrough is the template for the ask. Paste a prompt in the shape below: name the account and its ID, give the public media URL, state the caption, and close with an instruction to wait for approval before publishing. Their example ends with the line: do not publish until I approve the final request. Postlefy's plain-words version of the same moment is simpler still: write the post, check the preview, and say yes.
Use the Instagram account <NAME> (<ACCOUNT ID>).
Prepare a single-image post from this media URL: <PUBLIC IMAGE URL>
Caption: <CAPTION>
Show me the account, post type, media, and the full caption.
Do not publish until I approve the final request.The approval screen is where the connector earns trust. Underneath, Markifact explains what their publish does: it creates the media container, waits for Instagram to finish processing, then publishes, and a successful response includes the media ID and permalink. Meta's own guide lets you poll a container's status, naming states from IN_PROGRESS to PUBLISHED. Approval and confirmation are two events, not one.
Scheduled posts follow the vendor, not Claude. Markifact states plainly in their limits section that their operation has no native publish_at field, so scheduling happens in a workflow that runs later. Postlefy takes a time instead: say schedule it for Friday at 9am, and its preview still applies. Whichever you pick, include the time zone in words, because a chat window on one coast should never guess a posting time for an account on another.
The last step happens outside the chat. Open Instagram, find the post on the intended account, and check the caption, the crop, and the format. A tool response saying published is a claim; the account is the fact.
Approval and confirmation are two separate moments in one publish. Original diagram, following the connector walkthroughs and Meta's publishing guide cited above.
Publish each Instagram format within Meta's rules
Every format posts through the same connector, but the rules differ enough to deserve their own card. The official numbers come from Meta's guide; the narrower ones come from the connectors and are theirs.
| Format | Meta's rule | Connector-side notes |
|---|---|---|
| Single image | JPEG, public URL | Alt text is an API field since March 24, 2025 |
| Carousel | Up to 20 items; counts as one post | Blotato and Markifact declare 2 to 10 items |
| Reel | Video container, media_type REELS | Vendors quote 3 seconds to 15 minutes, ratio 4:5 to 1.91:1 |
| Story | Business accounts only through the API | Markifact accepts one item and no caption field |
Three quirks cause most failed attempts. Carousels are cropped from the first image, so lead with the frame that survives a square crop. Hashtags have their place: Blotato's setup holds them in a first comment field rather than the caption for the posts it publishes, while Markifact says their operation cannot post a first comment at all, so its users paste one by hand. And a feed video is published as a Reel; if you mean a Story, say Story.
Two more official details save arguments later. Meta accepts an is_ai_generated flag on a media container to disclose that the media is AI-made, and trial Reels, which Meta documents as reels shared only to non-followers, carry their own graduation settings. If a connector does not expose a field you read about here, ask the vendor before assuming the feature exists.
Meta's own publishing guide carries the full format reference, and every connector page linked in this section declares its own narrower support; the mismatch between them is normal and worth one question before you commit a calendar to the connector.
Meta's own rules, format by format; connector limits run narrower in the table above. Original diagram, from Meta's Content Publishing guide.
Fix the failures that show up first and read them safely
The first broken attempt is usually one of a short list. A personal account, and Meta's API gives nothing to publish to, so convert to Business or Creator first. Media behind a private link, and the download fails before anything else happens. A container that waited too long: Meta's guide says an unpublished container expires after 24 hours, which is a real deadline, not a warning.
The rest are workflow mistakes, not platform ones. A connector whose upload permission stayed off, which Genviral's guide calls the easy one to miss. A scheduled post prepared for the wrong brand, which is why the account list check exists. A time zone nobody wrote down. A caption that sounded right in the chat and wrong on the grid.
- Wrong account: list accounts again and match name and ID before publishing.
- Failed media: check the URL is public, the file is JPEG, and the size fits the connector's stated limits.
- Expired container: prepare and publish closer together; the 24-hour expiry is Meta's, not the vendor's.
- Silent failure: require a confirmation for success and for failure, so silence never reads as success.
- Missing feature: the connector's page, not the chat, is the authority on what it supports.
Genviral's guide carries the habit worth keeping: run the first post scheduled, not immediate, review what the connector actually made, and keep confirmations on until the workflow has survived several checks. One reviewed post per day diagnoses faster than three unwatched posts across platforms.
One caution comes from Anthropic rather than the vendors: connectors can act on your behalf, and Anthropic's guide warns that malicious servers may carry hidden instructions while noting Claude has built-in protections that attempt to block them. The practical reading is boring and correct. Connect servers you trust, review what permissions they request, and deny the ones the job does not need.
Keep posting yourself or hand the account to an operated one
Everything above is a job you can do in an afternoon: wire the connector, run a few posts, and keep the approvals in your own hands. It suits a founder whose posting is a handful of pieces a week and who wants the captions written where they already work.
The different job is running the channel. Superdirector's Growth plan is $199 a month for one customizable AI-run account: it watches your niche, finds formats gaining traction, prepares carousels and X posts in your brand, and publishes eligible Instagram carousels and single link-free X text posts to a connected account under its standing posting permission. Facebook, LinkedIn or Pinterest posts still need a scheduler, and AI video and full autopilot are coming soon; they are not live today.
If you keep doing the hands-on work yourself, Starter at $29 a month is the entry you use from Claude or ChatGPT for MCP access and asset creation, with limited video and script exploration and no native repeated channel workflows. It is the plan that matches this guide's job. Growth is the plan that replaces the job, and the honest boundary between them is the part worth writing down before you choose.
One more comparison from the vendor field, in its own words: Blotato's scheduler round-up found that five of eight tools ship an MCP server that schedules Instagram posts, and it records vendor claims as exactly that, documentation, not test results. Read it the same way: a connector's feature list is a promise to check, not a result to trust.
For the neighboring questions, our guides on using ChatGPT for social media, on which AI tools actually publish, and on how often to post on Instagram cover the decisions on either side of this one.