Instagram MCP Server
Related Servers
Alternatives to Instagram MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables publishing, scheduling, and measuring Instagram carousel, image, Reels, and Story posts, along with listing and responding to comments and checking account metrics through natural language.15MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Instagram Business accounts by automating content publishing, scheduling posts, and analyzing performance metrics. Supports posts, stories, reels, and carousels with detailed audience insights and hashtag discovery.1-
- FlicenseBqualityDmaintenanceEnables AI agents to control Instagram accounts programmatically, supporting profile management, media interaction, direct messaging, and follower management.132-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to inspect public Instagram profiles, posts, reels, comments, and hashtags anonymously, and to publish stories and posts, send direct messages, comment, and fetch account insights through an authenticated session.MIT

@inssist/mcpofficial
AlicenseAqualityBmaintenanceEnables AI agents to manage a personal Instagram account through a logged-in browser session, supporting actions like reading profiles and DMs, publishing posts, reels, and stories, scheduling content, and accessing insights and audience reports.62691 npm15MIT- FlicenseNot gradedqualityAmaintenanceEnables AI applications to programmatically interact with Instagram Business accounts through the Graph API, covering profile and media retrieval, engagement insights, publishing images and videos, and reading or replying to direct messages. It exposes these capabilities as tools, resources, and prompts so clients can manage content and analyze performance through natural language.-
TDQS
Scored across 25 tools
Each tool maps to a distinct resource+action (account, media, comment, DM, ad, event), and the descriptions carefully differentiate similar tools like send_dm vs send_human_agent_dm and get_account_info vs get_account_insights. The main risk is the density of overlapping read/insights and send/write tools, but a focused agent can usually pick correctly.
All tools use consistent lower_snake_case with a clear verb-first pattern: get_, list_, publish_, reply_, hide_, delete_, send_, like_, unlike_, search_, create_, update_. The minor 'get' vs 'list' variation is standard and does not hurt predictability.
At 25 tools, this sits at the heavy end of the scale and covers many domains: account, publishing, comments, DMs, engagement, hashtags, events, and ads. Each tool is individually justified, but the surface is broad enough that splitting into focused servers might reduce complexity.
Core workflows are covered: publishing/list/deleting media, managing comments, replying to DMs, and reading account/ads insights. However, there are notable gaps such as get_ad_accounts referencing a create_ad tool that does not exist, no update/delete for events, and no way to post an original top-level comment rather than just replying.