You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -60,19 +60,11 @@ When one section fails but the overall tool call still completes, responses may
60
60
61
61
## 🚀 uvx Setup (Recommended - Universal)
62
62
63
-
**Prerequisites:**[Install uv](https://docs.astral.sh/uv/getting-started/installation/) and run `uvx patchright install chromium` to set up the browser.
This opens a browser for you to log in manually (5 minute timeout for 2FA, captcha, etc.). The browser profile is saved to `~/.linkedin-mcp/profile/`.
74
-
75
-
**Step 2: Client Configuration:**
67
+
**Client Configuration**
76
68
77
69
```json
78
70
{
@@ -85,8 +77,10 @@ This opens a browser for you to log in manually (5 minute timeout for 2FA, captc
85
77
}
86
78
```
87
79
80
+
The server starts quickly, prepares the shared Patchright Chromium browser cache in the background under `~/.linkedin-mcp/patchright-browsers`, and opens a LinkedIn login browser window on the first tool call that needs authentication.
81
+
88
82
> [!NOTE]
89
-
> Sessions may expire over time. If you encounter authentication issues, run `uvx linkedin-scraper-mcp --login` again
83
+
> Early tool calls may return a setup/authentication-in-progress error until browser setup or login finishes. If you prefer to create a session explicitly, run `uvx linkedin-scraper-mcp --login`.
90
84
91
85
### uvx Setup Help
92
86
@@ -117,9 +111,6 @@ This opens a browser for you to log in manually (5 minute timeout for 2FA, captc
117
111
**Basic Usage Examples:**
118
112
119
113
```bash
120
-
# Create a session interactively
121
-
uvx linkedin-scraper-mcp --login
122
-
123
114
# Run with debug logging
124
115
uvx linkedin-scraper-mcp --log-level DEBUG
125
116
```
@@ -158,6 +149,7 @@ parallel. Use `--log-level DEBUG` to see scraper lock wait/acquire/release logs.
158
149
**Session issues:**
159
150
160
151
- Browser profile is stored at `~/.linkedin-mcp/profile/`
152
+
- Managed browser downloads are cached at `~/.linkedin-mcp/patchright-browsers/`
161
153
- Make sure you have only one active LinkedIn session at a time
162
154
163
155
**Login issues:**
@@ -301,40 +293,29 @@ Runtime server logs are emitted by FastMCP/Uvicorn.
301
293
<br/>
302
294
<br/>
303
295
304
-
## 📦 Claude Desktop (DXT Extension)
296
+
## 📦 Claude Desktop MCP Bundle (formerly DXT)
305
297
306
-
**Prerequisites:**[Claude Desktop](https://claude.ai/download) and [Docker](https://www.docker.com/get-started/) installed & running
**One-click installation** for Claude Desktop users:
309
301
310
-
1. Download the [DXT extension](https://github.com/stickerdaniel/linkedin-mcp-server/releases/latest)
311
-
2. Double-click to install into Claude Desktop
312
-
3. Create a session: `uvx linkedin-scraper-mcp --login`
302
+
1. Download the latest `.mcpb` artifact from [releases](https://github.com/stickerdaniel/linkedin-mcp-server/releases/latest)
303
+
2. Double-click to install it into Claude Desktop
304
+
3. Restart Claude Desktop
305
+
4. Call any LinkedIn tool
313
306
314
-
> [!NOTE]
315
-
> Sessions may expire over time. If you encounter authentication issues, run `uvx linkedin-scraper-mcp --login` again.
307
+
On startup, the MCP Bundle starts preparing the shared Patchright Chromium browser cache in the background. If you call a tool too early, Claude will surface a setup-in-progress error. On the first tool call that needs authentication, the server opens a LinkedIn login browser window and asks you to retry after sign-in.
316
308
317
-
### DXT Extension Setup Help
309
+
### MCP Bundle Setup Help
318
310
319
311
<details>
320
312
<summary><b>❗ Troubleshooting</b></summary>
321
313
322
-
**First-time setup timeout:**
314
+
**First-time setup behavior:**
323
315
324
-
- Claude Desktop has a ~60 second connection timeout
325
-
- If the Docker image isn't cached, the pull may exceed this timeout
- Make sure [Docker](https://www.docker.com/get-started/) is installed
337
-
- Check if Docker is running: `docker ps`
316
+
- Claude Desktop starts the bundle immediately; browser setup continues in the background
317
+
- If the Patchright Chromium browser is still downloading, retry the tool after a short wait
318
+
- Managed browser downloads are shared under `~/.linkedin-mcp/patchright-browsers/`
338
319
339
320
**Login issues:**
340
321
@@ -373,19 +354,15 @@ curl -LsSf https://astral.sh/uv/install.sh | sh
373
354
uv sync
374
355
uv sync --group dev
375
356
376
-
# 4. Install Patchright browser
377
-
uv run patchright install chromium
378
-
379
-
# 5. Install pre-commit hooks
357
+
# 4. Install pre-commit hooks
380
358
uv run pre-commit install
381
359
382
-
# 6. Create a session (first time only)
383
-
uv run -m linkedin_mcp_server --login
384
-
385
-
# 7. Start the server
360
+
# 5. Start the server
386
361
uv run -m linkedin_mcp_server
387
362
```
388
363
364
+
The local server uses the same managed-runtime flow as MCPB and `uvx`: it prepares the Patchright Chromium browser cache in the background and opens LinkedIn login on the first auth-requiring tool call. You can still run `uv run -m linkedin_mcp_server --login` when you want to create the session explicitly.
3. Double-click the `.dxt` file to install in Claude Desktop
22
-
4. Restart Claude Desktop
16
+
1. Download the `.mcpb` file below
17
+
2. Double-click the `.mcpb` file to install in Claude Desktop
18
+
3. Restart Claude Desktop
23
19
24
-
> **Note:**The pre-pull step is important because Claude Desktop has a ~60 second connection timeout. Without pre-pulling, the initial image download may exceed this limit.
20
+
> **Note:**MCP Bundles (MCPB) are the renamed successor to DXT/Desktop Extensions.
Copy file name to clipboardExpand all lines: docs/docker-hub.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ A Model Context Protocol (MCP) server that connects AI assistants to LinkedIn. A
15
15
16
16
## Quick Start
17
17
18
-
Create a browser profile locally, then mount it into Docker.
18
+
Create a browser profile locally, then mount it into Docker. Docker already includes its own Chromium runtime, so the managed Patchright Chromium browser download used by MCPB/`uvx` is not needed here.
19
19
20
20
**Step 1: Create profile on the host (one-time setup)**
0 commit comments