Instagram MCP: No Official Meta Server, and What Works
Meta does not publish an Instagram MCP server. Every “Instagram MCP” you’ll find — AleemHaider/instagram-mcp, jlbadano/ig-mcp, Bob-lance/instagram-engagement-mcp, and a dozen smaller ones — is community-built, and the good ones are thin wrappers around Meta’s own Instagram Graph API. Meta’s only shipped MCP server on the social side is the Meta Ads connector from its April 2026 AI Connectors beta, and that one manages paid campaigns, not your organic account. There is no Meta-maintained equivalent for posting, comments, DMs, or insights.
That’s the easy half of the answer. The harder half is that most people searching for this can’t use any of it, for a reason that has nothing to do with MCP.
Instagram is one of many — the complete list of MCP servers covers every app that ships one, grouped by category.
The account gate that stops most Instagram MCP plans
Before you clone a repo, check whether Instagram will let you in at all. Every honest Instagram MCP server runs on the Graph API, and the Graph API requires:
- A professional account — Business or Creator. Personal accounts are structurally locked out. The Instagram Basic Display API, which was the last route to personal-account data, was shut down in December 2024 and nothing replaced it.
- A Meta app. You create it in the Meta developer console, wire up OAuth, and manage token refresh yourself. Long-lived tokens expire in 60 days.
- A Facebook Page — sometimes. If you authenticate through Facebook Login for Business, your Instagram account must be connected to a Page. If you use the newer Instagram Login path, no Page is required — but you give up hashtag search and product tagging.
- App Review, if the account isn’t yours. Standard Access covers accounts you own or manage. The moment your app touches someone else’s Instagram — a client’s, an agency roster’s — you need Advanced Access, which means App Review plus Business Verification, on Meta’s own 2-to-4-week timeline.
If you’re a creator running your own professional account, you’re in the easy lane: your own app, Standard Access, no review. If you manage Instagram for clients, budget weeks, not an afternoon.
The shortcut that gets accounts banned
Some community Instagram MCP servers skip all of that by logging in with a username and password and calling Instagram’s private mobile API — the same endpoints libraries like instagrapi reverse-engineer. Repos in this category usually say so in the README: not affiliated with, endorsed by, or supported by Meta Platforms.
Don’t do this on an account you care about. It violates Instagram’s terms, Meta actively detects it, and the penalty is the account — not a warning. It also means handing your live Instagram password to a local server process. The workarounds people trade around (saved sessions, residential proxies, randomized delays) are effort spent making detection slower, not making the practice allowed. A Graph API server is more work to set up and is the only version that doesn’t put your account at risk.
What the Graph API actually lets an MCP server do
Assume you’ve cleared the gate and installed a Graph-API-backed server like AleemHaider/instagram-mcp (roughly 24 tools across profile, publishing, comments, DMs, and insights). Here’s the honest shape of what you get:
- Publishing works, with edges. Feed posts, carousels, Reels, and Stories can all be published. But JPEG is the only supported image format — no PNG, WebP, or GIF — carousels cap at 10 items, and every image in a carousel gets cropped to the first one’s aspect ratio. Shopping tags and filters aren’t available through the API. The account limit is 100 API-published posts per rolling 24 hours.
- Insights are read-only and account-scoped. Reach, impressions, engagement, follower counts, per-post performance. Fine for reporting.
- Comments are the most usable surface. Read, reply, hide, delete on your own media.
- DMs are heavily fenced. You can reply inside the 24-hour window a user opens by messaging you. The
HUMAN_AGENTtag that extends that to 7 days is explicitly for messages typed by a person — using it for automated sends is a policy violation Meta blocks and enforces against. - No scraping. You cannot pull arbitrary public profiles, competitor follower lists, or hashtag feeds through the official API. Anything promising that is running on the private API, with the ban risk above.
That last point catches a lot of people. If your plan was “have Claude analyze my competitors’ Instagram,” the official path doesn’t do it and the unofficial path risks your account.
Setting one up without breaking anything
If you’ve decided the Graph API path is worth it, the order matters — most failed setups are an account or permission problem misread as a server problem:
- Convert to a professional account first and decide your login path. Facebook Login for Business needs a linked Page; Instagram Login doesn’t but drops hashtag search.
- Create a Meta app, add the Instagram product, and request the permissions your use case actually needs —
instagram_business_basicplusinstagram_business_content_publishcovers posting on the Instagram Login path. - Generate a long-lived token and set a reminder to refresh it. Sixty days arrives faster than you expect, and an expired token looks exactly like a broken server.
- Pick a server that names the Graph API in its README. If setup asks for your Instagram username and password rather than a token, that’s the private-API route — walk away.
- Test read-only first. Pull your profile and recent media before you let anything publish or reply.
Where any Instagram MCP server stops
Even with everything working, MCP has a shape that doesn’t fit social media management.
MCP servers wait to be asked. The protocol has no scheduler and no event mechanism — its maintainers acknowledge that change detection today means polling — so an MCP connection can answer a question but cannot notice something on its own.
For an Instagram workflow, that’s the whole problem. The moments that matter are events: a comment lands, a DM arrives, a Reel takes off, someone tags you. An MCP server can’t notice any of them. It sits there until you open a chat and ask. So “auto-reply to comments,” “alert me when a post outperforms,” and “post every Tuesday at 9am” are all outside what MCP does, no matter which server you install.
It’s also one app at a time. Getting a new DM into your CRM and a Slack channel means a separate MCP server, separately authed, for each — and hoping your client juggles them in one turn.
Running Instagram work that doesn’t need a chat window open
That gap — triggered, scheduled, across apps — is where Carly fits. Carly connects to Instagram natively, so there’s no server to host, no Meta app to register, and no token refresh to babysit. The same professional-account rule still applies, because it’s Meta’s rule and not a Carly one: you’ll need a Business or Creator account, same as any Graph API tool.
What changes is that the work runs on its own:
- When a comment mentions a keyword → draft a reply, log it to a sheet, and ping you in Slack if it needs a human.
- Every Monday morning → pull last week’s post insights, compare them to the prior week, and email you what moved.
- When a product goes live in Shopify → draft the caption and publish the Instagram post with the image you approved.
The non-AI steps — moving, matching, and routing between apps — are free and unlimited, the Zapier-style backbone underneath. The AI steps (drafting captions, summarizing performance, deciding what needs a human) start at $35/month. You describe the outcome in plain language.
If you want to interrogate your account from a chat window and you’re comfortable registering a Meta app, a community Instagram MCP server does that job. If you want Instagram to respond to things while you’re doing something else, that’s the part MCP wasn’t built for. The same split shows up across ChatGPT’s MCP server support and in the per-app guides for ChatGPT and Instagram and Claude and Instagram.
FAQ
Does Instagram have an official MCP server? No. Meta publishes no MCP server for Instagram. The only official Meta MCP connector covers Meta Ads campaign management, released in open beta in April 2026, and it does not handle organic posting, comments, DMs, or insights. Every Instagram MCP server available is community-built.
Can I use an Instagram MCP server with a personal account? No. The Instagram Graph API requires a professional account — Business or Creator. Personal accounts have had no official API route since the Basic Display API shut down in December 2024. Community servers that claim personal-account support are using Instagram’s private API with your login credentials, which violates Instagram’s terms and risks a permanent ban.
Do I need App Review to use an Instagram MCP server? Only if you’re accessing accounts you don’t own or manage. Standard Access covers your own professional account. Managing clients’ Instagram accounts requires Advanced Access, which means App Review plus Business Verification — Meta documents a 2-to-4-week timeline per submission.
Can an Instagram MCP server auto-reply to comments or DMs?
Not on its own. MCP has no triggers and no scheduler, so nothing fires when a comment or DM arrives — the server only acts when you ask it to inside a chat. Instagram’s own rules also fence automated DMs tightly: replies are limited to the 24-hour window a user opens, and the 7-day HUMAN_AGENT extension is prohibited for automated messages. For event-driven Instagram work, you need a workflow tool rather than an MCP server.
Can I connect Instagram to AI without hosting a server? Yes. Carly connects to Instagram directly and lets you describe the automation in plain language — no Meta app to register, no OAuth to wire, no token refresh. You still need a Business or Creator account, since that requirement comes from Meta.
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
