Skip to main content
Glama

Sell The Trend MCP πŸΎπŸ“Š

An MCP (Model Context Protocol) server that turns your Sell The Trend account into an AI-drivable product-research engine, and generates detailed, decision-ready PDF dossiers for any niche.

Sell The Trend has no public API, so this server drives your own logged-in account through a real browser (Playwright). It gives an AI assistant (Claude Code, etc.) generic browser primitives plus purpose-built research + reporting tools.

⚠️ Personal-use tool, your own paid account, your own data. Automating a SaaS dashboard can be against its Terms of Service. Use responsibly and at your own risk. Not affiliated with, or endorsed by, Sell The Trend.


✨ What it does

  • πŸ”Ž stt_research: search NEXUS for a niche/keyword β†’ structured product data (name, sell price, orders, sales).

  • πŸ“„ stt_research_report: research a keyword and generate a detailed PDF dossier: full product list + deep dossiers for the top products (cost, profit, saturation %, AI insights, competitor stores + revenue + URLs, AliExpress suppliers, Facebook Ad Library link, FB targeting, product image).

  • 🧭 Browser primitives (stt_navigate, stt_snapshot, stt_extract, stt_click, stt_fill, stt_evaluate, stt_screenshot): reach anything in your dashboard (ad finders, spy tools, store intel…).

  • πŸ” stt_login / stt_status: one-click human login (handles the "verify you are human" check) + session status.

Related MCP server: merch-connector

βœ… Requirements

  • Node.js 18+

  • A Sell The Trend account (free trial works)

  • Claude Code (or any MCP client)

πŸš€ Installation

git clone https://github.com/mfahadiqbalofcl/sellthetrend-mcp.git
cd sellthetrend-mcp
npm install
npx playwright install chromium      # one-time browser download
cp .env.example .env                 # then add YOUR Sell The Trend login (never commit it)

Open .env and set:

STT_EMAIL=you@example.com
STT_PASSWORD=your-password
STT_HEADLESS=false        # keep false, STT blocks headless logins

πŸ”Œ Register with Claude Code

claude mcp add sellthetrend -s user -- node /ABSOLUTE/PATH/TO/sellthetrend-mcp/server.mjs

Then restart Claude Code so the tools load. Verify: claude mcp list β†’ sellthetrend βœ” Connected.

πŸ”‘ First login (once per server start)

STT guards login with a Cloudflare "verify you are human" check that only a human can pass. So:

  1. In Claude, call stt_login (or just ask: "log into Sell The Trend").

  2. A browser window opens (email + password pre-filled). Tick "verify you are human" β†’ Sign in.

  3. The session is held by the running server and reused for every tool call.

