instagram-mcp
Related Servers
Alternatives to instagram-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for interacting with Instagram Business accounts via the Instagram Graph API, enabling profile retrieval, media publishing, insights, and direct messaging.MIT
- 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.-
- AlicenseNot gradedqualityCmaintenanceMCP server for Instagram Graph API integration, enabling AI applications to manage Instagram Business accounts: fetch profiles, media, insights, publish content, and handle DMs.MIT
- AlicenseBqualityBmaintenanceAn MCP server for the official Instagram Graph API, enabling read, publish, comment, and analytics across Instagram Business/Creator accounts.2991 PyPI13MIT
- 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
- AlicenseNot gradedqualityDmaintenanceAn MCP server that integrates with Instagram's Graph API to enable AI-driven management of Instagram Business accounts. It provides tools for fetching profile data, publishing media, analyzing engagement metrics, and managing direct messages.203MIT
TDQS
Scored across 25 tools
Most tools target clearly distinct resources and actions (comments, insights, media, account, publishing). The main ambiguity is the dual publishing path: instagram_create_media_container + instagram_get_container_status + instagram_publish_media overlaps with instagram_post_image/reel/story, which wrap the same flow. Descriptions mitigate this, but an agent must still choose between low-level and high-level tools for the same outcome.
All 25 tools follow the instagram_ prefix with snake_case verb_noun naming (create_, get_, list_, post_, hide_, etc.). No mixed conventions; the pattern is predictable and readable throughout.
25 tools is on the heavy side for a single server; the domain is broad, but some capabilities (e.g., hide/unhide, multiple insight entry points) could potentially be consolidated. Each tool maps to a distinct API operation, so it's borderline rather than excessive.
The surface covers the core professional account lifecycle: profile, media publishing (image/reel/story/carousel), container status, publishing limit, media listing, comments moderation, and insights. Minor gaps include no tool for @mentions retrieval (explicitly noted as a separate capability) and no token refresh tool, but agents can work around these.