Twitter/X Community Tweets Scraper |$0.35/1K| Pay-Per Result
Pricing
$0.35 / 1,000 results
Twitter/X Community Tweets Scraper |$0.35/1K| Pay-Per Result
Extract tweets from any Twitter/X Community effortlessly with this high-speed scraper. Whether you’re monitoring niche discussions, tracking influencers, or conducting community-based research, this tool delivers accurate results—without needing the Twitter API or developer credentials.
0.0 (0)
Pricing
$0.35 / 1,000 results
0
Total users
1
Monthly users
1
Runs succeeded
>99%
Last modified
2 days ago
You can access the Twitter/X Community Tweets Scraper |$0.35/1K| Pay-Per Result 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", "fastcrawler/twitter-x-community-tweets-scraper-0-35-1k-pay-per-result" ], "env": { "APIFY_TOKEN": "<YOUR_API_TOKEN>" } } }}Configure MCP server with Twitter/X Community Tweets Scraper |$0.35/1K| Pay-Per Result
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=fastcrawler/twitter-x-community-tweets-scraper-0-35-1k-pay-per-result", "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.
