Amazon Trends MCP vs Catalog Cli Pro
A side-by-side look at the Amazon Trends MCP and Catalog Cli Pro MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Amazon Trends MCPE-Commerce · Remote HTTP/SSEAmazon product search demand over time, with growth for any keyword. Free key at trendsmcp.ai48FairAuth: not declaredVerdict: choose Amazon Trends MCP for e-commerce work over a hosted endpoint; choose Catalog Cli Pro for e-commerce as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Amazon Trends MCP when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
TRENDSMCP_API_KEY. - You want tools like
get_time_series, get_growth, get_top_trends.
Choose Catalog Cli Pro when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Amazon Trends MCP | |
|---|---|---|
| Category | E-Commerce | E-Commerce |
| Quality signal | 48/100 · Fair | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | TRENDSMCP_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 16 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View Amazon Trends MCP | View Catalog Cli Pro |
Tools & capabilities
Amazon Trends MCP tools 3
get_time_seriesWeekly (or daily) history for **one** `source` + `keyword`. Same name on MCP and REST (`mode: "get_time_series"`). REST also accepts `get_trends` as an alias.get_growthPoint-to-point percent change. Several windows in one call still count as **one** request for that source + keyword.get_top_trendsLive ranked list. **No keyword.** On MCP, `type` is required and must match the feed name **exactly** (including capitals). On REST, omit `type` only if you intend to pull every feed (billed per feed).
Catalog Cli Pro tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Amazon Trends MCP
{
"mcpServers": {
"amazon-trends-mcp-3": {
"url": "https://api.trendsmcp.ai/mcp"
}
}
}
Catalog Cli Pro
{
"mcpServers": {
"catalog-cli-pro": {
"command": "uvx",
"args": [
"amazon-catalog-cli"
]
}
}
}
Frequently asked questions
Amazon Trends MCP is categorized under E-Commerce and uses a remote HTTP/SSE transport. Catalog Cli Pro belongs to E-Commerce and uses a local stdio subprocess. Pick Amazon Trends MCP for e-commerce work and Catalog Cli Pro for e-commerce.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Amazon Trends MCP has no declared pricing — check the project's own site. Catalog Cli Pro has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add amazon-trends-mcp-3 and catalog-cli-pro as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Amazon Trends MCP has a quality signal of 48/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Catalog Cli Pro has 40/100 (Fair) with 0 views, 0 installs and 16 GitHub stars.
