Skip to main content
Glama
dr-ashraf-s-MCP-LABS

Instagram MCP Server

by dr-ashraf-s-MCP-LABS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Instagram MCP Server

No user-submitted related servers found.

    Related Servers

    • Instagram DM MCP Server

      addity3
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables sending and receiving Instagram Direct Messages, managing conversations, downloading media, viewing user profiles and stories, and interacting with posts through natural language in Claude.
      MIT

    • meta-mcp

      alissonjcdev
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects Claude to Instagram through Meta's official API, enabling users to retrieve account insights, analyze professional profiles, publish photos/carousels/reels/stories, manage comments, read and respond to Direct messages, and call any Graph API endpoint.
      22 npm
      MIT

    • Instagram MCP Server

      luminarylane
      A
      license
      A
      quality
      B
      maintenance
      Connects Claude Desktop and other MCP clients to the Instagram Graph API for reading analytics, managing comments, and publishing photos, carousels, and reels.
      11
      28 npm
      1
      MIT

    • instagram-mcp

      Stupidoodle
      A
      license
      B
      quality
      A
      maintenance
      Enables Claude to read and send Instagram DMs, manage threads and message requests, send media, and run autonomous conversations via the /dm skill.
      27
      3
      MIT

    • reel-relay

      siemd2
      A
      license
      Not graded
      quality
      D
      maintenance
      Forwards Instagram reels to Claude with timestamped transcripts and video frames, enabling Claude to watch, research, and build based on shared content.
      10
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 25 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose. Overlapping areas like hide vs delete comment and send DM vs human agent DM are well-differentiated by descriptions.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with underscores, making them predictable and machine-readable.

    Tool Count3/5

    With 25 tools, the server sits at the upper end of the borderline range (16-25). While the coverage is broad, the count feels slightly heavy for a single server.

    Completeness2/5

    Notable gaps exist: a 'create_ad' tool is referenced in descriptions but missing, and lifecycle operations for events (update/delete) are absent, which may cause agent failures.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources