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 AutoGen 12 tools — connect in under 2 minutes

Name: Temu Seller Hub
Availability: InStock
Author: Vinkius

microsoft.github.io/autogen/docs/tools/mcp-tools

Built by Vinkius GDPR 12 Tools Framework

Microsoft AutoGen enables multi-agent conversations where agents negotiate, delegate, and execute tasks collaboratively. Add Temu Seller Hub as an MCP tool provider through Vinkius and every agent in the group can access live data and take action.

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

import asyncio
from autogen_agentchat.agents import AssistantAgent
from autogen_ext.tools.mcp import McpWorkbench

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    async with McpWorkbench(
        server_params={"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"},
        transport="streamable_http",
    ) as workbench:
        tools = await workbench.list_tools()
        agent = AssistantAgent(
            name="temu_seller_hub_agent",
            tools=tools,
            system_message=(
                "You help users with Temu Seller Hub. "
                "12 tools available."
            ),
        )
        print(f"Agent ready with {len(tools)} tools")

asyncio.run(main())

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.

AutoGen enables multi-agent conversations where agents negotiate, delegate, and collaboratively use Temu Seller Hub tools. Connect 12 tools through Vinkius and assign role-based access. a data analyst queries while a reviewer validates, with optional human-in-the-loop approval for sensitive operations.

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 AutoGen 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 AutoGen via MCP

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

Install AutoGen

Run pip install "autogen-ext[mcp]"

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

Integrate into workflow

Use the agent in your AutoGen multi-agent orchestration

Explore tools

The workbench discovers 12 tools from Temu Seller Hub automatically

Why Use AutoGen with the Temu Seller Hub MCP Server

AutoGen provides unique advantages when paired with Temu Seller Hub through the Model Context Protocol.

Multi-agent conversations: multiple AutoGen agents discuss, delegate, and collaboratively use Temu Seller Hub tools to solve complex tasks

Role-based architecture lets you assign Temu Seller Hub tool access to specific agents. a data analyst queries while a reviewer validates

Human-in-the-loop support: agents can pause for human approval before executing sensitive Temu Seller Hub tool calls

Code execution sandbox: AutoGen agents can write and run code that processes Temu Seller Hub tool responses in an isolated environment

Temu Seller Hub + AutoGen Use Cases

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

Collaborative analysis: one agent queries Temu Seller Hub while another validates results and a third generates the final report

Automated review pipelines: a researcher agent fetches data from Temu Seller Hub, a critic agent evaluates quality, and a writer produces the output

Interactive planning: agents negotiate task allocation using Temu Seller Hub data to make informed decisions about resource distribution

Code generation with live data: an AutoGen coder agent writes scripts that process Temu Seller Hub responses in a sandboxed execution environment

Temu Seller Hub MCP Tools for AutoGen (12)

These 12 tools become available when you connect Temu Seller Hub to AutoGen 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 AutoGen

Ready-to-use prompts you can give your AutoGen 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 AutoGen

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

McpWorkbench not found

Install: pip install "autogen-ext[mcp]"

Temu Seller Hub + AutoGen FAQ

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

How does AutoGen connect to MCP servers?

Create an MCP tool adapter and assign it to one or more agents in the group chat. AutoGen agents can then call Temu Seller Hub tools during their conversation turns.

Can different agents have different MCP tool access?

Yes. AutoGen's role-based architecture lets you assign specific MCP tools to specific agents, so a querying agent has different capabilities than a reviewing agent.