
Tiktok | Instagram | Facebook | Transcriber
Pricing
$22.00 / 1,000 transcriptions

Tiktok | Instagram | Facebook | Transcriber
Extract accurate transcripts from Instagram Reels, Facebook Reels and TikTok videos. Use video URLs to transcribe public content with timestamps. Export transcripts in JSON format, run via API, schedule runs, or integrate with other tools for automated transcription workflows.
5.0 (2)
Pricing
$22.00 / 1,000 transcriptions
5
Total users
26
Monthly users
26
Runs succeeded
59%
Last modified
4 hours ago
You can access the Tiktok | Instagram | Facebook | Transcriber 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": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/sse?actors=tictechid/anoxvanzi-transcriber", "--header", "Authorization: Bearer <YOUR_API_TOKEN>" ] } }}
Configure MCP server with Tiktok | Instagram | Facebook | Transcriber
You have a few options for interacting with the MCP server:
Use
mcp.apify.com
viamcp-remote
from your local machine to connect and authenticate using OAuth or an API token (as shown in the JSON configuration above).Set up the connection directly in your MCP client UI by providing the URL
https://mcp.apify.com/sse?actors=tictechid/anoxvanzi-transcriber
along with an API token (or use OAuth).Connect to
mcp.apify.com
via Server-Sent Events (SSE), as shown below:
{ "mcpServers": { "apify": { "type": "sse", "url": "https://mcp.apify.com/sse?actors=tictechid/anoxvanzi-transcriber", "headers": { "Authorization": "Bearer <YOUR_API_TOKEN>" } } }}
You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other 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.