xingzi-mcp

Xingzi Material Distribution MCP Server — Let AI help you distribute materials, audit submissions, and process payments.

Table of Contents

• What is Material Distribution?

• Workflow

• Installation & Configuration

• Available Tools

• Usage Examples

• Pricing Reference

• Task Requirement Writing Guide

• Technical Architecture

• API Reverse Engineering Notes

• FAQ

• Changelog

Related MCP server: Kakao Moment MCP

What is Material Distribution?

"Material Distribution" is a KOC (Key Opinion Consumer) promotion model:

• Advertiser (You): Have promotion needs, prepare materials (images/videos/copy), and are willing to pay for performance.

• KOC (Creator): Have accounts on various social platforms and are willing to publish content for you to earn rewards.

• Xingzi Distribution Platform: An intermediary platform connecting both parties, providing capabilities for task publishing, claiming, submission, and payment.

This MCP serves the "Advertiser" role—publishing tasks, auditing submissions, and paying KOCs.

Workflow

┌─────────────────────────────────────────────────────────┐
│                    广告主（你 + AI）                       │
│                                                         │
│  ① publish_task ──→ 发布任务（素材+要求+单价+人数）        │
│                         │                                │
│                         ▼                                │
│              KOC 在素材广场看到并领取                       │
│                         │                                │
│                         ▼                                │
│              KOC 发布到社交媒体，提交回执                   │
│                         │                                │
│  ③ list_postbacks ──→ 查看回执                            │
│                         │                                │
│  ④ audit_postback ──→ 审核（通过/拒绝）                    │
│                         │                                │
│  ⑤ pay_reward ──────→ 生成支付链接                        │
│                         │                                │
│                         ▼                                │
│              在微信中打开链接完成付款 ✅                     │
└─────────────────────────────────────────────────────────┘

Installation & Configuration

Prerequisites

• Node.js >= 18

• An AI tool that supports MCP (Claude Code / Cursor / Windsurf / Cline, etc.)

