πŸ”πŸ›’ Wish Scraper (PPR) avatar
πŸ”πŸ›’ Wish Scraper (PPR)

Pricing

$1.50 / 1,000 products

Go to Store
πŸ”πŸ›’ Wish Scraper (PPR)

πŸ”πŸ›’ Wish Scraper (PPR)

Developed by

3x1t

3x1t

Maintained by Community

Simple listings scraper. Extract product data from Wish.com to track trends, monitor pricing, and analyze customer reviews. Get fast, customizable results for valuable e-commerce insights. Fast, cheap & reliable.

0.0 (0)

Pricing

$1.50 / 1,000 products

2

Total users

7

Monthly users

6

Runs succeeded

>99%

Last modified

a month ago

You can access the πŸ”πŸ›’ Wish Scraper (PPR) 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=3x1t/wish-scraper",
"--header",
"Authorization: Bearer <YOUR_API_TOKEN>"
]
}
}
}

Configure MCP server with πŸ”πŸ›’ Wish Scraper (PPR)

You have a few options for interacting with the MCP server:

  • Use mcp.apify.com via mcp-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=3x1t/wish-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=3x1t/wish-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.