instagram-mcp-server
Related Servers
Alternatives to instagram-mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceEnables posting and managing Instagram content (photos, reels, stories, carousels) and interacting with media and comments via Instagram Graph API.107 npm-
- AlicenseAqualityCmaintenanceEnables publishing photos, reels, and stories to Instagram, reading and moderating comments, fetching performance insights, drafting captions via MCP sampling, and scheduling reels for later.1328 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables AI clients to operate Instagram Business and Creator accounts through Meta's official API with OAuth 2.1 authentication, covering publishing images, carousels, reels and stories, content scheduling, comment moderation, Direct messaging, and account and media insights across multiple connected accounts. An optional read-only private-session reader exposes Direct inbox threads, and a webhook-backed archive accumulates conversation history that Meta's API cannot return on demand.-
- AlicenseBqualityBmaintenanceEnables reading, publishing, commenting on, and analyzing Instagram Business/Creator accounts through the official Graph API, with multi-account support and an optional self-hosted publishing panel.29MIT
- AlicenseAqualityCmaintenanceEnables AI agents such as Claude and Cursor to run an Instagram Business or Creator account through Meta's official Graph API: reading profile, post and audience insights; preparing and publishing posts, carousels, reels and stories with a confirm-before-publish step; managing comments and direct messages; and searching hashtags. It also ships with a demo mode that lets every tool work without an Instagram account or access token.17MIT
- 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 37 tools
Most tools have clearly distinct resource+action targets, and descriptions explicitly differentiate close pairs (hide vs delete comment, reply_to_comment vs create_comment, tagged media vs mentions). The main overlaps are the low-level container escape hatch (create_container/publish_container) versus the high-level publish_* tools, and get_media_insights versus get_story_insights, both of which are called out in the descriptions rather than left ambiguous.
Every tool uses the instagram_ prefix with snake_case verb_noun structure (publish_reel, list_comments, get_media_insights, reply_to_comment). Variants like mark_seen and toggle_media_comments still follow the same verb-first convention, so an agent can predict names reliably.
37 tools is heavy for a single-account publishing/insights server, well above the 25-tool threshold. Several groups could be consolidated (five publish variants, three token/auth tools, three mention tools), and the surface is large enough that an agent must read carefully to pick correctly.
Coverage is broad and coherent across publishing, media reading, comments, DMs, insights, mentions and auth — essentially the full Graph API surface for a professional account, including quota and token diagnostics. Minor gaps: instagram_list_tagged_media references an instagram_list_mentions tool that does not exist in this set, and there is no media-deletion capability (though Meta's API largely forbids it).