Amazon Trends API vs Profitlee MCP
A side-by-side look at the Amazon Trends API and Profitlee MCP 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 declaredVerdict: choose Amazon Trends API for e-commerce work as a local process; choose Profitlee MCP 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 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.
Choose Profitlee MCP when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PROFITLEE_API_TOKEN, PROFITLEE_BASE_URL. - You want tools like
calculate_profit, list_scenarios, get_scenario.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Amazon Trends API | |
|---|---|---|
| Category | E-Commerce | E-Commerce |
| Quality signal | 36/100 · Fair | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | TRENDSAPI_KEY | PROFITLEE_API_TOKENPROFITLEE_BASE_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 7 |
| Full listing | View Amazon Trends API | View Profitlee MCP |
Tools & capabilities
Amazon Trends API tools
No tool names declared yet. Check the project README from the listing page.
Profitlee MCP tools 7
calculate_profitFull per-unit cost stack, gross/net margin, and monthly P&L.list_scenariosList your saved scenarios.get_scenarioRead one scenario (inputs + outputs) by id.save_scenarioSave a named scenario from calculator inputs.update_scenarioRename and/or replace a scenario's inputs.delete_scenarioDelete a scenario by id.copy_scenarioDuplicate a scenario into a new one ("Copy of …").
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"
}
}
}
}
Profitlee MCP
{
"mcpServers": {
"profitlee-mcp": {
"command": "npx",
"args": [
"-y",
"profitlee-mcp"
],
"env": {
"PROFITLEE_API_TOKEN": "YOUR_PROFITLEE_API_TOKEN_HERE",
"PROFITLEE_BASE_URL": "YOUR_PROFITLEE_BASE_URL_HERE"
}
}
}
}
Frequently asked questions
Amazon Trends API is categorized under E-Commerce and uses a local stdio subprocess. Profitlee MCP belongs to E-Commerce and uses a local stdio subprocess. Pick Amazon Trends API for e-commerce work and Profitlee MCP 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 API has no declared pricing — check the project's own site. Profitlee MCP 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 profitlee-mcp 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. Profitlee MCP has 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars.
