Neonjelly MCP Server

by neonjelly Your server? Claim it

answering

Neonjelly is answering right now. Last checked 15 min ago. It exposes 60 tools. Last commit 4 Sep 2026.

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

Uptime history 15 days of history · worst day 79%

15 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

200 ms

Response time

average over 24h

Stars

last commit 4 Sep 2026

What changed 124

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 4 September 2026. No other catalogue keeps this.

4 Sep 60 tool descriptions were rewritten61 times that day assortment_watch, brief_market, change_tracker and 57 more

4 Sep 60 tools changed the parameters they ask for61 times that day assortment_watch, brief_market, change_tracker and 57 more

4 Sep a tool appeared upgrade

4 Sep a tool changed version

and 2 more, back to 4 September 2026

Nothing serious here today

Today is the operative word: we check Neonjelly every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp --transport http https://mcp.neonjelly.io/c/{connect_token}/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.neonjelly.io/c/{connect_token}/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.mcp]
url = "https://mcp.neonjelly.io/c/{connect_token}/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.neonjelly.io/c/{connect_token}/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.neonjelly.io/c/{connect_token}/mcp"
    }
  }
}

Available tools 60

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

signal

create_signal

Paid plans only (trial 403). Create a Signals watch on a competitor domain for ads, units, inventory, and social. Tight watch cap; meters the key. No probe, no scrape.

get_signal

Paid plans only (trial 403). Return one signal card. id is a Mongo id or a domain already on Signals.

get_signal_ads

Paid plans only (trial 403). Return the ad library or a slice (overview default). No probe — domain must already be on Signals.

get_signal_apps

Paid plans only (trial 403). Return apps observed on a tracked store. Set changes=true for app change history.

get_signal_insights

Paid plans only (trial 403). Return the insight feed for one watched domain. Prefer this over list_signal_insights.

get_signal_inventory

Paid plans only (trial 403). Return the stock timeline for a watched store. Domain must already be on Signals.

get_signal_product_changes

Paid plans only (trial 403). Return product movements on a tracked store. Catalog-wide SKU moves use get_product_changes.

get_signal_sales

Paid plans only (trial 403). Return daily units and variants. Needs ≥2 inventory snapshots on the watch — do not invent unit counts.

get_signal_social

Paid plans only (trial 403). Return follower snapshots for a watched store. Domain must already be on Signals.

get_signal_stats

Paid plans only (trial 403). Return totals plus store profile for a signal. Domain must already be on Signals.

list_signal_insights

Paid plans only (trial 403). Account-wide insight feed — often empty unless the key owns watches. Prefer get_signal_insights with a domain already on Signals.

product

get_product

Return one SKU by store domain plus Shopify handle. Use get_store_products or product_search when you do not yet have the handle.

get_product_changes

List price, new, removed, position, and bestseller SKU movements. Filter by storeDomain or productType; default noise floor is minPriceChangePct.

get_product_research

Return the saturation report for one product idea. Copy id from search_product_ideas or niche_research — do not invent seller counts.

list_product_sellers

List stores selling a product idea, sorted by traffic or price. Copy id from search_product_ideas — this is who-sells-this, not a single merchant SKU list.

product_intel

Build one SKU memo: card, discount vs compare-at, store, SKU change history, and store bestsellers. Pass domain+handle, or q to resolve first.

product_search

Search cross-store SKUs and return rows plus facets (vendors, types, stores, price band). At least one filter is required. For saturation / who-sells-this-idea, use niche_research.

search_product_ideas

Search product names/categories and return ideas with seller count, price, and UNTAPPED→SATURATED verdict — not one-store listings. Prefer niche_research when the user asks “is this saturated?”

store

get_store

Return one merchant card: traffic, modeled revenue, rating, apps, and socials. Call resolve_store first if you only have a brand name — missing domains stay not_found.

get_store_apps

List Shopify apps detected on one merchant. Use compare_stacks when the user wants shared vs exclusive apps across several domains.

get_store_changes

List observation diffs for one store: revenue, visits, products, rating, apps. For a mixed product+store board, prefer change_tracker.

