
Twitter (X.com) Search Scraper
Pricing
$30.00/month + usage

Twitter (X.com) Search Scraper
Easily extract tweets from Twitter (X.com) search results with our powerful Twitter Search Scraper. Get full tweet data, including text, engagement, media, and user info. Export in JSON, CSV, Excel, or HTML—perfect for social media monitoring, market research, competitor analysis, and trend tracking
2.3 (9)
Pricing
$30.00/month + usage
75
Total users
4.8K
Monthly users
295
Runs succeeded
>99%
Issues response
11 hours
Last modified
2 months ago
You can access the Twitter (X.com) Search 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=web.harvester/easy-twitter-search-scraper", "--header", "Authorization: Bearer <YOUR_API_TOKEN>" ] } }}
Configure MCP server with Twitter (X.com) Search Scraper
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=web.harvester/easy-twitter-search-scraper
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=web.harvester/easy-twitter-search-scraper", "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.