Ecommerce Intelligence Mcp Server

io.github.TheNextGenNexusPublished by GitHub account TheNextGenNexusv1.0.1Updated Oct 24, 2026

Analyze Shopify stores, get product catalogs, pricing strategies, and store performance data

Overview

AI-generated overview

A local MCP server that lets an assistant analyze Shopify stores: product catalogs, pricing strategies, inventory and store performance, via Apify.

What you can do
Analyze a Shopify store's products and overall performance metrics, including inventory status for a store. Retrieve a store's full product catalog and examine its pricing strategy. Requests are forwarded from the local process to the nexgendata Apify endpoint and results are returned to the assistant.
When to use it
Useful when you want an assistant to research a Shopify storefront, compare product catalogs or pricing, or check inventory and performance signals without browsing the store manually.
Requirements
Runs locally over stdio, typically launched with npx or installed globally with npm, so Node.js is needed. An Apify API token is supplied through the APIFY_TOKEN environment variable; the README marks it optional, with a rate-limited public endpoint used without it. Network access to Apify is required.
Before you install
The APIFY_TOKEN secret is passed in the environment and grants access to Apify scraping actors; keep it out of shared configs. Store analysis requests and results are sent to the third-party Apify endpoint. The README's example package name differs from the manifest's package name, so verify which package you install.

Installation

In SourceWeft

  1. Open Ecommerce Intelligence Mcp Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

E-Commerce Intelligence MCP Server

Analyze Shopify stores, get product catalogs, pricing strategies, and store performance data — powered by nexgendata on Apify.

Quick Start

Using npx (recommended)

bash
npx @nexgendata/ecommerce-intelligence-mcp-server

Install globally

bash
npm install -g @nexgendata/ecommerce-intelligence-mcp-server

Configure with Claude Desktop

Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

json
{      "mcpServers": {            "ecommerce-intelligence-mcp-server": {                  "command": "npx",                  "args": [                        "-y",                        "@nexgendata/ecommerce-intelligence-mcp-server"                  ],                  "env": {                        "APIFY_TOKEN": "your-apify-token-optional"                  }            }      }}

Configure with Cline

Add the same configuration to your Cline MCP settings.

Available Tools

ToolDescription
analyze_shopify_storeAnalyze a Shopify store's products and performance
get_product_catalogGet the full product catalog from a Shopify store
analyze_pricing_strategyAnalyze pricing strategy of a store
get_inventory_statusCheck inventory status for a store
get_store_performanceGet performance metrics for a store

Environment Variables

VariableRequiredDescription
APIFY_TOKENNoYour Apify API token for authenticated access. Without it, the server uses the public endpoint (rate-limited).

How It Works

This MCP server acts as a local stdio bridge to the nexgendata Apify MCP endpoint. When you call a tool, it forwards the request to Apify and returns the results.

Links

License

MIT

Source: servers/ecommerce-intelligence-mcp-server/README.md at commit 57f2369

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.