Twitter User Media Scraper

Try for free

Developed by

PowerAI

Fetch media content (photos and videos) from any Twitter user's timeline, with auto-pagination and detailed metadata. Supports up to your specified maxResults.

5.0 (1)

Pricing

$4.99 / 1,000 results

Total users

Monthly users

Runs succeeded

>99%

Last modified

8 days ago

Social media

Videos

You can access the Twitter User Media 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.

Python

JavaScript

CLI

OpenAPI

HTTP

MCP

{
    "mcpServers": {
        "local-actors-mcp-server": {
            "command": "npx",
            "args": [
                "-y",
                "@apify/actors-mcp-server",
                "--actors",
                "powerai/twitter-user-media-scraper"
            ],
            "env": {
                "APIFY_TOKEN": "<YOUR_API_TOKEN>"
            }
        }
    }
}

Configure MCP server with Twitter User Media 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/twitter-user-media-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.