Skip to content

Commit 9e059f1

Browse files
chore: update manifest.json and docker-compose.yml to v4.5.0 [skip ci]
1 parent f62c523 commit 9e059f1

2 files changed

Lines changed: 2 additions & 2 deletions

File tree

docker-compose.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
services:
22
linkedin-mcp:
3-
image: stickerdaniel/linkedin-mcp-server:4.4.2
3+
image: stickerdaniel/linkedin-mcp-server:4.5.0
44
volumes:
55
- ~/.linkedin-mcp:/home/pwuser/.linkedin-mcp
66
environment:

manifest.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
"manifest_version": "0.4",
33
"name": "linkedin-mcp-server",
44
"display_name": "LinkedIn MCP Server",
5-
"version": "4.4.2",
5+
"version": "4.5.0",
66
"description": "Connect Claude to LinkedIn for profiles, companies, job details, and people search",
77
"long_description": "# LinkedIn MCP Server\n\nConnect Claude to your LinkedIn account with an MCP Bundle (MCPB, formerly DXT). The bundle starts quickly, downloads the Patchright Chromium browser in the background when needed, and opens LinkedIn login on the first auth-requiring tool call.\n\n## First-time managed runtime flow\n\n1. Install the `.mcpb` bundle in Claude Desktop.\n2. Start Claude Desktop; the MCP server starts and begins preparing the Patchright Chromium browser cache under `~/.linkedin-mcp/patchright-browsers`.\n3. If you call a tool before setup finishes, the tool returns a setup-in-progress error.\n4. On the first tool call that needs authentication, a browser window opens so you can sign into LinkedIn.\n5. Retry the tool after login completes.\n\nDocker remains available as a separate runtime path, but it still requires host-side `--login`.",
88
"author": {

0 commit comments

Comments
 (0)