linkedin-relay-mcp 1.1.0 → 1.2.0

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.
@@ -183,10 +183,14 @@ call again.
183
183
 
184
184
  ## What this tool will not do
185
185
 
186
- Writes — posting, commenting, reacting — are **not on this surface at all**. They exist as CLI
187
- commands (`lnrelay share`, `comment`, `react`) and go over LinkedIn's own official OAuth scope, not
188
- the private API. Each stops at an interactive terminal, shows exactly what it will send, states the
189
- ToS breach, and requires the user to type a token derived from the content.
186
+ Writes — posting, commenting, reacting, deleting — are **not on this surface at all**. They exist as
187
+ CLI commands (`lnrelay share`, `comment`, `react`, `delete`). Each stops at an interactive terminal,
188
+ shows exactly what it will send and over which surface, and requires the user to type a token
189
+ derived from the content.
190
+
191
+ `share` prefers LinkedIn's official OAuth scope and falls back to the private API when the user has
192
+ no developer app — the prompt always names which, and a Voyager write states the ToS breach. If a
193
+ user asks why writing needs an app at all, the answer is in `docs/DECISION-writes.md`.
190
194
 
191
195
  **Without a terminal there is no write and no network call.** That is deliberate and there is no
192
196
  flag that changes it: a flag an agent could set would not be confirming anything. If the user asks
package/README.md CHANGED
@@ -32,7 +32,7 @@ claude mcp add linkedin-relay -s user -- bun "$(npm root -g)/linkedin-relay-mcp/
32
32
  | `post` · `reactions` | a post's comment thread, and who engaged |
33
33
  | `sync` · `local` · `connections` · `my-posts` | fill a local cache, then query it for free |
34
34
  | `whoami` · `doctor` · `risk` · `budget` · `cache-status` | session, standing and spend |
35
- | `oauth` · `share` · `comment` · `react` | writes, over LinkedIn's official OAuth scope |
35
+ | `oauth` · `share` · `comment` · `react` · `delete` | writes — OAuth when available, private API otherwise |
36
36
  | `purge` | delete cached data |
37
37
 
38
38
  Every command prints a JSON envelope on stdout. `--compact` and `--fields a,b` trim the output;
@@ -48,12 +48,16 @@ self-serve products, no partner review — and then:
48
48
  ```bash
49
49
  lnrelay oauth login --client-id <id> # opens consent, catches the callback, stores the token
50
50
  lnrelay share "text" # prints the plan, asks, then posts
51
- lnrelay oauth status | logout
51
+ lnrelay delete <urn> # reads the post back and shows it before destroying it
52
52
  ```
53
53
 
54
- `lnrelay oauth login` with nothing set up prints the registration steps. Every write stops at an
55
- interactive terminal and shows exactly what it will send, to whom, and how reversible it is — no
56
- TTY means no write and no network call. There is no `--yes`.
54
+ **No company, no Page, no app?** Then that route is closed to you, and `share` falls back to the
55
+ private API using the same session your reads use. It breaches §8.2 and puts the account at risk;
56
+ the prompt says so, names the transport, and asks anyway. An expired OAuth token is never silently
57
+ demoted to it. Reasoning and alternatives: **[docs/DECISION-writes.md](docs/DECISION-writes.md)**.
58
+
59
+ Every write stops at an interactive terminal and shows exactly what it will send, over which
60
+ surface, and how reversible it is — no TTY means no write and no network call. There is no `--yes`.
57
61
 
58
62
  ## Design in one screen
59
63
 
@@ -105,7 +109,7 @@ position under argument. The convergence and the full disagreement record are in
105
109
  ## Development
106
110
 
107
111
  ```bash
108
- bun run check # typecheck + lint + 317 tests
112
+ bun run check # typecheck + lint + 366 tests
109
113
  bun run build
110
114
  bun run dev -- <command>
111
115
  ```