Best Instagram MCP Servers in 2026: 12 Compared by What They Can Actually Do

There is no official Instagram MCP server. Meta has not published one, and neither Anthropic nor OpenAI ships an Instagram connector. Every "Instagram MCP" you can install is third-party, and they do very different things: some publish posts, Reels and Stories through Meta's API, some answer your DMs and comments, some log in with your password and act like the Instagram app, and some only scrape public data.

This page sorts the twelve that come up most, using two sources only: each vendor's own documentation, and Meta's developer documentation for the Instagram Platform. Everything was checked on 12 October 2026, and every row links to where the fact came from. For servers that post to every network, not just Instagram, see social media MCP servers compared.

The three kinds of Instagram MCP server

Every server below is one of three kinds, and the kind decides what it can do and what it risks:

1. Hosted, on Meta's official API. You sign in once (OAuth) on Instagram's or Facebook's own screen, and the server publishes through the API. No developer app, nothing to install. Antwork, Zernio, Buffer, Metricool, Postiz, Ayrshare and PostMCP.
2. Automation bridges. Instagram is one connector among hundreds, used as a step in a wider workflow. Composio and Zapier. The do-it-yourself version of the official API, jlbadano/ig-mcp, sits close to this group: free, but you bring your own Meta app.
3. Private API and scrapers. The server either logs in with your username and password through an unofficial client, so it can do what the app does, or it scrapes public pages without logging in at all. trypeggy/instagram_dm_mcp and Apify.

What Meta's API lets any MCP server do

Before comparing tools, it helps to know what Meta's official Instagram API allows. That list decides which MCP servers can be built "properly" and which can only work by logging in as you. It also answers most of the "why can't my AI do X on Instagram" questions.

One inconsistency worth knowing: the same content publishing guide also says, in its carousel section, that accounts are limited to 50 published posts in 24 hours. Some vendors below quote 50, some quote 100. Plan for the lower figure.

Three practical consequences:

1. Publishing is the job an ordinary app does best. Feed posts, carousels, Reels and Stories are all in the API, which is why most of the servers below are publishing tools.
2. Inbox work is possible, but only as replies. An official-API server can answer comments and reply to DMs within 24 hours of the last message. It cannot open a conversation.
3. If a server follows, likes, sends the first DM or reads private accounts, it is not using Meta's API. It is either logged in with your password through an unofficial client or scraping, and that is where the account risk sits.

Pick by job, not by star count

• Publish your own posts, carousels, Reels and Stories from Claude or ChatGPT. Use a hosted server with its own approved Meta app: you sign in once and never handle a token. Antwork, Zernio, Buffer, Metricool and Postiz are in this group.
• Answer DMs and comments from the chat. Zernio. It is the only publishing server here that documents DM replies, comment moderation and insights alongside Reels and Stories, all on the official API.
• Analytics and competitor research next to publishing. Metricool, with the caveat that its MCP does not cover inbox messages or comments.
• Post as the last step of an automation (a new product, a new blog post). Composio or Zapier, where Instagram is one connector among many.
• Public data from other accounts. Apify runs a scraper actor and bills per result. It publishes nothing.

Publishing servers, one by one

Private API and scraping servers

trypeggy/instagram_dm_mcp is the best-known DM server on GitHub. It logs in with your Instagram username and password, saves a session file, and its requirements pin instagrapi, an unofficial Instagram client. That is how it can do what Meta's API does not allow: send the first message, list and search chats, and read other users' posts, stories, followers and following. Its README carries no warning about account risk, so here is ours: Meta's API only lets apps in through Instagram Login or Facebook Login, and this is not either of those. Use it only on an account you can afford to lose. It does not publish posts.

Apify runs an Instagram Scraper actor that extracts public posts, Reels, profiles, hashtags and comments with "No Business or Creator account, no OAuth". You reach it from Claude through Apify's hosted MCP at https://mcp.apify.com, and it bills per result. Bright Data offers a similar public-data MCP with a free tier of 5,000 requests a month. Neither publishes anything.

If your goal is posting, none of these is the right tool, however many stars they have.

How to connect an Instagram MCP server

The steps are the same for any hosted server. Here they are with Antwork's URL; swap in your vendor's. Whatever the server, the Instagram account must be Business or Creator. Switching is free in the Instagram app's settings.

• Claude (claude.ai and Claude Desktop): Settings → Connectors → Add custom connector, paste https://api.antwork.io/mcp, sign in, then ask Claude to connect Instagram. The full walkthrough is in how to connect Claude to Instagram.
• ChatGPT: turn on Developer mode in Settings → Security and login, open Plugins in the sidebar, click +, and paste the URL. ChatGPT only accepts remote servers, so local GitHub servers will not work here. Walkthrough: how to connect ChatGPT to Instagram.
• Claude Code: run claude mcp add antwork --transport http https://api.antwork.io/mcp, then /mcp to sign in.
• Cursor: add the URL as a remote MCP server in Cursor's MCP settings.

Then ask for something concrete:

Before you give an AI publish rights

• Prefer OAuth over passwords and pasted tokens. An OAuth grant can be revoked from Instagram's settings. A password in a .env file is the whole account.
• Keep a review step. An assistant with publish rights and an untrusted document in its context (an email, a web page) can be talked into posting. Choose a server that creates drafts and publishes only on an explicit request.
• Know the ceiling. Meta caps API publishing per account per 24 hours, and its own guide gives both 100 and 50. No tool gets around that.
• Match the tool to the job. Use a password-based or scraping server only for work that genuinely needs it, and never on an account you cannot afford to lose. More on what Antwork does and does not do is in the MCP docs, and prices are on the pricing page.