tiktok-erp-mcp
TikTok Shop 一键上架 MCP 服务。把 Seller Open Platform 的 Product API 封装成 MCP 工具， 供智能体完成「草稿 → 审核 → 上架」闭环。凭据（AppKey/AppSecret/店铺 token）只在 server 端使用， 调用方只传业务参数（user_id / shop_cipher / draft_id），永远不碰凭据。
工具清单
| 工具 | 说明 |
|---|---|
list_shops |
列出当前用户已授权店铺（返回 shop_cipher 等展示字段，不含 token） |
get_categories |
获取类目树，精确匹配 category_id（叶子类目） |
create_product_draft |
生成上架草稿（save_mode=AS_DRAFT，无真实上架效果） |
get_draft |
查询草稿详情 |
update_draft |
修改草稿内容（仅 draft 状态可改） |
submit_for_review |
草稿提交人工审核（draft → submitted） |
publish_draft |
上架（前置：status=approved），用 save_mode=LISTING 进入平台审核 |
状态机：draft → submitted → approved → published
启动（STDIO MCP）
uvx tiktok-erp-mcp
环境变量
| 变量 | 必填 | 说明 |
|---|---|---|
TIKTOK_APP_KEY |
是 | 开放平台应用 AppKey |
TIKTOK_APP_SECRET |
是 | 应用 AppSecret |
TIKTOK_SANDBOX |
否 | true/false，默认 true |
TIKTOK_BASE_URL |
否 | API 域名，默认生产域名 |
TIKTOK_DB_PATH |
否 | SQLite 路径，默认 ~/.tiktok_erp_mcp/tokens.db |
TIKTOK_ENCRYPTION_KEY |
否 | Fernet 密钥，留空则明文存 token（仅限 demo） |
安全说明
access_token只存 server 端 SQLite，LLM 只拿到shop_cipher（密文），永远看不到 token。- 生产环境请务必设置
TIKTOK_ENCRYPTION_KEY（Fernet），demo/沙箱可留空明文。
1 maintainer
Metadata
1 maintainer
Release files for tiktok-erp-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| tiktok_erp_mcp-0.1.0.tar.gz | 8.0 kB | Without provenance | Details for tiktok_erp_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tiktok_erp_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for tiktok_erp_mcp-0.1.0-py3-none-any.whl |
Total release size: 18.9 kB
Release files / tiktok_erp_mcp-0.1.0.tar.gz
| Download URL | tiktok_erp_mcp-0.1.0.tar.gz |
|---|---|
| Size | 8.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
266fe11c7637f50d5dd8bba7631b7c332ab41fd7b1d3f757f8bc1ba2f704d927
|
|
BLAKE2b-256 checksum How to use checksums |
d831c626ef915b8251e74b6523675c58375a26f4883aff8b09767e6a98f665cd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.7 {"installer":{"name":"uv","version":"0.11.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / tiktok_erp_mcp-0.1.0-py3-none-any.whl
| Download URL | tiktok_erp_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 10.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
557ddf52c3208266469f574abe38adb200940e60114ab6e78e2e5b205c4bb400
|
|
BLAKE2b-256 checksum How to use checksums |
721ffce2ffb8e458bd83b1a530802137eb0eee0e93956e6bd305eb107d1a6f72
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.7 {"installer":{"name":"uv","version":"0.11.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for tiktok-erp-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