(Standalone alternative when the server isn't running: node login.mjs.)

πŸ’‘ Usage examples (in Claude)

  • "Research the catnip niche on Sell The Trend and give me a detailed PDF report." β†’ drops a dossier in ./reports/.

  • "Find winning cat dental products with their cost, profit and saturation."

  • "Open the Facebook Ad finder and show me the top pet ads."

  • "Screenshot my NEXUS page."

Reports are saved to ./reports/winning-product-report-<keyword>-<timestamp>.pdf. Each has a summary table + per-product dossiers with embedded image, economics, AI insights, competitor stores (URLs + revenue), AliExpress suppliers, FB Ad Library link, and targeting.

βš™οΈ Configuration (.env)

Var

Purpose

STT_EMAIL / STT_PASSWORD

your login (pre-fills the form)

STT_HEADLESS

false recommended (headless logins are blocked)

STT_PROXY_SERVER / STT_PROXY_USERNAME / STT_PROXY_PASSWORD

optional residential proxy to avoid IP rate-limits

STT_DASHBOARD_URL / STT_SEARCH_PATH / STT_CARD_SELECTOR

optional overrides if STT changes its UI

🧰 Troubleshooting

  • "verify you are human" loops / logged out β†’ call stt_login again (session expired). Never kill -9 the browser. That discards the session.

  • Empty results β†’ STT changed selectors; use stt_navigate + stt_snapshot to find the new path and set overrides in .env.

  • IP blocked β†’ add a residential proxy via STT_PROXY_*.

πŸ“ Project layout

server.mjs      # the MCP server (14 tools)
report.mjs      # parser + detailed PDF report engine
login.mjs       # standalone one-time manual login
make_report.mjs # generate a report from sample data
smoke.mjs       # lists the tools (sanity check)
reports/        # generated PDFs (gitignored)

βš–οΈ Disclaimer

For personal research on your own account. Respect Sell The Trend's Terms of Service and robots policies. The author/operator is responsible for how it's used. MIT-licensed code; the data belongs to Sell The Trend and its sources.

Available Tools

14 tools
stt_clickB

Click an element by CSS selector or visible text.

Inputs: text, selector.

stt_evaluateA

Run JavaScript in the page and return the JSON-serializable result. The escape hatch for anything the other tools don't cover.

Inputs: script (required).

stt_extractB

Extract data from the current page via a CSS selector. Returns innerText (or a given attribute) of each match.

Inputs: selector (required), limit, attribute.

stt_fillC

Fill an input by CSS selector; optionally submit with Enter.

Inputs: value (required), selector (required), submit.

stt_loginA

Open Sell The Trend login in THIS server's browser window and wait (up to 5 min) for you to solve the human-check + sign in. Run once per server start if stt_status shows loggedIn:false. (Server must be headful: STT_HEADLESS=false.)

Inputs: no named parameters.

stt_navigateA

Log in if needed, navigate to a Sell The Trend path or full URL, and return a text snapshot (title, url, text, links, buttons).

Inputs: pathOrUrl (required).

stt_researchA

Search Sell The Trend NEXUS for a niche/keyword and return STRUCTURED product data (name, sell price, orders, sales). The reliable way to pull winning-product data.

Inputs: keyword (required).

stt_research_reportA

Research a niche/keyword on NEXUS and generate a DETAILED PDF dossier under ./reports/: full product list + deep dossiers (cost, profit, saturation, stores+URLs, suppliers, Facebook ad library, targeting, image) for the top products. Use this by default whenever researching a product.

Inputs: keyword (required), deepCount, recommendation.

stt_save_sessionA

Persist the current browser session after a manual login so future runs stay logged in.

Inputs: no named parameters.

stt_screenshotC

Take a PNG screenshot of the current page so you can see the dashboard.

Inputs: fullPage.

stt_search_productsB

Search Sell The Trend product research for a niche/keyword and return found product cards. Best-effort β€” if cards are empty, use stt_navigate + stt_snapshot to find the real path/selector and set STT_SEARCH_PATH / STT_CARD_SELECTOR in .env.

Inputs: query (required).

stt_snapshotA

Return a text snapshot of the CURRENT page (title, url, visible text, links, buttons).

Inputs: no named parameters.

stt_statusA

Report Sell The Trend session/auth status and whether you're logged in.

Inputs: no named parameters.

stt_winning_productsB

Open Sell The Trend winning/handpicked products and return a snapshot. Tune STT_WINNING_PATH in .env if the default isn't right.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 14 tools

    Disambiguation4/5

    Tools have mostly distinct purposes, but stt_research, stt_research_report, and stt_search_products overlap in searching products. Descriptions clarify differences (structured data vs. PDF vs. raw cards), so agents can differentiate.

    Naming Consistency5/5

    All tools use the 'stt_' prefix with consistent verb_noun snake_case (e.g., stt_click, stt_extract, stt_research_report). No mixed conventions or ambiguous names.

    Tool Count5/5

    14 tools is well-scoped for a platform automation server covering login, navigation, interaction, data extraction, research, and reporting. No excess or deficiency.

    Completeness4/5

    Covers major workflows: login, navigation, interaction, research, reporting. Minor gaps like logout or advanced filtering, but core user tasks are supported.

    Related MCP Connectors

    Related MCP Servers