# Neonjelly [Health: Active]

**Category:** 🛒 E-Commerce  
**Repository:** https://github.com/germanas/neonjelly-mcp-public  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/neonjelly

## Description
Remote MCP over 1.37M Shopify stores. 14-day trial, 100/day, no account. Paid from $29/mo.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "neonjelly": {
    "url": "https://mcp.neonjelly.io"
  }
}
```

## Documentation

## What Neonjelly MCP server does

Neonjelly MCP server provides ecommerce research tools over a remote Streamable HTTP MCP connection. Its data covers 1.37 million Shopify stores and 368.9 million SKUs. The tool groups support several research workflows: finding stores and contacts, inspecting an individual store, comparing competitors, researching product niches, mapping suppliers, and preparing market or investment analysis.

For store discovery, `search_stores`, `find_outreach`, `get_contacts`, and `get_app_stores` support list-oriented research. A known or suspected store can be handled with `resolve_store`, followed by tools such as `get_store`, `get_store_traffic`, `get_store_products`, `get_store_apps`, `get_store_history`, and `get_store_changes`. `compare_stores` supports side-by-side analysis. When the input is a brand name, the documented workflow is to resolve the store before assuming a domain.

The server also includes tools for market and competitive analysis. These include `brief_market`, `cohort_tam`, `find_peers`, `diligence_pack`, `compare_stacks`, `competitor_moves`, and `overlap_vendors`. Dropshipping workflows use `screen_dropship`, `source_map`, and `winning_skus`. Merchandising research includes `niche_research`, `search_product_ideas`, `product_search`, `change_tracker`, and `price_watch`.

## How it works

Authentication is tied to a generated identity key rather than a user account. Start at the Neonjelly website to mint a trial key or obtain a paid key. The service returns a connect URL in this form:

`https://mcp.neonjelly.io/c/<njc_…>/mcp`

That URL can be added directly to a compatible MCP client. Alternatively, the base endpoint at `https://mcp.neonjelly.io/mcp` accepts an `Authorization: Bearer nj_…` header or an `X-Api-Key` header.

The service exposes playbooks and guidance through `list_playbooks` and `get_examples`. The documented starting points include `lookup-store`, `store-list-emails`, `product-saturation`, `competitor-moves`, and `market-brief`. Resources are available at `neonjelly://instructions`, `neonjelly://start`, and `neonjelly://catalog`.

## Setup and configuration

Open the Neonjelly start page, create a trial or use a paid key, and copy the resulting MCP URL into Cursor, Claude, VS Code, or Windsurf. The trial lasts 14 days and allows 100 requests per day with a 20-per-minute limit.

The `whoami` tool reports the current plan and quota without consuming metered usage. `upgrade` handles the account upgrade flow. Paid access is required for signal tools: `create_signal` and the related `get_signal_*` tools return HTTP 403 during the trial.

## Limitations and notes

Results should be treated as data returned by the service, not as values to fill in by inference. The usage guidance specifically says not to invent sales or traffic numbers. If a store cannot be found, the expected result is `not_found`.

Neonjelly MCP server is remote, so client configuration requires a network-accessible MCP endpoint and a valid identity key. The public material also does not specify a software license.

_Full upstream README: https://allmcps.com/mcp/neonjelly/readme_