Instagram MCP Server: Post to Instagram From Claude and ChatGPT

An Instagram MCP server is a small program that sits between an AI assistant and Instagram. The assistant, such as Claude or ChatGPT, does not talk to Instagram directly. It talks to the server through the Model Context Protocol, which the official MCP introduction describes as an open source standard for connecting AI applications to outside systems. The server then calls Instagram on your behalf: it uploads a picture, builds a carousel, publishes a Reel or reads how a post did.

So when people search for an Instagram MCP server, they usually want one of four things. They want to post to Instagram from a chat window without opening the app. They want the assistant to make the post, not only send it. They want to read comments, messages or numbers. Or they are developers who want a server on GitHub they can run and change. Each of those needs a different kind of server, and some of them carry real risk to your account.

This page covers the whole question for Instagram only: whether Meta runs an official server, what Instagram's publishing API lets any server do, how the open source servers on GitHub sign in, which hosted options exist, what to check before you connect one, and how to set one up in Claude and ChatGPT. Spreadcast runs an Instagram capable MCP server, and we explain how it works, but every check and every limit below applies to whichever server you pick.

If you want the reference for every tool Spreadcast's server offers across networks, read the social media MCP server page. For a ranked list of every vendor with an MCP server, see the best social media MCP servers.

No, not for posting. On October 16, 2026, the only MCP server Meta runs itself is for ads. Meta announced its ads AI connectors in open beta in its business news post on Meta ads AI connectors, dated April 29, 2026, with an update on July 16, 2026. The post describes reporting, campaign management, catalog management and signal diagnostics. It does not mention organic posts.

Meta's Ads MCP server documentation says the server is hosted by Meta at mcp.facebook.com/ads and lists tools for reporting, creating and editing ads, ad sets and campaigns, catalogs, datasets, A/B tests and activity logs. That is useful if you run Instagram ads, because an ad can show on Instagram. It is not a way to publish a regular feed post, a carousel or a Reel to your account. We found no Meta page describing an MCP server for organic Instagram publishing.

That means every Instagram MCP server you can use for posting today is built by someone other than Meta. The good ones call Meta's official Instagram API, the same one scheduling tools use, and inherit its rules. The risky ones skip the API and log in as you with your password. The difference matters more than any feature list, and the sections below show how to tell them apart.

Not on their own. Neither ChatGPT nor Claude has a built in Instagram account connection that posts for you. Both can write a caption or describe a picture in a normal chat, but publishing needs a third piece: a connector or an MCP server that holds permission from Instagram to post to your account.

In ChatGPT those pieces are called apps and plugins. OpenAI's help page on connected apps says app availability depends on the app, your ChatGPT plan, region, workspace, role, model and the interface you use, and that apps can take supported actions in a connected service. A custom MCP server is a separate route. OpenAI's article on custom MCP servers says custom MCP server connections with full MCP support, including write actions, are available for ChatGPT Business, Enterprise and Edu on the web, and its FAQ says they are web only, not mobile. So "can ChatGPT connect to Instagram" has an honest answer: yes, through an app or a custom server, and the custom server route needs one of those workspace plans.

Claude is more open here. Anthropic's guide to custom connectors lists custom connectors using remote MCP on Free, Pro, Max, Team and Enterprise, and says Free users are limited to one custom connector. So "can Claude post to Instagram" is also a yes, on any plan, once you add a server that can post and connect your Instagram account to it. The same guide warns that custom connectors reach services Anthropic has not verified, which is why the checks further down matter.

Claude Code and other developer tools can add a server from the terminal. Claude Code's MCP docs show one command for a remote server, either with a key sent as a Bearer header or with a browser sign in started from /mcp. The docs also tell you to verify you trust each server before connecting it.

Yes, Instagram has an official API for posting, and it comes in two setups. Meta's Instagram Platform overview lists content publishing, comments, insights and mentions in both: the Instagram API with Instagram Login, which needs no Facebook Page, and the Instagram API with Facebook Login, which does. Messages work directly on the Instagram Login setup and through the Messenger Platform on the Facebook one. Hashtag search and product tagging exist only on the Facebook setup.

Calling it costs nothing. The overview covers access levels, App Review, Business Verification and rate limits, and none of the Meta pages we read on October 16, 2026 lists a fee. You pay in setup work and limits instead. Most calls share a daily budget that the overview gives as 4,800 calls in 24 hours multiplied by the number of impressions the account had, and publishing has its own cap of posts per day, shown in the table below.

What the API no longer has is a door for personal accounts. Meta's developer blog post on the Instagram Basic Display API says that API stopped working on December 4, 2024, and that from then on there would be no Instagram APIs for consumer apps. Older tutorials that tell you to add the Basic Display product to your Meta app are out of date.

So a hosted Instagram MCP server that charges money is charging for the work around the API, such as hosting files, renewing tokens and passing App Review, not for Meta.