get_store_history

Return daily snapshots: visits, revenue band, rating, and product counts, up to 365 days. Use for growth charts after get_store.

get_store_products

List SKUs for one merchant with price, vendor, type, and bestseller filters. Prefer this over global search_products when you already have a domain.

get_store_traffic

Return monthly visits and channel mix for one store. Use after get_store when the user asks how traffic is trending.

app

get_app

Return one Shopify app plus an install-base sample. Copy slug from search_apps, then get_app_stores for the merchant list.

get_app_stores

List merchants observed running a Shopify app, sorted by visits. Use for “who uses Klaviyo?” store lists — country filters live on search_stores, not here.

compare

compare_stacks

Compare 2–8 store app stacks: shared vs exclusive apps, tagged by role (email, support, reviews, subs, ads). Pass hostnames, not brand names.

compare_stores

Compare 2–8 store cards side by side (traffic, revenue band, apps, rating). Missing domains land in notFound — do not invent the missing rows.

analytics

get_analytics_overview

Return catalog coverage: store/SKU counts, averages, top verticals and countries. Quote these snapshot figures only — do not invent traffic totals.

apps

search_apps

Search the Shopify App Store catalog by name, category, pricing, or rating. Follow a slug with get_app_stores to see which merchants run it.

assortment

assortment_watch

List new and removed SKUs plus bestseller enter/exit. Filter by storeDomain or productType when the user names a shop or category.

brief

brief_market

Return a one-page TAM brief: vertical size, geos, movers, and an optional filtered cohort from 1.37M stores. Pass a vertical; quote catalog counts only — do not invent TAM.

change

change_tracker

Return a full change board: unified feed, all 8 product change types, 5 store change types, and Signals SKU changes if watched. Prefer this over calling each change tool separately.

changes

get_changes

Return the unified store + product movement feed. Prefer change_tracker when the user wants every change type on one board.

cohort

cohort_tam

Roll a filtered store cohort into a groupBy table (country, vertical, industry, category). This is not the unfiltered get_countries TAM — use that when no filters apply.

competitor

competitor_moves

List catalog store and SKU changes plus vertical movers for one competitor domain. Ads and daily units need a paid Signals watch — do not offer create_signal on trial.

contacts

get_contacts

Return emails, social URLs, and ESP/support app tells for one store. No phone or owner names in this catalog — pass domain or q.

countries

get_countries

Return unfiltered geo TAM (store counts by country). Pass vertical to slice one market; a filtered cohort belongs on search_stores groupBy=country.

diligence

diligence_pack

Build an IC memo for one domain: card, growth, traffic, stack roles, bestsellers, changes, and contacts. Includes Signals stats only if that domain is already watched.

examples

get_examples

Same playbook map as list_playbooks (VC, competitor, dropship, outreach). Prefer list_playbooks on new sessions.

movers

get_movers

List stores growing or shrinking on visits or modeled revenue. Defaults: metric/direction any, minPct 5. Quote catalog movers only.

niche

niche_research

Run semantic product-idea search plus a saturation report and the stores that sell the top hit. q is a product name or category, not a domain — quote seller count and the UNTAPPED→SATURATED verdict.

outreach

find_outreach

Filter the 1.37M-store catalog, hydrate each row, and keep stores that have an email or Instagram. Caps at 10 (each costs a call) — country is a filter, not a login region.

overlap

overlap_vendors

Find product-vendor overlap and the average price gap between two stores. Use after compare_stacks when you need shared suppliers, not shared apps.

peers

find_peers

Find stores in the same vertical, country, and visit band as a target domain, then compare cards. Call resolve_store first if you only have a brand name.

playbooks

list_playbooks

List composed-tool playbooks by job: store lists, VC, competitor, dropship, outreach, merch. Start here when the user has not named a tool — then call the playbook's first tool.

price

price_watch

List price decreases and increases across stores or one merchant. Default minPriceChangePct is 10 — raise it to cut noise.

products

search_products

Search SKUs across the 368.9M-product catalog. At least one filter is required. For saturation or who-sells-this-idea, use niche_research.

