instagram-data-mcp
Related Servers
Alternatives to instagram-data-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceMCP server for HikerAPI — auto-generates 100+ Instagram tools (profiles, posts, reels, stories, comments, hashtags, locations) from the live OpenAPI spec. Local stdio via npx -y hikerapi-mcp, requires only HIKERAPI_KEY.10050 npm8MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for downloading Instagram content (videos, reels, audio, carousels) using yt-dlp, with tools for downloading media and fetching metadata. Supports stdio and HTTP transports.MIT
- FlicenseBqualityDmaintenanceProvides Instagram analytics, media downloads, and search capabilities through an MCP interface for use with Claude and other MCP clients.4341-
- AlicenseNot gradedqualityCmaintenanceA 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.16 npmMIT
- AlicenseAqualityBmaintenanceEnables MCP clients to retrieve read-only public Instagram data through 27 tools covering profiles, posts, reels, stories, highlights, comments, likers, followers, hashtags, places, audio and keyword search. No login is required, and every response reports remaining API credits.27MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for DataLikers — 29 hand-built tools for Instagram & TikTok data: user search by demographics (gender/age/race/country), profiles, engagement, hashtags, locations, business accounts, top-users. Local stdio via npx -y datalikers-mcp, requires only DATALIKERS_KEY.15 npm9MIT
TDQS
Scored across 27 tools
Most tools target a distinct resource, but several near-duplicate pairs invite misselection: instagram_highlights vs instagram_highlight (list vs items), instagram_posts vs instagram_post (list vs single), and instagram_reels vs instagram_reels_search. Descriptions do clarify the boundaries, and lookup tools (username/user_id/check) are distinguishable, so confusion is limited rather than pervasive.
Every tool follows the exact same instagram_ prefix plus snake_case noun pattern (instagram_profile, instagram_place_posts, instagram_audio_search). No mixed conventions or vague verbs anywhere.
27 tools is heavy and sits just past the point where each tool clearly earns its place. The domain is genuinely broad (profiles, posts, reels, comments, hashtags, places, audio, search), so the count is defensible, but it is on the bloated side for an agent to navigate.
Coverage is broad and coherent for a read-only Instagram data API: profiles, posts, reels, stories, highlights, comments, likers, followers/following, hashtags, places, audio, search and insights. Minor gaps (e.g. no comment-level or follower-delta analytics beyond what exists) are workable but keep it from a perfect score.