linkedin-relay-mcp 3.14.0 → 3.16.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.
- package/.claude/skills/linkedin-relay/SKILL.md +54 -6
- package/README.md +20 -2
- package/dist/cli.js +1179 -474
- package/dist/cli.js.map +1 -1
- package/dist/index.js +45 -0
- package/dist/index.js.map +1 -1
- package/dist/mcp-shim.js +887 -160
- package/dist/mcp-shim.js.map +1 -1
- package/package.json +1 -1
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: linkedin-relay
|
|
3
|
-
description: Research LinkedIn from the user's own account — find people by company, past company, school, place, title, degree or whose connections they are, search posts, companies, groups, events, courses, products, services and schools, hunt jobs with every filter LinkedIn has and collect their apply links, read profiles, read the chronological feed — and, through the lnrelay CLI, post (text, image or video), comment, reply, react, delete and edit the user's own profile (headline, About, roles, skills) under the approval mode the owner chose. Use when finding or evaluating people (who works or worked somewhere, alumni, people in a role or a city, someone's connections), companies, groups, events, courses, posts on a topic, roles or job openings on LinkedIn, when the user wants job listings or application links, when reading what the user's network is posting, or when the user asks to post, engage or update their profile on LinkedIn.
|
|
3
|
+
description: Research LinkedIn from the user's own account — find people by company, past company, school, place, title, degree or whose connections they are, search posts, companies, groups, events, courses, products, services and schools, hunt jobs with every filter LinkedIn has and collect their apply links, read profiles, read the chronological feed — and, through the lnrelay CLI, post (text, image or video), comment, reply, react, delete and edit the user's own profile (headline, About, roles, skills) under the approval mode the owner chose. Use when looking at the user's own network (connections, followers, who they follow, invitations they sent), when finding or evaluating people (who works or worked somewhere, alumni, people in a role or a city, someone's connections), companies, groups, events, courses, posts on a topic, roles or job openings on LinkedIn, when the user wants job listings or application links, when reading what the user's network is posting, when the user wants to read their LinkedIn messages or draft replies to them, or when the user asks to post, engage or update their profile on LinkedIn. Cannot send messages, connect, or apply to jobs: those do not exist.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# linkedin-relay
|
|
@@ -12,8 +12,8 @@ in the request path.
|
|
|
12
12
|
## Three things to know before you call anything
|
|
13
13
|
|
|
14
14
|
1. **Every call spends a budget that cannot be topped up.** Caps are deliberately low (30 profile
|
|
15
|
-
reads a day, 25
|
|
16
|
-
job reads) because LinkedIn restricts accounts for *read*
|
|
15
|
+
reads a day, 25 search calls shared by `people`, `search` (every kind) and name lookups, 350
|
|
16
|
+
requests total; job hunting has its own 150 job searches and 60 job reads) because LinkedIn restricts accounts for *read*
|
|
17
17
|
velocity alone — several documented restrictions involved no automation and no writes, just fast
|
|
18
18
|
browsing. Check `meta.budget.remaining`; when it's low, tell the user and stop rather than
|
|
19
19
|
spending the rest.
|
|
@@ -348,6 +348,52 @@ experience
|
|
|
348
348
|
Each role on their profile with its `positionId` and title. The id is what `lnrelay role edit` and
|
|
349
349
|
`lnrelay role remove` take.
|
|
350
350
|
|
|
351
|
+
### `network` — the user's My Network. Read only.
|
|
352
|
+
```
|
|
353
|
+
network [list:connections|following|followers|pages|events|groups|invitations] [limit:N] [start:N] [compact]
|
|
354
|
+
```
|
|
355
|
+
CLI: `lnrelay network [list] [--limit N] [--compact]`. With no list: `counts` of each (7 page calls).
|
|
356
|
+
With a list, its rows, 50 a call: people (connections, following, followers) as `id`, `name`,
|
|
357
|
+
`headline`, `location`, `degree`, `url`; pages, events, groups as `id`, `name`, `subtitle`, `detail`,
|
|
358
|
+
`url`; sent invitations as `to`, `id`, `headline`, `sent`, `note`, `url`.
|
|
359
|
+
- This is the live list. `connections` (the cache, filled by `sync`) is free but only as fresh as the
|
|
360
|
+
last sync; `network connections` costs a call and is current.
|
|
361
|
+
- Opening My Network in the browser clears the invitations badge and marks notifications seen; this
|
|
362
|
+
does neither.
|
|
363
|
+
- Not available: received invitations, newsletters, "people you may know".
|
|
364
|
+
|
|
365
|
+
### `inbox` — 1 page call per 20 conversations. The user's messages.
|
|
366
|
+
```
|
|
367
|
+
inbox [folder:inbox|primary|other|archive|requests|spam] [unread] [limit:N] [compact]
|
|
368
|
+
```
|
|
369
|
+
CLI: `lnrelay inbox [--folder archive] [--unread] [--limit N] [--compact]`. Each conversation: `id`,
|
|
370
|
+
`url` (the thread), `with` (each person or organisation: `name`, `kind`, `headline`, `degree`, `url`),
|
|
371
|
+
`unread`, `lastActivity`, `last` (`from`, `fromMe`, `at`, `text`, `sponsored`), `folders`, `inmail`.
|
|
372
|
+
`meta.unread` counts conversations with unread messages. `inbox` is LinkedIn's Inbox folder; much
|
|
373
|
+
of a mailbox may sit in `archive` or `other`, so look there before saying there is nothing.
|
|
374
|
+
|
|
375
|
+
### `messages` — 1 page call. One conversation.
|
|
376
|
+
```
|
|
377
|
+
messages conversation:"<id from inbox | /messaging/thread/ URL>"
|
|
378
|
+
```
|
|
379
|
+
The latest messages, oldest first: `from` ("you" for the user), `fromMe`, `at`, `text`, `subject`.
|
|
380
|
+
`meta.state: "partial"` means a full page came back and older messages may exist.
|
|
381
|
+
|
|
382
|
+
**Reading is invisible to the other side.** The browser, opening a conversation, also marks it read
|
|
383
|
+
(the sender sees it), clears "unseen" and acknowledges delivery; those are separate calls, and this
|
|
384
|
+
tool makes none of them. Nothing read is stored. These are private messages: summarise or quote them
|
|
385
|
+
to the user, never into anything else (a post, a comment, a file someone else will read).
|
|
386
|
+
|
|
387
|
+
### `draft` / `drafts` — local. A reply for the user to send.
|
|
388
|
+
```
|
|
389
|
+
draft conversation:"<id | thread URL>" text:"<reply>" drafts draft remove:"<draft id>"
|
|
390
|
+
```
|
|
391
|
+
CLI: `lnrelay draft <conversation> "<text>" | --file <path>`, `lnrelay drafts`, `lnrelay draft remove <id>`.
|
|
392
|
+
Saves the reply ON THIS MACHINE with the conversation's link (one read, to check the conversation
|
|
393
|
+
and who it is with). **Nothing is sent, and nothing can be: there is no send.** Show the user the
|
|
394
|
+
draft and the link; they open it, paste, review, and send it themselves. Write drafts in the user's
|
|
395
|
+
own voice and language, from what the conversation actually says.
|
|
396
|
+
|
|
351
397
|
### `skills` — live, ~3 calls. The user's skills.
|
|
352
398
|
```
|
|
353
399
|
skills
|
|
@@ -482,10 +528,12 @@ Things worth telling a user who asks:
|
|
|
482
528
|
preview's own words, which name the timezone.
|
|
483
529
|
- **Deleting a comment also deletes every reply under it**, including other people's. Verified live.
|
|
484
530
|
|
|
485
|
-
|
|
486
|
-
|
|
531
|
+
**Sending a message and connecting do not exist at all, in any surface.** Messages can be read and
|
|
532
|
+
replies drafted (below), but a draft stays on this machine for the user to send. These are the
|
|
533
|
+
actions where the enforcement reports cluster, and an agent bug there is visible to a third party
|
|
534
|
+
and unrecoverable.
|
|
487
535
|
|
|
488
|
-
Also absent by design:
|
|
536
|
+
Also absent by design: notifications, nested comment replies, and bulk sweeps.
|
|
489
537
|
|
|
490
538
|
## Honest risk
|
|
491
539
|
|
package/README.md
CHANGED
|
@@ -24,7 +24,7 @@ lnrelay local "rust" # then search it offline, free
|
|
|
24
24
|
|
|
25
25
|
## As an MCP server
|
|
26
26
|
|
|
27
|
-
Twenty-
|
|
27
|
+
Twenty-seven tools, none of which writes to LinkedIn, so an agent does the reading. Writes are not on that surface at any price.
|
|
28
28
|
The bundled Claude Code skill (`.claude/skills/linkedin-relay/SKILL.md`) teaches an agent the
|
|
29
29
|
funnels, the budget, and how to read `meta` — including step-by-step recipes for finding people and
|
|
30
30
|
for job hunting.
|
|
@@ -43,6 +43,8 @@ claude mcp add linkedin-relay -s user -- bun "$(npm root -g)/linkedin-relay-mcp/
|
|
|
43
43
|
| `jobs` · `job` · `job-filters` | job search with every filter, several keyword sets merged in one call, and apply links |
|
|
44
44
|
| `post` · `reactions` | a post's comment thread, and who engaged |
|
|
45
45
|
| `scheduled` · `experience` · `skills` | your queued posts, and your own roles and skills |
|
|
46
|
+
| `network` | your My Network: connections, following, followers, pages, events, groups, invitations sent — or the count of each |
|
|
47
|
+
| `inbox` · `messages` · `draft` · `drafts` | read your messages without marking them read; draft replies locally — nothing is ever sent |
|
|
46
48
|
| `sync` · `local` · `connections` · `my-posts` | fill a local cache, then query it for free |
|
|
47
49
|
| `whoami` · `doctor` · `risk` · `budget` · `cache-status` | session, standing and spend |
|
|
48
50
|
| `share` · `comment` · `reply` · `edit` · `react` · `delete` | writes to your feed — OAuth when available, private API otherwise |
|
|
@@ -83,6 +85,22 @@ approved the way **you** chose with `lnrelay approval set` (only at a real termi
|
|
|
83
85
|
There is no `--yes` and no environment variable. Every approval and outcome is logged to
|
|
84
86
|
`~/.lnrelay/writes.jsonl`.
|
|
85
87
|
|
|
88
|
+
## Messages: read, and draft — never send
|
|
89
|
+
|
|
90
|
+
```bash
|
|
91
|
+
lnrelay inbox --folder archive --unread --compact # conversations, who with, unread, last message
|
|
92
|
+
lnrelay messages <conversation-id|thread-url> # a conversation, oldest first
|
|
93
|
+
lnrelay draft <conversation-id> "Thanks — let's talk Tuesday." # saved locally, with the thread link
|
|
94
|
+
lnrelay drafts # your drafts; open the link and send it yourself
|
|
95
|
+
```
|
|
96
|
+
|
|
97
|
+
- **Reading leaves no trace.** Opening a conversation in the browser marks it read, clears "unseen"
|
|
98
|
+
and acknowledges delivery — separate calls this tool never makes. Nothing read is stored.
|
|
99
|
+
- **There is no send.** A draft is a local note (`~/.lnrelay/drafts.json`, owner-only) with the
|
|
100
|
+
conversation's link; you review and send it yourself. Agents get `inbox`, `messages` and `draft`
|
|
101
|
+
over MCP for exactly that: read, then draft.
|
|
102
|
+
- Folders: `inbox`, `primary`, `other`, `archive`, `requests`, `spam`.
|
|
103
|
+
|
|
86
104
|
## Searching everything else
|
|
87
105
|
|
|
88
106
|
`lnrelay search <kind>` covers the rest of the search box — `posts`, `companies`, `groups`, `events`,
|
|
@@ -146,7 +164,7 @@ lnrelay job <id> <id> <id> # finalist
|
|
|
146
164
|
- **The apply link** is the employer's own site (`external`) or LinkedIn's Easy Apply. This tool
|
|
147
165
|
finds jobs; it does not apply to them.
|
|
148
166
|
- Job hunting has its own daily budget — 150 search calls, 60 job reads — so it neither uses up nor
|
|
149
|
-
is stopped by
|
|
167
|
+
is stopped by the other searches, which share 25 search calls a day.
|
|
150
168
|
|
|
151
169
|
## Design in one screen
|
|
152
170
|
|