Neonjelly logo

Neonjelly

Researches Shopify stores, products, competitors, suppliers, market niches, traffic, and ecommerce signals through remote MCP.

Install Neonjelly

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
Server URL
https://mcp.neonjelly.io

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Overview

Neonjelly MCP server gives AI agents remote access to ecommerce intelligence across 1.37 million Shopify stores and 368.9 million SKUs. It uses a Streamable HTTP MCP endpoint authenticated with a trial or paid key, either in a generated connect URL or through bearer authentication. Use it to investigate stores, products, competitors, suppliers, market niches, and store changes. Reach for it when an agent needs Shopify market research rather than access to a single store account.

Use cases

  • Find Shopify stores for outreach
  • Investigate a brand’s store traffic and products
  • Measure product niche saturation
  • Compare competitor technology stacks
  • Map suppliers and dropshipping opportunities

Key features

  • Searches 1.37M Shopify stores
  • Inspects store traffic, products, apps, history, and changes
  • Researches niches, products, pricing, and market signals
  • Compares competitors and identifies overlapping vendors
  • Supports supplier and dropshipping analysis
  • Connects through remote Streamable HTTP MCP

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

6/6 checks healthy over the last 45d

How Neonjelly works

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.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Neonjelly

Neonjelly is an MCP server that connects AI agents to ecommerce intelligence across 1.37 million Shopify stores and 368.9 million SKUs. Its main tools search stores, inspect traffic and products, compare competitors, research niches, map suppliers, track changes, and prepare market analysis through a remote Streamable HTTP endpoint.

You do not install it locally; create a trial or paid key at the Neonjelly start page and paste the generated MCP URL into your client. The service also accepts bearer or X-Api-Key authentication at its base MCP endpoint.

Yes, Neonjelly works with Cursor through its generated remote MCP connect URL. The README also names Claude, VS Code, and Windsurf as compatible clients for the same URL-based connection.

It requires an identity key from a trial or paid plan. You can use the generated connect URL, or send the key to the base endpoint with an Authorization Bearer header or an X-Api-Key header.

No, signal tools require paid access.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewNeonjelly AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/neonjelly?style=directory)](https://allmcps.com/mcp/neonjelly)
HTML Embed
<a href="https://allmcps.com/mcp/neonjelly"><img src="https://allmcps.com/api/badge/neonjelly?style=directory" alt="Neonjelly on AllMCPs" /></a>