Amazon Trends API vs Signals
A side-by-side look at the Amazon Trends API and Signals MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Amazon Trends APIE-Commerce · Local subprocess (stdio)Amazon product search volume and best-seller trends. Free key at trendsapi.ai36FairAuth: not declaredS
SignalsE-CommercePay-per-call eCommerce competitive intel: competitor pricing, promotions, AI-readiness scores.41FairAuth: not declaredVerdict: choose Amazon Trends API for e-commerce work as a local process; choose Signals for e-commerce. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Amazon Trends API when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
TRENDSAPI_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Amazon Trends API | S Signals |
|---|---|---|
| Category | E-Commerce | E-Commerce |
| Quality signal | 36/100 · Fair | 41/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | TRENDSAPI_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | — |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Amazon Trends API | View Signals |
Tools & capabilities
Amazon Trends API tools
No tool names declared yet. Check the project README from the listing page.
Signals 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 API
{
"mcpServers": {
"amazon-trends-api-2": {
"command": "uvx",
"args": [
"trendsapi-amazon"
],
"env": {
"TRENDSAPI_KEY": "YOUR_TRENDSAPI_KEY_HERE"
}
}
}
}
Signals
No confirmed install command for Signals yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Amazon Trends API is categorized under E-Commerce and uses a local stdio subprocess. Signals belongs to E-Commerce and uses an install path we have not confirmed yet. Pick Amazon Trends API for e-commerce work and Signals 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. Signals has no confirmed install command yet — follow its own setup instructions.
Amazon Trends API has no declared pricing — check the project's own site. Signals 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-api-2 and signals-3 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Amazon Trends API has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Signals has 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.
