instagram-data-mcp
Related Servers
Alternatives to instagram-data-mcp
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityBmaintenanceEnables MCP clients to read public Instagram profiles, content, engagement, discovery, and search results through a hosted, read-only API.50 npmMIT- AlicenseAqualityAmaintenanceEnables MCP clients to look up public Instagram profiles by handle and page through their public post feeds, returning structured JSON data such as follower counts, bios, and engagement metrics.293 npm20 PyPI15MIT
- FlicenseNot gradedqualityAmaintenanceEnables sending direct messages, managing chats and media, retrieving user, story, and follower information, and performing engagement actions on Instagram through MCP tools.-
- FlicenseNot gradedqualityAmaintenanceEnables users to send, retrieve, search, and manage Instagram Direct Messages and related media, threads, users, stories, likes, followers, following, and posts from their Instagram account through MCP tools.-
- AlicenseNot gradedqualityBmaintenanceInstagram MCP by SocialDataX for public post search and details, comments and replies, creator profiles and posts, and video or Reels speech-to-text.MIT
- AlicenseNot gradedqualityCmaintenanceWraps the unofficial Instagram private API into 34 ready-to-use tools, enabling AI agents to log in, search users and hashtags, browse, like, comment on, upload and download media, send DMs, and view stories through any MCP client. It provides agent-readable errors, flexible username/URL references, and automatic session relogin.MIT
TDQS
Scored across 27 tools
Most tools map to distinct Instagram resources or actions, and descriptions clarify scope (e.g., followers vs following, post vs media). However, a few close pairs remain: highlights/highlight, posts/post/media, and the three search endpoints can require careful reading to select correctly.
All tools use lower_snake_case with a consistent instagram_ prefix, and singular/plural forms generally signal single-resource vs collection endpoints. The pattern is predictable despite a few compound names.
27 tools is heavy for an MCP server and exceeds the 25+ threshold; while most endpoints are distinct, the breadth increases selection burden. Some adjacent operations (highlight/highlights, user_id/username, search variants) could be consolidated.
The surface covers profiles, social graph, posts/reels, stories/highlights, search, comments, likers, insights, and media URLs, which is broad for a read-only Instagram data API. Minor gaps remain, such as no single-comment endpoint or dedicated hashtag/location/user search variants, but core workflows are covered.