
Video Transcript Scraper: Youtube, X, Facebook, Tiktok, etc.
Pricing
$19.99/month + usage

Video Transcript Scraper: Youtube, X, Facebook, Tiktok, etc.
Scrapes transcripts from online video/audio content on multiple plateforms (Youtube, X, ..) in any available language. It delivers outputs in both JSON and LLM-ready formats, making it ideal for analytics, and AI-based applications. Perfect for research and building intelligent conversational agents
3.0 (6)
Pricing
$19.99/month + usage
79
Total users
901
Monthly users
123
Runs succeeded
>99%
Issues response
1.4 days
Last modified
a month ago
You can access the Video Transcript Scraper: Youtube, X, Facebook, Tiktok, etc. programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, you’ll need an Apify account and your API token, found in Integrations settings in Apify Console.
{ "mcpServers": { "local-actors-mcp-server": { "command": "npx", "args": [ "-y", "@apify/actors-mcp-server", "--actors", "invideoiq/video-transcript-scraper" ], "env": { "APIFY_TOKEN": "<YOUR_API_TOKEN>" } } }}
Configure MCP server with Video Transcript Scraper: Youtube, X, Facebook, Tiktok, etc.
You can interact with the MCP server via standard input/output - stdio (as shown above), which is ideal for local integrations and command-line tools such as the Claude desktop client, or you can interact with the server through Server-Sent Events (SSE) to send messages and receive responses, which looks as follows:
{ "mcpServers": { "remote-actors-mcp-server": { "type": "sse", "url": "https://mcp.apify.com/sse?actors=invideoiq/video-transcript-scraper", "headers": { "Authorization": "Bearer <YOUR_API_TOKEN>" } } }}
You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other supported MCP client of your choice.
If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.