linkedin-relay-mcp 3.17.0 → 3.18.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 +14 -1
- package/README.md +2 -1
- package/dist/cli.js +351 -111
- package/dist/cli.js.map +1 -1
- package/dist/index.js +9 -0
- package/dist/index.js.map +1 -1
- package/dist/mcp-shim.js +284 -39
- 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 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.
|
|
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) or their saved items (saved posts, courses, the job tracker), 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
|
|
@@ -348,6 +348,19 @@ 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
|
+
### `my-items` — saved posts, learning, the job tracker.
|
|
352
|
+
```
|
|
353
|
+
my_items list:posts|learning|jobs [stage:saved|in-progress|applied|interview|archived] [limit:N] [compact]
|
|
354
|
+
```
|
|
355
|
+
CLI: `lnrelay my-items posts|learning|jobs [--stage …] [--compact]`. 1 page call per 10 items.
|
|
356
|
+
- `posts`: what the user saved — `id` (the post urn: `post` reads its thread), `author`,
|
|
357
|
+
`authorHeadline`, `posted`, `text`, `url`.
|
|
358
|
+
- `learning`: their courses — `name`, `length`, `detail` (instructor, released), `progress`.
|
|
359
|
+
- `jobs`: the job tracker — `id` (`job` reads it in full: description and apply link), `title`,
|
|
360
|
+
`company`, `location`, `workplace`, `stage`, `note` (e.g. "No longer accepting applications").
|
|
361
|
+
With no `stage`, all five stages (5 calls) and `meta.byStage`. LinkedIn does not check stage names:
|
|
362
|
+
an empty stage and a misnamed one look the same, so trust `byStage` with that in mind.
|
|
363
|
+
|
|
351
364
|
### `events` / `event` — the events page, and events in full.
|
|
352
365
|
```
|
|
353
366
|
events [premium] [limit:N] [compact] event event:"<id | /events/ URL>" | ["<id>", …]
|
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
|
-
|
|
27
|
+
Thirty 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,7 @@ 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
|
+
| `my-items` | your saved posts, LinkedIn Learning courses, and the job tracker by stage |
|
|
46
47
|
| `events` · `event` | the events page's recommended and Premium events, and any event in full: when, where, attendees, organiser, its site |
|
|
47
48
|
| `network` | your My Network: connections, following, followers, pages, events, groups, invitations sent — or the count of each |
|
|
48
49
|
| `inbox` · `messages` · `draft` · `drafts` | read your messages without marking them read; draft replies locally — nothing is ever sent |
|