unofficial-instagram-mcp
Related Servers
Alternatives to unofficial-instagram-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to operate a logged-in Instagram account through a real Chrome browser, including reading content, managing DMs and comments, liking and following, analyzing followers and insights, discovering and enriching leads, and drafting or publishing posts.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- 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
- AlicenseAqualityFmaintenanceEnables AI assistants to interact with Instagram by scraping profiles, posts, reels, DMs, and business insights through a robust, DOM-agnostic browser orchestration engine that bypasses Instagram's anti-automation measures.281Apache 2.0
- FlicenseBqualityDmaintenanceEnables AI agents to control Instagram accounts programmatically, supporting profile management, media interaction, direct messaging, and follower management.132-
- FlicenseNot gradedqualityAmaintenanceEnables users to send Instagram Direct Messages, manage chats and messages, download media from conversations, and retrieve user, story, follower, and post information through natural-language tool calls.-
TDQS
Scored across 34 tools
The domain prefixes (dm_, post_, story_, user_) plus descriptors make most boundaries clear, and paired read/write tools are explicitly linked in their descriptions (post_comments ↔ post_reply_to_comment, stories_tray ↔ story_view). A few pairs still need care: story_create vs story_create_poll, dm_list_threads vs dm_check vs dm_read_thread, and post_get vs media_urls vs post_comments all touch the same resource and could be mispicked by a hurried agent.
Theming is recognizable but conventions are mixed: dm_list_threads/dm_read_thread/dm_send are verb-first, whereas post_like, post_get, user_follow, and profile_get are noun-first, and un-prefixed names like `search` sit alongside prefixed ones. The story family is also split between the singular `story_*` (view, reply, create, delete) and plural `stories_tray`, which breaks the otherwise tidy prefix scheme.
34 tools is heavy for a single-account browser automation surface, and a handful (media_urls, explore_posts, ig_selftest, story_create_poll) feel like variants rather than independent capabilities. That said, the breadth mirrors the real Instagram web surface (DMs, posts, comments, stories, social graph), so most tools map to a distinct UI action rather than bloat.
Read/write coverage is genuinely broad: DMs, posts, comments, stories, follows, search, feed/explore/hashtag browsing, notifications, and a documented self-test harness, with sane idempotency and dry-run semantics. The gaps are mostly inverse operations (unlike, unsave, delete comment, delete DM, block/report) and no post/profile editing, which agents can work around but leave the lifecycle slightly asymmetric.