MerchantFlow vs Neonjelly
A side-by-side look at the MerchantFlow 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 MerchantFlow for e-commerce work over a hosted endpoint; choose Neonjelly for e-commerce over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MerchantFlow when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
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 | ||
|---|---|---|
| Category | E-Commerce | E-Commerce |
| Quality signal | 67/100 · Great | 37/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Verified | Community listing |
| GitHub stars | — | 0 |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View MerchantFlow | View Neonjelly |
Tools & capabilities
MerchantFlow tools
No tool names declared yet. Check the project README from the listing page.
Neonjelly 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.
MerchantFlow
{
"mcpServers": {
"merchantflow": {
"command": "npx",
"args": [
"-y",
"merchantflow"
]
}
}
}
Neonjelly
{
"mcpServers": {
"neonjelly": {
"url": "https://mcp.neonjelly.io"
}
}
}
Frequently asked questions
MerchantFlow is categorized under E-Commerce and uses a remote HTTP/SSE transport. Neonjelly belongs to E-Commerce and uses a remote HTTP/SSE transport. Pick MerchantFlow for e-commerce work and Neonjelly 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.
MerchantFlow has no declared pricing — check the project's own site. Auth: oauth 2.0. Neonjelly 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 merchantflow and neonjelly as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MerchantFlow has a quality signal of 67/100 (Great) with 3 views, 0 installs and 0 GitHub stars. Neonjelly has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.
