Neonjelly vs Shopops MCP
A side-by-side look at the Neonjelly and Shopops MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Neonjelly for e-commerce work over a hosted endpoint; choose Shopops 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 Neonjelly when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a remote HTTP/SSE transport.
Choose Shopops MCP when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a local stdio subprocess transport.
- You want tools like
store_connect, store_demo_seed, inventory_status.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | E-Commerce | E-Commerce |
| Quality signal | 37/100 · Fair | 49/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 | 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.
Shopops MCP tools 12
store_connectConnects, lists, disconnects, or syncs a Shopify/WooCommerce store (`action: "connect" \store_demo_seedCreates a realistic demo store (20 products, 40 customers, 150+ orders) so you can explore every tool without real store credentials.inventory_statusReturns current stock levels, back-order flags and low-stock alerts.inventory_forecastProjects future inventory requirements using moving-average demand and safety-stock buffers.pricing_analyzeGenerates a price elasticity report and identifies under-/over-priced SKUs.pricing_optimizeSuggests optimal price points based on margin analysis, sales velocity, and configurable pricing rules.customers_segmentPerforms RFM analysis and assigns customers to one of seven segments.customers_churnScores customers for churn risk and provides retention recommendations.order_anomaliesDetects potentially fraudulent or erroneous orders using pattern-recognition models.product_performanceConducts ABC analysis and returns contribution metrics per product class.report_dailyGenerates a JSON/CSV daily operations summary (sales, inventory, alerts).report_weeklyGenerates a weekly performance report with trend visualisations.
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"
}
}
}
Shopops MCP
{
"mcpServers": {
"shopops-mcp": {
"command": "npx",
"args": [
"-y",
"shopops-mcp"
]
}
}
}
Frequently asked questions
Neonjelly is categorized under E-Commerce and uses a remote HTTP/SSE transport. Shopops MCP belongs to E-Commerce and uses a local stdio subprocess. Pick Neonjelly for e-commerce work and Shopops 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.
Neonjelly has no declared pricing — check the project's own site. Shopops 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 neonjelly and shopops-mcp 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. Shopops MCP has 49/100 (Fair) with 0 views, 0 installs and 1 GitHub stars.
