Fetch Single Tweet/X Post (Last update: November 2024)
Deprecated
Pricing
$19.90/month + usage
Fetch Single Tweet/X Post (Last update: November 2024)
Deprecated
Fetch Single Tweet/X Post helps you retrieve any specific Tweet without restrictions or rate limits, and returns live data.
0.0 (0)
Pricing
$19.90/month + usage
2
Total users
31
Monthly users
2
Last modified
8 months ago
You can access the Fetch Single Tweet/X Post (Last update: November 2024) 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=yeyo/single-tweet-scraper", "--header", "Authorization: Bearer <YOUR_API_TOKEN>" ] } }}Configure MCP server with Fetch Single Tweet/X Post
You have a few options for interacting with the MCP server:
Use
mcp.apify.comviamcp-remotefrom 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=yeyo/single-tweet-scraperalong with an API token (or use OAuth).Connect to
mcp.apify.comvia Server-Sent Events (SSE), as shown below:
{ "mcpServers": { "apify": { "type": "sse", "url": "https://mcp.apify.com/sse?actors=yeyo/single-tweet-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.
