@sellable/mcp 0.1.14 → 0.1.15

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
@@ -83,14 +83,14 @@ The token is provided when you generate it. Use `list_workspaces` +
83
83
  For customer/package installs, use the public installer:
84
84
 
85
85
  ```bash
86
- npx -y @sellable/install@0.1.14 --host codex --token skt_live_your_token_here --workspace-id your_workspace_id
86
+ npx -y @sellable/install@0.1.15 --host codex --token skt_live_your_token_here --workspace-id your_workspace_id
87
87
  ```
88
88
 
89
89
  If you already have `~/.sellable/config.json`, rerun/verify without rewriting
90
90
  auth:
91
91
 
92
92
  ```bash
93
- npx -y @sellable/install@0.1.14 --host codex
93
+ npx -y @sellable/install@0.1.15 --host codex
94
94
  sellable --verify-only --host codex
95
95
  ```
96
96
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sellable/mcp",
3
- "version": "0.1.14",
3
+ "version": "0.1.15",
4
4
  "type": "module",
5
5
  "description": "Sellable MCP server for Claude Code and Codex campaign workflows",
6
6
  "main": "dist/index.js",
@@ -154,6 +154,18 @@ Validated draft directory:
154
154
  `fetch_company` when possible, otherwise one web lookup, then ask who the
155
155
  LinkedIn messages should send from.
156
156
 
157
+ If `list_senders` returns zero connected senders, avoid the sender-confirmation
158
+ branch entirely. Ask for the user's LinkedIn URL or the company they want to
159
+ send on behalf of so you can research context:
160
+
161
+ ```text
162
+ I’m ready to build this in {workspace}.
163
+
164
+ First, paste your LinkedIn URL or the company website you want to send on
165
+ behalf of. I’ll use that to understand the company before we pick the target,
166
+ offer, proof, and lead source.
167
+ ```
168
+
157
169
  If there is no strong sender match, make the first quick question panel ask
158
170
  for the user's LinkedIn URL or company website. The point of this gate is not
159
171
  "pick a sender"; it is to learn who the user is, infer the current or most