Tiktok Comments Scraper avatar
Tiktok Comments Scraper

Pricing

$1.00 / 1,000 results

Go to Store
Tiktok Comments Scraper

Tiktok Comments Scraper

Developed by

Goldmine

Goldmine

Maintained by Community

Extract TikTok comments without limit. Extract valuable insights from TikTok comments at scale with our powerful, reliable, and easy-to-use scraping solution.

5.0 (1)

Pricing

$1.00 / 1,000 results

0

Total users

22

Monthly users

12

Runs succeeded

>99%

Issues response

18 hours

Last modified

2 months ago

You can access the Tiktok Comments Scraper 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=logical_scrapers/tiktok-comments-api",
"--header",
"Authorization: Bearer <YOUR_API_TOKEN>"
]
}
}
}

Configure MCP server with Tiktok Comments Scraper

You have a few options for interacting with the MCP server:

  • Use mcp.apify.com via mcp-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=logical_scrapers/tiktok-comments-api 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=logical_scrapers/tiktok-comments-api",
"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.