The professional account rule is the one most people hit first. Meta's Instagram Platform overview says app users must have an Instagram professional account, for a business or a creator. A server built on the API cannot publish to a personal account, however it is set up. Switching is free and takes a minute in the Instagram app. Instagram's help page on professional accounts walks through it under Settings, Account type and tools, and warns that a private personal account becomes public when you switch, with pending follow requests accepted. Read that before you switch a private account.

The second rule is about who the server is for. The same overview says an app that serves professional accounts it does not own needs Advanced Access, and that this requires Meta App Review and Business Verification. Standard Access is meant for people with a role on the app, development and testing. In practice this means a hosted service has gone through Meta's review, while a server you run from GitHub uses your own Meta developer app, which works for your own accounts.

The third rule is what the API leaves out. Filters and shopping tags are listed as unsupported in Meta's content publishing guide. Some things you can do in the Instagram app, like picking a song for a Reel, depend on how the account is connected. A server that promises everything the app can do, through the API, is promising more than Meta's own documentation does.

These limits are why some GitHub servers skip the API and log in as you. They can then reach a personal account and features the API does not offer. The next sections explain why that trade is a bad one for an account you care about.

Searching for an Instagram MCP on GitHub turns up dozens of projects, many with a handful of commits and no recent release. Some are excellent. All of them make you the operator: you install Python or Node, keep the server running while you use it, store a secret on your machine and fix it when Meta changes something.

With a Graph API server the secret is an Instagram access token. A long lived token lasts about 60 days, as the ig mcp README notes, so a server that does not renew it stops working without warning two months after setup. The token sits in a .env file or in your assistant's config. Anyone who gets that file can post to your account until the token expires or you remove the app's access in Meta's settings. Never commit it to a repository, and give it only the permissions the server needs: publishing needs the content publish permission, and messages need a separate one that has to pass App Review.

With a password based server the stakes are higher. Instagram's Terms of Use say you cannot create accounts or access or collect information in unauthorized ways, which includes "accessing or collecting information in an automated way without our express permission", whether or not you are logged in. The same section says you cannot request or collect Instagram usernames or passwords. A server that logs in as you, from a script, to send messages or read follower lists sits squarely inside what those terms describe. Instagram can restrict or disable an account for that, and there is no appeal that turns a script login into an allowed one.

There is a quieter risk too. A password gives full control of the account, not a narrow permission. If the server, a package it depends on or a prompt injection in a message it reads misbehaves, it can do anything you can do: change the email, delete posts, message followers. An API token can be limited to publishing and revoked on its own. Your password cannot.

So use GitHub servers for what they are good at: learning how the API works, testing a workflow on a throwaway professional account, or building your own tool on top. For the account that carries your brand, prefer a server that signs in through Meta's official login and never asks for your Instagram password.

Yes, and each is free in a different way. Open source servers cost nothing to download. The ig mcp project carries the MIT License and runs on your own Meta developer app, so what you spend is time and a computer that stays on while you use it.

Hosted toolkits often have a free tier. Composio's pricing page lists a Hobby plan at $0 with no card and 100,000 tool calls, of which 20,000 may run through the apps Composio manages for you, and usage pauses at the cap until the next month. You still write the code that opens a session.

Spreadcast's server is on every plan, Free included. On Free the assistant designs Instagram posts and carousels, writes captions and saves drafts for one app, and you publish them yourself. The assistant side can be free too: Claude Free allows one custom connector, which is enough for one Instagram MCP server.

After posting, direct messages are the most common reason people want an Instagram MCP server. Meta allows it through the official API, with stricter rules than publishing. Meta's guide to the Instagram messaging API works for professional accounts only and needs a separate permission to manage messages on top of the basic one.

Two rules decide what an assistant may do. A business can only message someone who wrote to it first, and it has 24 hours to answer each message. Meta allows a tag for a human agent who needs longer, so an assistant that drafts replies for a person to send fits the rules better than one that sends by itself. And an app that answers messages for accounts it does not own needs Advanced Access, with App Review and Business Verification.

That explains the split on GitHub. The ig mcp README marks its conversation and send message tools as needing Advanced Access. Password based servers skip the review by logging in as you, with the Terms of Use problem above. Spreadcast has no message tools, so for direct messages pick a toolkit that lists them or a server on your own reviewed Meta app.

Spreadcast is a remote MCP server at spreadcast.app/api/mcp, starting with https, made for people who market an app. You add that address to Claude or ChatGPT once and sign in with your Spreadcast account. There is no key to copy for those two. Claude Code and Cursor can use a key from Settings, AI Assistants, or sign in the same way.

Your Instagram account is connected to Spreadcast itself, never to the assistant. Spreadcast supports both of Meta's setups: Instagram Login, which needs no Facebook Page, and Facebook Login for an account linked to a Page. Either way you approve access on Meta's own screen, and Spreadcast never sees or stores your Instagram password. When a post is due and the Instagram token is close to running out, Spreadcast renews it first, and an account connected through Facebook holds a Page token that does not expire.

