Instagram Reel Transcripts from audio (Apify)

io.github.Rwb3nPublished by GitHub account Rwb3nv1.0.0Updated Oct 25, 2026

Instagram reel transcripts from the audio, in the language spoken, via Apify. Silent reels free.

The publisher's own server: Apify MCP Server

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingMedia & Design

Overview

AI-generated overview

An Apify-hosted remote MCP server that lets an assistant fetch transcripts of Instagram reels, generated from the reel audio in the spoken language.

What you can do
Retrieve transcripts of Instagram reels, produced from the audio in the language actually spoken in the video. Silent reels are handled at no cost. Access is through an Apify-hosted remote endpoint rather than a local package.
When to use it
Useful when you want an assistant to pull the spoken content of Instagram reels into text, for example to review or quote what is said in a video without watching it.
Requirements
A remote MCP endpoint at mcp.apify.com over streamable HTTP. An Apify account is needed; authentication is by OAuth or an optional Bearer token supplied in the Authorization header. Network access to Apify is required.
Before you install
The Authorization header carries an Apify account credential, so treat it as a secret. Requests go to Apify's hosted service, which processes the reel content on your behalf. Transcripts depend on audio quality and may be inaccurate.

Installation

In SourceWeft

  1. Open Instagram Reel Transcripts from audio (Apify) in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Rwb3n%2Finstagram-transcripts/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "instagram-reel-transcripts-from-audio-ap": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=neonroobz/instagram-transcripts"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 25, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Apify integrations