Amazon POE MCP Server
Extracts data from Amazon's Product Opportunity Explorer in Seller Central via browser automation, enabling niche search and CSV export of search terms, products, customer reviews, returns, and insights using natural language.
README
Amazon POE MCP Server
MCP server that extracts data from Amazon's Product Opportunity Explorer (Seller Central) via browser automation. POE data is not available through the Selling Partner API — this tool automates the UI directly.
How it works
Claude Code / MCP Client
│ (stdio)
▼
MCP Server (FastMCP)
│ (Playwright CDP)
▼
Chrome Browser (with active Seller Central session)
│
▼
Amazon Product Opportunity Explorer
The server connects to an already-open Chrome browser via Chrome DevTools Protocol (CDP), navigates the POE interface, and extracts data — either via Amazon's Download button or by scraping HTML tables.
Setup
1. Install dependencies
cd amazon-poe-mcp
uv sync
uv run playwright install chromium
2. Launch Chrome with remote debugging
Important: You must kill ALL Chrome instances first, then relaunch. If Chrome is already running, the debug flag is silently ignored.
# Kill existing Chrome
pkill -9 -f "Google Chrome"
sleep 2
# Launch with CDP enabled (temp profile)
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome \
--remote-debugging-port=9222 \
--user-data-dir=/tmp/chrome-debug-profile
3. Log into Seller Central
Navigate to sellercentral.amazon.es (or your marketplace) in the Chrome window that just opened and log in manually.
4. Configure Claude Code
The project includes a .mcp.json file. When you open a Claude Code session from this directory, the amazon-poe tools will be available automatically.
If you need to create it manually:
{
"mcpServers": {
"amazon-poe": {
"command": "uv",
"args": [
"--directory",
"/Users/arnauaumedes/Code/amazon-poe-mcp",
"run",
"src/amazon_poe_mcp/server.py"
]
}
}
}
Quick start: example extraction
1. Launch Chrome with CDP
cd ~/Code/amazon-poe-mcp
./start-chrome.sh
Chrome opens. Navigate to sellercentral.amazon.es and log in.
2. Open Claude Code from the project
cd ~/Code/amazon-poe-mcp
claude
Claude Code detects .mcp.json and loads the 7 amazon-poe tools automatically.
3. Ask for what you need in natural language
Search niches:
"Busca niches de 'magnesio' en el POE de España"
Claude calls search_niche(keyword="magnesio") and returns a table with ~25 niches, volumes, prices, growth, etc.
Export data from a specific niche:
"Exporta los search terms y productos del niche 'magnesium glycinate'"
Claude uses the niche URL (from the previous step) and calls export_search_terms + export_products. CSVs appear in output/.
Export everything at once:
"Exporta todos los datos del niche de magnesium glycinate"
Claude calls export_all — downloads search terms, products, customer reviews, returns and insights in one go.
4. Collect the CSVs
output/
├── magnesium_glycinate_search_terms_2026-03-02.csv
├── magnesium_glycinate_products_2026-03-02.csv
├── magnesium_glycinate_customer_reviews_2026-03-02.csv
└── magnesium_glycinate_returns_2026-03-02.csv
Visual flow
You: ./start-chrome.sh → log into Seller Central
│
You: claude (from ~/Code/amazon-poe-mcp)
│
You: "busca niches de creatina"
│
Claude: calls search_niche("creatina") → shows niche table
│
You: "exporta todo del primer niche"
│
Claude: calls export_all(niche_url) → 4 CSVs in output/
│
You: open CSVs in Excel / analyze with Claude
You talk in natural language, Claude decides which tool to call, and the browser moves on its own in the background.
MCP Tools
| Tool | Description | Output |
|---|---|---|
search_niche(keyword, marketplace?) |
Search POE for a keyword, returns matching niches with metrics | JSON |
export_search_terms(niche_url, output_filename?) |
Export "Search terms" tab | CSV |
export_products(niche_url, output_filename?) |
Export "Products" tab | CSV |
export_customer_reviews(niche_url, output_filename?) |
Export "Customer Review Insights" tab | CSV |
export_returns(niche_url, output_filename?) |
Export "Returns" tab | CSV |
export_insights_and_trends(niche_url) |
Extract "Insights and trends" summary | JSON |
export_all(niche_url, prefix?) |
Export all tabs in one call | JSON + CSVs |
Typical workflow
search_niche("magnesio")→ get list of niches with URLs- Pick a niche URL from results
export_all(niche_url, prefix="magnesio_glicinato")→ exports all tabs tooutput/
Output
CSV files are saved to ./output/ with the naming convention:
{keyword}_{tab_name}_{YYYY-MM-DD}.csv
Example: magnesium_glycinate_search_terms_2026-03-02.csv
Supported marketplaces
| Marketplace | Base URL |
|---|---|
| Spain (default) | sellercentral.amazon.es |
| United States | sellercentral.amazon.com |
Testing
# Unit tests
uv run pytest tests/ -v
# Manual integration test (requires Chrome + Seller Central session)
uv run python -c "
import asyncio
from amazon_poe_mcp.browser import BrowserManager
from amazon_poe_mcp.scraper import search_niche_in_poe
async def test():
mgr = BrowserManager()
await mgr.connect()
page = await mgr.get_page()
niches = await search_niche_in_poe(page, 'magnesio', 'Spain')
print(f'Found {len(niches)} niches')
for n in niches[:3]:
print(f' {n.niche_name} | vol:{n.search_volume}')
await page.close()
await mgr.disconnect()
asyncio.run(test())
"
Troubleshooting
| Problem | Solution |
|---|---|
ConnectionError: Could not connect to Chrome |
Chrome not running with --remote-debugging-port=9222. Kill all instances and relaunch. |
| CDP port not binding | Chrome was already running when you added the flag. Must kill ALL instances first (pkill -9 -f "Google Chrome"). |
PermissionError: not logged in |
Navigate to Seller Central in the debug Chrome and log in manually. |
| Selectors not finding elements | Amazon updates their UI periodically. Check scraper.py selectors against current POE HTML. |
| Download button fails | Falls back to HTML table scraping automatically. |
Project structure
amazon-poe-mcp/
├── pyproject.toml
├── .mcp.json # Claude Code MCP config
├── src/amazon_poe_mcp/
│ ├── server.py # MCP tool definitions (FastMCP)
│ ├── browser.py # Chrome CDP connection manager
│ ├── scraper.py # POE navigation + data extraction
│ └── models.py # Data models + marketplace constants
├── tests/
│ ├── test_models.py
│ ├── test_browser.py
│ └── test_scraper.py
└── output/ # Exported CSVs
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。