• A Xingzi Zhutui platform account (Register: https://m.xingziwenhua.com )

• Xingzi Membership (VIP): Membership is required to publish material distribution tasks (see explanation below).

Why is membership required? The Xingzi Zhutui platform requires membership to publish material distribution tasks for two reasons:

1. Credit and Performance: The membership system helps the platform manage credit and default risks, ensuring advertisers have the ability to pay on time.

2. Member Benefits: Material distribution is an exclusive value-added service for members.

If you are not a member yet, you can sign up in the "Member Center" of the Xingzi Zhutui App / H5.

Claude Code

Edit ~/.claude/settings.json:

{
  "mcpServers": {
    "xingzi": {
      "command": "npx",
      "args": ["-y", "xingzi-mcp"],
      "env": {
        "XINGZI_MOBILE": "你的手机号",
        "XINGZI_PASSWORD": "你的密码"
      }
    }
  }
}

Cursor

Edit .cursor/mcp.json:

{
  "mcpServers": {
    "xingzi": {
      "command": "npx",
      "args": ["-y", "xingzi-mcp"],
      "env": {
        "XINGZI_MOBILE": "你的手机号",
        "XINGZI_PASSWORD": "你的密码"
      }
    }
  }
}

Windsurf / Others

Add the same configuration to the MCP configuration file of the corresponding tool.

No Environment Variables (Manual Login)

You can also leave the env field empty and let the AI call the login tool during the first use:

"Help me log in to Xingzi Distribution, phone number 138xxxx, password xxxx"

Available Tools

There are 11 tools in total, covering the complete workflow for advertisers:

Authentication & Guidance

Publishing Tasks

Auditing Submissions

Payments

Wallet

Usage Examples

Publishing a Distribution Task

你：帮我发一个代发任务
    素材是这张图 https://example.com/ad.jpg
    要求发到小红书，配文提到"夏日好物推荐"
    单价10元，最多50人

AI：[调用 publish_task]
    ✅ 任务发布成功！50 个名额，10 元/条。
    KOC 可以在素材广场看到并领取。

Auditing Submissions and Processing Payments

你：看看任务 1615 的回执，合格的帮我通过

AI：[调用 list_postbacks] 共 3 条回执
    - 66°C 提交了抖音链接 ✓
    - 小明 提交了小红书截图 ✓  
    - 用户A 截图模糊看不清 ✗

    [调用 audit_postback x3] 通过 2 条，拒绝 1 条

你：帮我打款

AI：[调用 pay_reward]
    待打款 2 人，共 20 元
    请在微信中打开此链接付款：https://m.xingziwenhua.com/spages/material/batchpay?id=1615
    
    💡 支付页面可以修改金额（表现好的可以加钱），也可以写奖励说明。

Checking Wallet

你：钱包余额多少？

AI：[调用 get_wallet]
    总收益：11,290.36 元
    可提现：11,256.46 元
    已提现：33.90 元
    冻结中：0.00 元

Pricing Reference

Tasks under 5 Yuan/item have extremely low claim rates, and the MCP will proactively warn you.

Task Requirement Writing Guide

Task requirements (task_requirement) are key to influencing claim rates and completion quality.

Good Task Requirement Examples

发布到小红书，图文形式。
配文需包含"XXX品牌夏日新品"关键词，200字以内。
发布后截图+笔记链接作为回执。

发布到抖音，直接使用我提供的视频素材。
视频标题和文案自由发挥，需要 @XXX品牌 官方账号。
发布后提交视频链接。

Recommended Inclusions

• Which platform to post to (Xiaohongshu / Douyin / Zhihu / Weibo, etc.)

• Format (Image/Text / Video / Article)

• Core copy points (brand name, keywords, hashtags, etc.)

• Posting time requirements (if any)

Recommended Avoidances

• ❌ Requiring posting to multiple platforms at once (better to split into multiple tasks)

• ❌ Restricting follower count (unless you are willing to significantly increase the unit price)

• ❌ Requiring original long videos (high complexity, low completion rate)

• ❌ Requiring pinning/highlighting/trending (uncontrollable factors)

• ❌ Task descriptions that are too long or complex (KOCs will leave immediately)

Technical Architecture

Overall Design

┌──────────────────┐     stdio      ┌───────────────────┐
│  AI 工具          │ ◄──────────► │  xingzi-mcp       │
│  (Claude/Cursor)  │   MCP协议     │  (Node.js Server) │
└──────────────────┘               └─────────┬─────────┘
                                             │ HTTPS
                                             ▼
                                   ┌───────────────────┐
                                   │  api.xingziwenhua  │
                                   │  .com              │
                                   │  (星子助推后端)      │
                                   └───────────────────┘

Tech Stack

• Runtime: Node.js >= 18 (using native fetch)

• MCP SDK: @modelcontextprotocol/sdk

• Parameter Validation: zod (built-in dependency of MCP SDK)

• Transport Protocol: stdio (standard input/output)

• API Communication: HTTPS REST, JSON format

Authentication Mechanism

Xingzi API uses a non-standard authentication method (discovered via reverse engineering the H5 application):

// 不是标准的 Authorization: Bearer <token>
// 而是三个自定义 HTTP headers:
headers: {
  "token": "<JWT>",      // 登录返回的 token
  "plt": "h5",           // 平台标识，固定值
  "user_id": "<number>"  // 用户 ID
}

The token is valid for 24 hours, and the MCP will automatically re-login before it expires.

Amount Handling

The API internally uses cents as the currency unit (e.g., 500 = 5.00 Yuan). The MCP tool layer uses Yuan uniformly and handles internal conversion automatically.

Payment Process

Payments are processed via WeChat JSAPI Payment, which requires a WeChat browser environment (WeixinJSBridge). The MCP cannot initiate payments directly, so it generates a payment page URL instead:

https://m.xingziwenhua.com/spages/material/batchpay?id={task_id}
https://m.xingziwenhua.com/spages/material/batchpay?id={task_id}&to_user_id={koc_id}

Users can complete the payment by opening the link in WeChat. The payment page supports modifying the amount and entering reward notes.

API Reverse Engineering Notes

All API endpoints for this MCP were obtained by reverse engineering the Xingzi Zhutui H5 application (m.xingziwenhua.com). The platform does not provide public API documentation.

Reverse Engineering Method

1. Puppeteer simulating a mobile browser to log in to the H5 application

2. Intercepting XHR requests to observe API calls (custom headers instead of standard Bearer authentication)

3. Parsing webpack chunk JS to extract all API paths

4. Testing endpoints one by one to confirm parameters and return formats

Key Findings

Verified API Endpoints

POST /c/user/login                               — 手机号+密码登录
GET  /c/user/detail                              — 用户信息
GET  /c/channel/list-available                   — 可用推广频道
POST /c/fodder/material/instead/publish           — 发布素材任务
GET  /c/fodder/material/instead/list              — 素材列表
GET  /c/fodder/material/instead/materialInfo      — 素材详情
POST /c/fodder/material/instead/del               — 删除素材
GET  /c/fodder/material/instead/postback/list     — 回执列表
POST /c/fodder/material/instead/postbackAudit     — 审核回执
GET  /c/fodder/material/instead/unpaidAward/list  — 待打款列表
POST /c/fodder/material/instead/batch/pay/reward  — 批量打款 (需微信)
GET  /c/withdraw/wallet                          — 钱包余额

Submission Status Codes (status)

FAQ

Q: How to upload material files?

The publish_task tool accepts file URLs (publicly accessible links), not local file paths. You need to upload files to any file hosting service (e.g., Tencent Cloud COS, Alibaba Cloud OSS, Qiniu, or even GitHub) and pass the URL to the MCP.

The Xingzi H5 application itself uses frontend direct upload to Tencent Cloud COS, but the upload interface is bound to the frontend SDK and cannot be called via pure API.

Q: Why can't payments be completed directly in the MCP?

Xingzi's payments use WeChat JSAPI, which requires calling WeixinJSBridge.invoke('getBrandWCPayRequest', ...) within a WeChat browser. This is a technical limitation of WeChat Pay, not the MCP. The MCP generates a payment page link that you can open in WeChat to pay.

Q: Can a task have multiple material files?

Yes. The files parameter is an array that supports multiple URLs, up to 50 files. Supported formats: gif, jpg, jpeg, png, word, txt, pdf, mp4.

Q: What happens to the material after an audit rejection?

After rejection, the KOC's claim quota is released, and other KOCs can continue to claim it. If you provided a rejection reason (reject_reason), the KOC can see it.

Q: What if the token expires?

Don't worry. The MCP will automatically re-login using your account and password before the token expires. The token is valid for 24 hours.

Q: Can I use multiple accounts at the same time?

One MCP instance corresponds to one account. If you need multiple accounts, you can add multiple servers in the MCP configuration, distinguished by different names:

{
  "mcpServers": {
    "xingzi-account1": {
      "command": "npx",
      "args": ["-y", "xingzi-mcp"],
      "env": { "XINGZI_MOBILE": "手机号1", "XINGZI_PASSWORD": "密码1" }
    },
    "xingzi-account2": {
      "command": "npx",
      "args": ["-y", "xingzi-mcp"],
      "env": { "XINGZI_MOBILE": "手机号2", "XINGZI_PASSWORD": "密码2" }
    }
  }
}

Q: What is a reasonable unit price?

It depends on task complexity. 5 Yuan is the recommended minimum; almost no one claims tasks below 5 Yuan. See Pricing Reference for details.

Q: Can I change the amount on the payment page?

Yes. After opening the link generated by pay_reward, the amount for each KOC can be manually modified. For example, if a KOC's quality is exceptionally good, you can pay them more. You can also enter "Reward Notes" which the KOC can see.

Q: What is the relationship between this MCP and the Xingzi Zhutui App?

Xingzi Zhutui is a comprehensive KOC promotion platform that includes various promotion businesses such as articles, short dramas, and novels. "Material Distribution" is one independent product module. This MCP only encapsulates the advertiser operations for material distribution and does not include other functions of Xingzi Zhutui (keywords, team management, earnings statistics, etc.).

Q: Is it safe? Where are the account and password stored?

• Environment variable method: The password is stored in your local MCP configuration file and will not be transmitted anywhere other than the Xingzi API.

• Manual login method: The password is only used during the current session.

• The MCP code is fully open source and can be audited by yourself.

Changelog

3.0.0 (2026-04-06)

• Full end-to-end workflow verified

• Code and documentation fully cleaned up

• Published to GitHub

2.1.0

• pay_reward supports single/bulk payment, supports koc_user_id parameter

• Payment links support to_user_id filtering

2.0.1

• Fixed audit_postback parameter: is_pass (not isPass), claim_id + postback_id (not material_id + id)

2.0.0

• Refactored for material distribution specifically, removed irrelevant Xingzi Zhutui functions

• Tools streamlined from 21 to 11

• Default value optimization: Channel fixed to Xingzi Distribution, standard materials, fixed unit price, publicly visible

• Currency unit changed from "cents" to "Yuan"

• Added guide usage guide tool

1.0.0

• Initial version, including full Xingzi Zhutui API encapsulation

License

MIT