Newegg Products avatar
Newegg Products

Under maintenance

Pricing

$5.00 / 1,000 products

Go to Store
Newegg Products

Newegg Products

Under maintenance

Developed by

Nine-Tail.Net

Nine-Tail.Net

Maintained by Community

Scrape and download product details from Newegg without using the official API. This actor extracts comprehensive product information, including reviews, prices, descriptions, images, manufacturer details, seller info, and more.

0.0 (0)

Pricing

$5.00 / 1,000 products

0

Total users

1

Monthly users

1

Last modified

19 hours ago

You can access the Newegg Products 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=nine-tail-net/newegg-products",
"--header",
"Authorization: Bearer <YOUR_API_TOKEN>"
]
}
}
}

Configure MCP server with Newegg Products

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=nine-tail-net/newegg-products 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=nine-tail-net/newegg-products",
"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.