Amazon Seller Intelligence Pro avatar
Amazon Seller Intelligence Pro

Pricing

$100.00/month + usage

Go to Store
Amazon Seller Intelligence Pro

Amazon Seller Intelligence Pro

Developed by

AutomateLab

AutomateLab

Maintained by Community

The #1 Investment-Grade Amazon Seller Intelligence Scraper - Extract comprehensive seller data from Amazon with advanced business analytics, risk assessment, and competitive intelligence. No Amazon API key required, instant access to Fortune 500-ready seller insights!

0.0 (0)

Pricing

$100.00/month + usage

0

Total users

1

Monthly users

1

Runs succeeded

>99%

Last modified

2 hours ago

You can access the Amazon Seller Intelligence Pro 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": {
"local-actors-mcp-server": {
"command": "npx",
"args": [
"-y",
"@apify/actors-mcp-server",
"--actors",
"red.cars/amazon-seller-intelligence-pro"
],
"env": {
"APIFY_TOKEN": "<YOUR_API_TOKEN>"
}
}
}
}

Configure MCP server with Amazon Seller Intelligence Pro

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=red.cars/amazon-seller-intelligence-pro",
"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.