Skool Members Scraper avatar
Skool Members Scraper

Pricing

$15.00/month + usage

Go to Store
Skool Members Scraper

Skool Members Scraper

Developed by

Muhamed Didovic

Muhamed Didovic

Maintained by Community

Boost your business leads with our Skool.com Groups' Members/Users Scraper. Gather user details like names, emails, and social media links (Facebook, Instagram, LinkedIn, Twitter, etc.). It is ideal for market research, competitor analysis, and lead generation. Save time with our advanced scraper.

1.0 (1)

Pricing

$15.00/month + usage

4

Total users

77

Monthly users

16

Runs succeeded

>99%

Issues response

0.4 hours

Last modified

2 months ago

You can access the Skool Members 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",
"memo23/skool-members-scraper-rent"
],
"env": {
"APIFY_TOKEN": "<YOUR_API_TOKEN>"
}
}
}
}

Configure MCP server with Skool Members 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=memo23/skool-members-scraper-rent",
"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.