A side-by-side look at the MCP Ecommerce Platform Profiler and Neonjelly MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Ecommerce Platform Profiler for e-commerce work as a local process; choose Neonjelly for e-commerce over a hosted endpoint. You can also run both side by side in one mcpServers block.
APIFY_TOKEN.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | E-Commerce | E-Commerce |
| Quality signal | 43/100 · Fair | 37/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | APIFY_TOKEN | None listed |
| 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 | Not listed |
| Full listing | View MCP Ecommerce Platform Profiler | View Neonjelly |
No tool names declared yet. Check the project README from the listing page.
No tool names declared yet. Check the project README from the listing page.
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.
{
"mcpServers": {
"mcp-ecommerce-platform-profiler": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-ecommerce-platform-profiler"
],
"env": {
"APIFY_TOKEN": "YOUR_APIFY_TOKEN_HERE"
}
}
}
}
{
"mcpServers": {
"neonjelly": {
"url": "https://mcp.neonjelly.io"
}
}
}
