ppxc-leads-mcp 0.1.12 → 0.1.13
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md
CHANGED
|
@@ -14,7 +14,7 @@ Setup guide: <https://opc1.me/download/mcp>
|
|
|
14
14
|
- Finds high-intent sales leads from public comments.
|
|
15
15
|
- Detects purchase intent, comparison questions, complaints, and recommendation requests.
|
|
16
16
|
- Generates follow-up scripts that a sales or private-traffic team can use.
|
|
17
|
-
- Saves
|
|
17
|
+
- Saves results into the user's customer pool after OPC login and save/unlock.
|
|
18
18
|
- Helps content teams turn real customer questions into the next content angles.
|
|
19
19
|
|
|
20
20
|
Best-fit searches: lead generation, sales leads, social media leads, comment analysis, intent detection, customer discovery, CRM, social listening, local business leads, Xiaohongshu leads, Douyin leads, Kuaishou leads.
|
|
@@ -86,7 +86,8 @@ The package exposes eleven MCP tools:
|
|
|
86
86
|
- Platform login sessions and OPC login credentials stay on the user's machine.
|
|
87
87
|
- Platform tokens and cookies are not uploaded to OPC and are not written to diagnostics.
|
|
88
88
|
- Public comment text is sent to OPC over HTTPS for customer-intent analysis, follow-up suggestions, and customer-pool storage.
|
|
89
|
-
-
|
|
89
|
+
- Trial scans show the first two complete customer signals and do not save to the customer pool.
|
|
90
|
+
- Saved results are stored only in the user's own OPC customer pool.
|
|
90
91
|
- Captchas, QR-code login, and security checks are handled by the user in a local window. This package does not bypass verification.
|
|
91
92
|
- The tool does not send private messages or automate outreach.
|
|
92
93
|
|
package/package.json
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "ppxc-leads-mcp",
|
|
3
|
-
"productName": "
|
|
4
|
-
"version": "0.1.
|
|
5
|
-
"description": "
|
|
3
|
+
"productName": "OPC 评论线索雷达",
|
|
4
|
+
"version": "0.1.13",
|
|
5
|
+
"description": "OPC 评论线索雷达：从公开评论里识别高意向客户线索",
|
|
6
6
|
"keywords": [
|
|
7
7
|
"mcp",
|
|
8
8
|
"lead-generation",
|
|
@@ -122,7 +122,7 @@ description: OPC 评论线索雷达：找客户、销售线索、评论分析、
|
|
|
122
122
|
3. **前 5 名**：每人一行——昵称、意向、需求类型、一句评论原话。
|
|
123
123
|
4. **战报文件**：如果返回里有 `reportFile`，只能把它说成「本机临时战报备份」，可用于转发同事照着跟进；不要把它说成解锁入口，也不要让用户误以为本地 HTML 能解锁全部客户。
|
|
124
124
|
5. **下一步提示**：提醒完整名单、历史记录、解锁和保存动作在 OPC 网页端客户池完成。
|
|
125
|
-
6. **转化动作（重要）**：如果返回里 `paywall.locked` 为真，说明已经先给用户看到了前几个完整客户。要**如实、不啰嗦**地转达：「这次挖到 N 个，先给你看前 2 个完整线索（含话术和主页入口），其余 X
|
|
125
|
+
6. **转化动作（重要）**：如果返回里 `paywall.locked` 为真，说明已经先给用户看到了前几个完整客户。要**如实、不啰嗦**地转达：「这次挖到 N 个，先给你看前 2 个完整线索（含话术和主页入口），其余 X 个已锁。登录并开通后可以保存到客户池并解锁完整名单」。用 `paywall.unlockHint` 的话术，别夸大、别假装全给了。
|
|
126
126
|
7. **登录时机**：用户说「看剩下的」「保存」「查客户池」「继续跟进」时，再调 `check_status_and_login`，参数 `action=login_ppxc`，让他登录 OPC。不要在试用扫描前做这一步。
|
|
127
127
|
|
|
128
128
|
### 第 6.1 步：收集用户判断（持续学习的关键）
|