TikTok User Followers Scraper avatar
TikTok User Followers Scraper

Pricing

$4.99 / 1,000 results

Go to Store
TikTok User Followers Scraper

TikTok User Followers Scraper

Developed by

PowerAI

PowerAI

Maintained by Community

Extract detailed TikTok user followers list with comprehensive profile data including engagement metrics, account information, and social media links. Perfect for audience analysis, influencer research, and social network mapping. Supports pagination for large-scale data collection.

0.0 (0)

Pricing

$4.99 / 1,000 results

1

Total users

13

Monthly users

13

Runs succeeded

97%

Last modified

25 days ago

You can access the TikTok User Followers 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": {
"local-actors-mcp-server": {
"command": "npx",
"args": [
"-y",
"@apify/actors-mcp-server",
"--actors",
"powerai/tiktok-user-followers-scraper"
],
"env": {
"APIFY_TOKEN": "<YOUR_API_TOKEN>"
}
}
}
}

Configure MCP server with TikTok User Followers Scraper

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=powerai/tiktok-user-followers-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.