When you connect an assistant, a consent screen asks what it may do: Make Drafts, or Make and Publish. Make Drafts is the default. With it the assistant can design posts, write captions and put drafts on your calendar, and nothing reaches Instagram until you approve it in Spreadcast. Scheduling and publishing also need the Pro plan. On Free the assistant saves drafts and you publish them yourself.

When a post does go out, Spreadcast handles the parts of the API that trip up simpler servers. A post with several pictures is published as a real Instagram carousel, not as separate posts: each slide is made as a carousel item, checked until Instagram has processed it, and then joined into one carousel with one caption. A video is published as a Reel that also shows in the feed, and a cover picture you chose is sent with it. Spreadcast waits for Instagram to finish processing, and if a long video is still processing it carries on in the next run with the same upload instead of posting twice. A picture outside the 4:5 to 1.91:1 range is padded with a blurred copy of itself and saved as JPEG rather than cropped, so nothing is cut off. After publishing, Spreadcast saves the link to the live post.

Spreadcast does not post Instagram Stories, and it does not set collaborators, alt text, location or shopping tags. If you need those, add them in the Instagram app after the post is live, or pick a server that lists them.

There is no single Instagram MCP server URL, because Meta does not run one for posting. Each server has its own address. Spreadcast's is spreadcast.app/api/mcp with https in front, and the same address covers Instagram and every other network you connect. Meta's server for ads sits at mcp.facebook.com/ads, per Meta's Ads MCP documentation.

A server from GitHub has no public address at all. Your assistant starts it as a program on your computer, so you copy a command and a folder path into its config instead of a URL. If a site offers a free Instagram MCP URL with no sign in behind it, ask who holds your Instagram permission once you paste it.

Yes, in two ways, and both need publishing turned on deliberately. The first is scheduling. Claude saves the post with a time, and Spreadcast publishes it then, whether or not the chat or your computer is open. That takes a Make and Publish connection and Spreadcast Pro. With Make Drafts, Claude can still fill the week, and every post waits for your approval.

The second is a Claude task that runs by itself. Anthropic's article on Cowork scheduled tasks says tasks can run hourly, daily, weekly or on weekdays on paid Claude plans, keep running while your computer sleeps or the desktop app is closed, and use the connectors you set up in Cowork. A weekly task that asks Spreadcast for new App Store moments and designs a post for each one becomes a steady Instagram pipeline.

Keep that task on drafts. A schedule nobody watches is how a wrong version number or an old screenshot reaches your profile. Let the task fill the week, then approve it in a few minutes. The wider Claude setup is in Claude for social media.

Most failed posts from an assistant come from a handful of API rules, all of them in Meta's content publishing guide. Knowing them helps you read an error in the chat, whichever server you use.

The picture is not a JPEG. Instagram's API takes JPEG and nothing else, so a PNG screenshot or a WebP from a design tool is refused. A good server converts it first. If yours does not, export JPEG.

The picture is the wrong shape. A feed picture must be between 4:5 and 1.91:1. A phone screenshot at full height is far taller than 4:5 and fails. Put it inside a 4:5 design, which is what Spreadcast's iPhone frame does, or crop it.

The link is not public. Meta fetches the file from the address the server gives it, at the moment it publishes. A link from a private folder, a signed link that expired or a file on your own computer fails. The server has to host the file somewhere public.

The media is not ready. Instagram processes each upload before it can be published, and a server that publishes too early gets an error saying the media is not available. Videos can take minutes. The server has to wait and check again rather than give up.

The token expired. An Instagram token that is never renewed stops working after about 60 days, and every post fails with an access error until you connect again. Hosted servers renew it. With a local server, that job is yours.

The Page needs Publishing Authorization. For an account connected through a Facebook Page, Meta's guide says a Page that requires Page Publishing Authorization cannot be published to until that is complete, and recommends finishing it early. If posts fail with a permission error and everything else looks right, check this in Meta's settings.

Spreadcast is built for app makers: the posts start from your app's brand kit, its screenshots and its App Store listing. If that is not you, or you need something it does not do, another option may fit better.

If you want an assistant to read and answer Instagram comments and direct messages, Spreadcast has no tools for that. Composio's Instagram toolkit lists comment and message tools, and is a good fit if you are a developer building your own agent. If you run Instagram ads and want an assistant to report on them or edit campaigns, Meta's own Ads MCP server is the official route.

If you are a developer and want full control of the code, a Graph API server from GitHub such as the ig mcp project shows every call and runs on your own Meta app. Expect to handle tokens, App Review for some permissions and Meta's version changes yourself.

If you need Instagram Stories through MCP, Spreadcast does not make them. Check the tool list of any scheduler you consider, and compare the field in the best social media MCP servers.

Pick Spreadcast when you want the post made, not only sent: a carousel about a feature, a post for a new version or a thank you for a rating, designed in your app's look, with a real screenshot, saved as a draft you approve. For the wider plan on Instagram, read how to promote an app on Instagram. If you would rather make Instagram posts without any assistant, the Instagram post generator does it inside Spreadcast, and the guide to scheduling social media posts with Claude covers the posting habit around it.