Instagram Account MCP
Related Servers
Alternatives to Instagram Account MCP
No user-submitted related servers found.
Related Servers
- 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
- AlicenseNot gradedqualityDmaintenanceA production-ready Remote MCP Server that gives Claude direct, tool-based access to your Instagram Business account through the Meta Graph API — profile data, posts, comments, publishing, insights, analytics, hashtags, messaging, and real-time webhooks.11 npmMIT
- AlicenseBqualityBmaintenanceSelf-hosted MCP server and CLI for publishing and scheduling Instagram Reels, photos, carousels and stories through the official Instagram Graph API. Validates and auto-fixes media with ffmpeg, keeps a persistent queue, and lets AI agents read insights and reply to comments.121MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to operate an Instagram account through standard MCP tools — searching hashtags, reading posts and comment threads, posting comments and replies, reading and sending direct messages, fetching the timeline feed, and liking media — while managing Python FastMCP subprocess lifecycle, persistent login sessions, and two-factor authentication.228 npmMIT
- AlicenseNot gradedqualityDmaintenanceExposes Instagram actions (posts, media, comments, DMs, insights, Messenger profile) to Claude and ChatGPT via MCP.1MIT
- FlicenseNot gradedqualityCmaintenanceA production-ready MCP server for interacting with Instagram/Meta APIs, enabling AI agents to manage content, analyze performance, research competitors, and handle publishing workflows.-
TDQS
Scored across 65 tools
Most tools target a clearly distinct action+resource (publishing, comment moderation, DM, scheduling, analytics), and the descriptions explicitly cross-reference when to prefer one over another (e.g. hide_comment over delete_comment, generate_hashtags vs hashtag_research). The remaining overlaps sit in clusters — get_media_insights / analyze_post / find_outliers / get_account_insights / benchmark_competitor, and list_comments / triage_comments / list_mentions — where an agent must read carefully to pick correctly.
Almost entirely snake_case, with a dominant verb_noun shape (publish_photo, reply_to_comment, get_media_insights, delete_template). A handful of noun/status names break the pattern (publish_budget, auth_status, media_host_status, hashtag_budget, ai_status, content_ideas), but the casing convention never varies, so the set stays predictable.
65 tools is far above what an agent can hold in context comfortably, even for a broad domain. Several analytics tools (get_media_insights, analyze_post, find_outliers, best_publish_time, export_insights) and AI-writing tools (generate_caption, generate_hashtags, suggest_carousel, translate_caption, content_ideas) could be consolidated behind a mode parameter.
The surface covers the full lifecycle: connect/auth, media prep, publish/schedule/cancel/resume/status, media and story listing, comments and DMs, insights and audience, competitor and hashtag research, A/B testing, AI drafting and templates. The only apparent gaps are Meta API restrictions (caption editing, sticker/music on stories), which are documented in the descriptions rather than left as dead ends.