Temu MCP Server

Give your AI assistant live access to Temu. This Actor runs as a Model Context Protocol (MCP) server so agents like Claude, Cursor, ChatGPT and n8n can search Temu, fetch product detail and browse the product feed in real time — and it also works as a classic one-shot scraper.

Tools exposed to AI agents

Tool	What it does
temu_product_feed	Products from Temu's homepage/recommendation feed — title, price, market price, discount, image, sales, URL. Works without login.
temu_search_products	Keyword product search — same product fields, with sort options. Best-effort: Temu often walls search; results then come back empty with walled: true.
temu_product_detail	Full detail for a product ID/URL — price, images, SKU variants, seller, rating, reviews, description. Residential proxy recommended; falls back to SEO fields when gated.

Who uses this

• AI builders & agent developers — plug Temu product data into an assistant or workflow without writing a scraper or handling anti-bot.
• Dropshippers & analysts — ask your assistant to find products, compare prices and pull details conversationally.
• No-code automations — call the tools from n8n, Make or a custom agent.

Connect your MCP client

1. Start this Actor in Standby mode.

2. Point your MCP client at the standby URL with the /mcp path (Streamable HTTP transport):

   <ACTOR_STANDBY_URL>/mcp
   

3. Example Claude Desktop / Cursor config:

   {
       "mcpServers": {
           "temu": {
               "url": "https://<your-actor-standby-url>/mcp"
           }
       }
   }
   

Your agent will then see temu_product_feed, temu_search_products and temu_product_detail as callable tools.

Example agent prompts

• "Use Temu to find the 10 best-selling wireless earbuds and list their prices."
• "Get the full detail and variants for Temu product 601099651743804."
• "Show me 20 products from Temu's feed with their discounts."

Classic scraper mode

Prefer a one-shot run? Provide input and the Actor pushes rows to a dataset:

{ "mode": "search", "query": "wireless earbuds", "limit": 100 }

Modes: feed (default), search (needs query), detail (needs goodsIds).

Output fields

Product rows include goods_id, title, price, market_price, currency, discount_text, sales_tip, image and url. Detail results add images, skus, mall_name, rating, review_count and description.

FAQ

Do I need a Temu account or cookies? No — the server bootstraps its own session automatically.

Why are residential proxies recommended? Temu gates full product detail from low-reputation IPs; residential proxies give the best detail coverage (when gated, detail falls back to SEO fields). The product feed works without them.

Why does keyword search sometimes return nothing? Temu puts keyword search behind a login/captcha wall for guest sessions, and this can happen even on residential proxies, so search is best-effort. A walled search is reported — walled: true from the MCP tool, or a run status message and walled in the SUMMARY record in classic mode — rather than failing silently.

Which AI clients are supported? Any MCP-compatible client — Claude Desktop, Cursor, ChatGPT (MCP), n8n, and custom agents using the MCP SDK.

How is it billed? Per MCP tool call (plus a small start fee). See the Store listing for current pricing.