mcp-cn-commerce
Read-only MCP servers for order, refund and ad data from Chinese platforms: Douyin Shop, Taobao, JD, Kuaishou and others
- 99 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Reads orders, refunds and ad balances with seller keys: commercial and customer personal data
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/mcp-cn-commerceDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Reads orders, refunds and ad balances with seller keys: commercial and customer personal data
This is third-party code. Review the repository files before installing.
What it does
mcp-cn-commerce is a monorepo of independent MCP servers that give an agent structured access to seller data on Chinese marketplaces. Each server wraps one platform's open API: Douyin Shop and Taobao (orders and refunds), JD (orders, shop, two after-sale queries), Kuaishou, Xiaohongshu and WeChat Store (part of order and refund reads), Ocean Engine and Qianchuan (advertiser info and balance) and Pinduoduo (an entry exists but reads are disabled pending the full schema). In all, eight platforms and 155 registered tools, with Youzan available through the SDK only. All tools are read-only by default: the agent analyzes data and changes nothing. A shared base provides connection pools, rate limits, retries, metrics and redaction. Money and time are normalized, and reports flag gaps and incomplete pagination. Each tool's `tools/list` description carries `contract_status`, `supported` and `live_verified` labels. Installation is from PyPI into a virtual environment: `python -m pip install "mcp-cn-commerce==0.1.6"`. Servers start with commands such as `mcp-cn-doudian`, `mcp-cn-jd` and `mcp-cn-oceanengine`, and credentials are set through environment variables.
Who it is for. Sellers and analysts working on Chinese marketplaces who want to read orders, refunds and ad account balances through Claude Desktop or another MCP client.
Good fit when
- Douyin Shop orders for a fixed window must be pulled and the remaining pages and details found
- You need the status, amount and completion time of a Taobao refund
- You need an authorized Ocean Engine ad account balance without opening the interface
- A combined report from normalized records with flags for missing fields is needed
Not a fit when
- You need to change products, prices or stock: the tools only read
- You need Pinduoduo data: reads are closed until the full official schema arrives
- You need data without a seller's authorization: access goes through your platform keys
Example request
Read yesterday's Douyin Shop orders and show the remaining pages, then check the refund status for an order from that listMCP
- Transport
- stdio
- Authentication
- key is optional
Environment variables
DOUDIAN_APP_KEYsecret- Douyin Shop app key
DOUDIAN_APP_SECRETsecret- Douyin Shop app secret
DOUDIAN_ACCESS_TOKENsecret- Douyin Shop access token
JD_APP_KEYsecret- JD app key
JD_APP_SECRETsecret- JD app secret
JD_ACCESS_TOKENsecret- JD access token
Limitations
- Every SDK has `live_verified` set to `false`: real-merchant acceptance and back-office reconciliation are unfinished, so first calls should be compared with the platform's back office.
- The count of registered tools (155) does not equal the count of verified contracts. Some entries are historical or explicitly unsupported, and some operations (full JD refunds, Ocean Engine reports) are closed.
- Each platform needs its own credentials: app key, secret, token and shop ID issued by the platform.
- Python 3.11 or newer is required, and the MCP client is given the absolute path to the executable in `.venv/bin/`.
How to disable. Remove the `oceanengine`, `doudian` and `jd` blocks from the MCP client configuration, then delete the virtual environment with the package. Revoke tokens in the platform's developer console.
FAQ
How do I connect mcp-cn-commerce to Claude Desktop?
Install the package into a virtual environment (`python -m pip install "mcp-cn-commerce==0.1.6"`) and add blocks to the MCP config with absolute paths to `.venv/bin/mcp-cn-doudian`, `mcp-cn-jd` and `mcp-cn-oceanengine`. Set platform credentials in `env`: a desktop client does not see shell variables.
Can the agent change my shop?
No. All tools are read-only by default, and operations marked `supported=false` are rejected before any platform request.
Which platforms are covered?
Douyin Shop, Taobao, JD, Pinduoduo (reads closed), Kuaishou, Xiaohongshu, WeChat Store, Ocean Engine and Qianchuan. Youzan is connected only as an SDK. Per-operation details are in `docs/sdk-integration.md`.
What does the live_verified label mean?
It shows whether an operation has been tested against a real shop. For all SDKs it is currently `false`, so first results should be compared with the seller console. `contract_status`, `supported` and `live_verified` appear in every tool's description.
Which environment variables are needed?
Each platform has its own set: for example `DOUDIAN_APP_KEY`, `DOUDIAN_APP_SECRET`, `DOUDIAN_SHOP_ID` and `DOUDIAN_ACCESS_TOKEN` for Douyin Shop or `JD_APP_KEY`, `JD_APP_SECRET`, `JD_ACCESS_TOKEN` for JD. The full list is in `.env.example`.
Discussion
No questions or reviews yet.
Related
MCP serversMCP servers for Wildberries, Ozon, Yandex Market and Avito seller accounts via official APIs with write confirmation
A set of MCP servers for Wildberries, Ozon, Yandex Market, Bitrix24, amoCRM, Avito, Direct, Metrika, Webmaster and DaData, free locally
A read-only MCP for a Yandex Market seller dashboard: products, orders, prices, stock and reviews, with no write tool at all even if the key has write rights
RetailCRM MCP
retailcrm-mcp
RetailCRM MCP server: orders, customers, products, stock, payments, tasks and store analytics via API v5
mpmentor-ru-mcp-readonly: read-only Wildberries and Ozon
mpmentor-ru-mcp-readonly
A local MCP server connects Codex and Claude Code to Wildberries, Ozon Seller and Ozon Performance with no write or delete tools
An MCP server for the Ozon Seller API with a catalog of 441 methods, read and write access classes, and keys stored outside the repository
README in short
The README (in Chinese and English) explains that this is a set of MCP servers for seller data and not for content publishing. It continues with a platform table with support boundaries, a quick start installing Core 0.1.6 and setting environment variables, MCP client setup, architecture, a tools reference, a security section, request examples and a roadmap.