Skip to main content
Glama
HikerAPI — Instagram MCP

HikerAPI — Instagram MCP

Related Servers

Alternatives to HikerAPI — Instagram MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for DataLikers — 51 tools for Instagram & TikTok data: Instagram user search by demographics (gender/age/race/country/city), profiles, engagement, posts, comments, hashtags, locations, stories, business accounts; TikTok users, videos, comments, hashtags, playlists. Local stdio via npx -y datalikers-mcp, requires only DATALIKERS_API_KEY.
      64 npm
      9
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for LamaTok TikTok data API — auto-generates 20+ tools from the live OpenAPI spec (users, videos, hashtags, music, comments). Local stdio via npx -y lamatok-mcp, requires only LAMATOK_KEY.
      23
      61 npm
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients like Claude and Cursor to query public Instagram data read-only — profiles, posts, reels, stories, highlights, comments, likers, followers, hashtags, places, audio and search — over local stdio without writing files or storing anything.
      28
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      16 Instagram creator tools as an MCP server — Reels/Story/carousel downloaders, engagement audit, hashtag search, Reels hook generator, best-time-to-post and content calendar. Wraps instapdown.com public API — no auth required.
      16
      56 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      Thin MCP server that turns each tool into one authenticated call to a self-hosted Instagram REST API, letting an agent schedule and publish posts, take and keep insights snapshots, and reply to comments and DMs by rules within Meta's limits. At startup it reads the API token's permissions and exposes only the tools that token can use.
      MIT

    TDQS

    A4.1/5.0

    Scored across 44 tools

    Disambiguation4/5

    The tools cover many distinct Instagram resources and actions, and descriptions explicitly cross-reference alternatives such as by id vs username vs URL vs shortcode, or top vs recent vs clips. While no two tools are truly interchangeable, the sheer number of near-variants increases cognitive load and misselection risk.

    Naming Consistency4/5

    All tools use a get_ + lowercase snake_case convention, making the pattern predictable. Minor inconsistency comes from mixed API-version prefixes (v1, v2, gql, g2) and compound tokens like fbsearch, usertags, and clips_chunk, but the naming remains readable and largely consistent.

    Tool Count2/5

    44 tools far exceeds the typical 3-15 range and includes many access-method variants that could be consolidated into fewer flexible tools. While each maps to a real endpoint, the set is heavy and likely to overwhelm tool selection.

    Completeness4/5

    The surface covers users, media, comments, likes, stories, highlights, search, hashtags, locations, music, followers/following, suggestions, and account provenance, giving broad read-only Instagram coverage. Gaps exist for less common data such as live videos, saved media, or media by music track, but core workflows are covered.

    Maintenance

    ActivitySlowing
    ResponsivenessOutdated data