How do I obtain the Access Token required for authentication?

You must complete the OAuth 2.0 authorization flow using your App Key through your specific seller account on the Temu Open Platform. The flow will generate an Access Token that grants scoped permissions to your store's order, inventory, and logistics data.

Can I manage inventory across multiple SKU variants simultaneously?

Yes! The `sync_inventory` tool accepts batch SKU updates. You can push quantity changes for multiple product variants in a single call, and the engine handles all MD5 signature computation and parameter encoding automatically.

Is there any risk of accidentally modifying live product listings or canceling orders?

All write operations require explicit parameters — order IDs, SKU identifiers, tracking numbers — that must be deliberately specified. The Access Token is scoped to your seller account, and the MD5 signature layer prevents request forgery. Critical actions like order cancellation are logged and require confirmation parameters.

Temu Seller Hub MCP Server for CrewAI 12 tools — connect in under 2 minutes

Name: Temu Seller Hub
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 12 Tools Framework

Connect your CrewAI agents to Temu Seller Hub through Vinkius, pass the Edge URL in the `mcps` parameter and every Temu Seller Hub tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Temu Seller Hub Specialist",
    goal="Help users interact with Temu Seller Hub effectively",
    backstory=(
        "You are an expert at leveraging Temu Seller Hub tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Temu Seller Hub "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 12 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Temu Seller Hub MCP Server

Bridge your AI agents directly into the Temu Open Platform, Pinduoduo's global cross-border marketplace processing millions of orders daily. Automate the complete supply-chain lifecycle without navigating complex seller consoles.

When paired with CrewAI, Temu Seller Hub becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Temu Seller Hub tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Order Management — List incoming orders from global buyers, retrieve full line-item details, and monitor payment status dynamically
Fulfillment & Logistics — Query valid shipping carriers, mark orders as shipped with tracking numbers, and monitor delivery milestones
Inventory Sync — Automate stock quantity updates across SKUs preventing overselling and stockout situations
Product Catalog — Pull published product listings and detailed goods specifications for auditing and optimization
Returns Handling — Track incoming RMA requests, query refund states, and manage reverse logistics efficiently

The Temu Seller Hub MCP Server exposes 12 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Temu Seller Hub to CrewAI via MCP

Follow these steps to integrate the Temu Seller Hub MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 12 tools from Temu Seller Hub

Why Use CrewAI with the Temu Seller Hub MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Temu Seller Hub through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Temu Seller Hub + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Temu Seller Hub MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Temu Seller Hub for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Temu Seller Hub, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Temu Seller Hub tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Temu Seller Hub against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Temu Seller Hub MCP Tools for CrewAI (12)

These 12 tools become available when you connect Temu Seller Hub to CrewAI via MCP:

create_ship_order

Uses the v2 ship order creation API. Create a shipping order to fulfill a delivery

get_aftersale_list

List after-sale / return requests

get_goods_detail

Get full product details for a specific item

get_goods_list

List published products on Temu store

get_goods_sku

Get SKU-level details for a product

get_inventory

List inventory levels across all SKUs

get_logistics_companies

Get supported shipping carriers on Temu

get_order_detail

Get full details for a specific Temu order

get_order_list

Supports pagination and optional status filter. Uses create_after/create_before timestamps. Get a list of Temu orders by creation date range

get_purchase_orders

Used to track incoming stock requests from the platform. Get restocking / purchase orders from Temu

get_ship_order_list

List existing shipping orders

sync_inventory

Update inventory stock quantity for a specific SKU

Example Prompts for Temu Seller Hub in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Temu Seller Hub immediately.

"Get my Temu orders from the last 24 hours and summarize pending fulfillment."

"Mark order TMU-2024-88712 as shipped with tracking number YT2048391004."

"Update inventory for SKU TMU-SHOE-42BLK to 250 units."

Troubleshooting Temu Seller Hub MCP Server with CrewAI

Common issues when connecting Temu Seller Hub to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Temu Seller Hub + CrewAI FAQ

Common questions about integrating Temu Seller Hub MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.