resolve

resolve_store

Resolve a brand name or URL against 1.37M Shopify storefronts and return up to 5 candidates. On a single hit, also return the full store card — call this before inventing a domain; missing stores stay not_found.

screen

screen_dropship

List dropship-flagged stores in a vertical/geo plus their cheapest SKUs. Country is a filter, not a login region — quote the catalog flag, do not invent supplier names.

signals

list_signals

Paid plans only (trial 403). List Signals watches stored on this Neonjelly key. Then GET a domain that is already on Signals — do not advertise this on trial.

source

source_map

Group a SKU search by vendor: store count and price min/max across the catalog. Use for sourcing or arbitrage after niche_research names the product.

stores

search_stores

Filter 1.37M Shopify stores into a list (emails/socials live on the card) or roll them up with groupBy. Without groupBy you get store cards; with groupBy you get breakdown rows, not stores. Country is a filter, not a login region.

suggest

suggest_product_ideas

Autocomplete product-idea names as the user types. Follow with search_product_ideas or niche_research on the chosen row.

trending

trending_product_ideas

List product ideas the catalog marks as heating up. Pair a hit with get_product_research and list_product_sellers — do not invent trend scores.

upgrade

upgrade

Return the paid upgrade URL when trial expired, daily quota is 0, or Signals is blocked. Does not count against quota. Always show the returned URL — never invent a checkout link.

upstream

get_upstream_health

Return catalog health JSON and whether auth is required. Use when a lookup fails unexpectedly — not for store research.

verticals

get_verticals

Return market size by vertical (store counts and averages). Pass countryCode to slice one geo — for a filtered cohort, use search_stores with groupBy=vertical.

whoami

whoami

Return this key's plan, used today, remaining quota, rate limit, and expiry. Does not count against daily quota — call first when the user asks “what's my quota?” If remaining is 0 or trial expired, call upgrade and open the URL.

winning

winning_skus

List bestsellers, ≥10% markdowns, and new products for a vertical or one store. Require storeVertical or storeDomain — do not call empty.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.neonjelly.io/c/{connect_token}/mcp	streamable-http	answering	297 ms	15 min ago

Alternatives to Neonjelly

same job, measured the same way

Shopify Catalog Monitor

by dizzyvinci

Track price drops, stock-outs, restocks, and new/removed products across Shopify stores.

answering

ReplenishRadar

by replenishradar

Shopify + Amazon inventory planning, forecasting & replenishment over MCP (50 tools).

80 installs/wk local only

CartScout

by veselin15

Live product prices, stock, variants and deal ratings from Shopify, Walmart, eBay and more.

local only

Commercebridge

by isaiahdupree

Remote MCP connector for eBay, Shopify, Best Buy & Etsy marketplace data via the Commerce API

14 tools answering

Shopify Store Builder MCP

by nazariinalyvaikobs

MCP server for building Shopify stores via the Admin GraphQL API: themes, pages, and navigation

31 installs/wk local only

Shopify Admin MCP

by a1-x-tech

MCP server for the Shopify Admin API: products, orders, customers, inventory, discounts.

61 installs/wk local only

Agentstorefront

by lmaniraruta

MCP for AgentStorefront — discover, price, and subscribe to paid agent services.

30 installs/wk local only

Storesignal

by anthesiallc

Shopify store intelligence: apps, tech stack, CDN, and market data over a 19K-store corpus.

45 installs/wk local only

Neonjelly — questions

Answers built from our own checks of this server.

What can Neonjelly do?

It exposes 60 tools, read directly from the server on our last check. Among them: assortment_watch, brief_market, change_tracker, cohort_tam, compare_stacks, compare_stores and 54 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Neonjelly mostly used for?

Its tools cluster around signal, product and store. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Neonjelly working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 200 ms. The bar chart above shows every period we have measured.

How do I connect Neonjelly?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Neonjelly need an API key?

No. Neonjelly completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 60 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Neonjelly?

It answers our handshake in 200 ms on average, which is faster than 66% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Neonjelly open source?

We cannot say either way: 0 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.