Lumnix MCP Server

Lumnix MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. E-commerce research via MCP. Amazon, Alibaba & AliExpress product search and FBA margins.

What you get

Stop paying for three different SaaS dashboards. Ask your AI to find winning products, vet suppliers, and calculate margins — all in one conversation.

What the assistant can call

Once Lumnix is connected, these are the calls the assistant has available:

• amazon_search_products — Search by keyword with price, rating, and review filters
• amazon_get_product_details — Full product page — features, specs, reviews, images, category
• amazon_estimate_sales — Monthly sales volume with confidence range
• amazon_opportunity_score — ⭐ 0-100 niche score — demand, competition, margin potential
• amazon_analyze_competition — Top players, review counts, price ranges for a keyword
• amazon_best_sellers — Best-selling products by category with sales data
• amazon_keyword_suggestions — Amazon autocomplete keywords with search frequency
• amazon_price_history — 📊 Keepa-powered — historical price chart
• amazon_bsr_history — 📊 Keepa-powered — Best Sellers Rank trend over time
• amazon_analyze_negative_reviews — Complaint categories, sentiment breakdown, common issues
• amazon_analyze_listing_quality — CTR + CVR scoring with specific improvement suggestions
• alibaba_search_products — Search suppliers and products with MOQ and price filters

Setting it up

lumnix on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration and credentials

You will need one environment variable: YOUR_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

Among the payments and commerce options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Lumnix's toolset — amazon_search_products, amazon_get_product_details, amazon_estimate_sales and 11 more — is a fair guide to whether it matches your workflow. It is maintained by moltstudios; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Lumnix.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the lumnix mcp server does with a few real requests.