Neonjelly vs Signals
A side-by-side look at the Neonjelly and Signals MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
SignalsE-CommercePay-per-call eCommerce competitive intel: competitor pricing, promotions, AI-readiness scores.41FairAuth: not declaredVerdict: choose Neonjelly for e-commerce work over a hosted endpoint; choose Signals for e-commerce. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Neonjelly when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S Signals | |
|---|---|---|
| Category | E-Commerce | E-Commerce |
| Quality signal | 37/100 · Fair | 41/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Remote HTTP/SSE | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing |
Tools & capabilities
Neonjelly 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.
Neonjelly
{
"mcpServers": {
"neonjelly": {
"url": "https://mcp.neonjelly.io"
}
}
}
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
Neonjelly is categorized under E-Commerce and uses a remote HTTP/SSE transport. Signals belongs to E-Commerce and uses an install path we have not confirmed yet. Pick Neonjelly 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.
Neonjelly 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 neonjelly and signals-3 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Neonjelly has a quality signal of 37/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.
