Skip to main content
Glama
Sign In
Reels Research MCP

Reels Research MCP

by jindratilk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Reels Research MCP

No user-submitted related servers found.

    Related Servers

    • reel-to-text

      salto-agancy
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to transcribe Instagram Reels into text by providing a tool that accepts a Reel URL and returns the speech transcript along with metadata such as author and duration.
      MIT

    • reelminner

      ilovekushgola
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to scrape Instagram Reels and public profile data (metadata, engagement, owner info) without the official API, via tools for scraping, status checks, cookie import, stopping, and exporting results.
      1
      MIT

    • Instagram MCP Server

      ishan-parihar
      A
      license
      A
      quality
      F
      maintenance
      Enables AI assistants to interact with Instagram by scraping profiles, posts, reels, DMs, and business insights through a robust, DOM-agnostic browser orchestration engine that bypasses Instagram's anti-automation measures.
      28
      1
      Apache 2.0

    • Reel Library

      ic3w4r
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes a locally built, searchable index of your saved Instagram reels — AI summaries, key points, transcripts, categories, and every extracted tool, place, product, and link — to any AI assistant over MCP. Enables chat-based search and retrieval across the whole collection without leaving the conversation.
      Apache 2.0
    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

    A4.6/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: reels_fetch reads a Reel by URL, reels_links collects Reel URLs from web pages, and reels_doctor verifies environment dependencies. There is no overlap in what they do or when to invoke them.

    Naming Consistency5/5

    All three tools use the same snake_case pattern with a shared 'reels_' prefix followed by a distinct noun/verb (fetch, links, doctor). The convention is fully predictable.

    Tool Count4/5

    Three tools is on the lean side, but the server has a narrow, well-defined scope (reading Instagram Reels for research), and each tool earns its place: discovery, fetching, and diagnostics. Nothing is redundant, though it borders on thin.

    Completeness4/5

    For a read-only research surface, the lifecycle is largely covered: reels_links discovers URLs, reels_fetch retrieves content (details, transcript, frames, comments), and reels_doctor handles troubleshooting. A minor gap is the lack of a direct search/discovery tool (correctly noting Instagram has no anonymous search), but the web-page link extraction compensates.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources