Skip to content

Releases: devag7/linkedin-mcp

v2.0.3

Choose a tag to compare

@github-actions github-actions released this 17 Jun 09:24

Full Changelog: v2.0.2...v2.0.3

v2.0.2

Choose a tag to compare

@github-actions github-actions released this 17 Jun 09:20

Full Changelog: v2.0.1...v2.0.2

v2.0.1

Choose a tag to compare

@github-actions github-actions released this 17 Jun 07:10

Full Changelog: v2.0.0...v2.0.1

v2.0.0

Choose a tag to compare

@github-actions github-actions released this 16 Jun 20:24

Full Changelog: v1.0.0...v2.0.0

v1.0.4 — Honesty Audit

Choose a tag to compare

@devag7 devag7 released this 13 Jun 07:01

Documentation Integrity Release

Live testing confirmed all data tools fail against LinkedIn due to Cloudflare bot-management (302 redirect loops that plain HTTP cannot resolve — verified with both Node fetch and curl).

This release corrects every false/misleading claim:

What Changed

  • README: Removed "most reliable" tagline. Added ⚠️ Cloudflare limitation warning. Added "Known Limitations" section. Rewrote comparison table truthfully.
  • AGENTS.md: Added limitation warning. Fixed OAuth claim (0 call sites, not "experimental").
  • mcp-manifest.json: Corrected both model and human descriptions.
  • package.json: Honest description with Cloudflare note.
  • whoami tool: Capabilities now include note about Cloudflare blocking.
  • health_check tool: Description clarifies it checks linkedin.com reachability, NOT Voyager API access.

What Still Works

  • MCP protocol (36 tools register, schemas valid) ✅
  • whoami, health_check, CLI ✅
  • Cookie jar + redirect handling (v1.0.3) ✅
  • 53 tests, all passing ✅

Install

npx -y linkedin-mcp-tools@1.0.4

Full Changelog: v1.0.3...v1.0.4

v1.0.3 — Cloudflare Cookie-Bounce Fix

Choose a tag to compare

@devag7 devag7 released this 13 Jun 06:39

🔴 Critical: All Data Tools Now Work Against Live LinkedIn

v1.0.2 and earlier: every data tool (get_my_profile, search_people, etc.) returned {"error":"fetch failed"} after 29s when used against real LinkedIn.

Root cause: Cloudflare bot-management returns HTTP 302 with Set-Cookie: __cf_bm. Node fetch() auto-followed without storing the cookie → infinite redirect loop.

Fix: redirect: 'manual' + persistent cookie jar. Every response's Set-Cookie is captured and merged into subsequent requests.

Also Fixed

  • CSRF token now required — previously fabricated ajax:<timestamp> was rejected by LinkedIn. Now throws clear error: "Copy the JSESSIONID cookie value from your browser."
  • validateCookie() also handles Cloudflare bounces
  • 53 tests (4 new), all passing

Install

npx -y linkedin-mcp-tools@1.0.3

Full Changelog: v1.0.2...v1.0.3

v1.0.2 — 9 Bug Fixes, Security Hardening

Choose a tag to compare

@devag7 devag7 released this 13 Jun 06:03

What's Changed

🔴 Critical Fixes

  • HTTP transport now shares rate limiter and cache across requests — previously each request created a new server instance, defeating rate limiting and caching
  • search_people filters (connectionOf, network) now work — parameters were accepted but silently ignored
  • OAuth documentation corrected — all 36 tools use Voyager API (cookie auth); OAuth marked experimental

🟡 Security & Moderate Fixes

  • CORS origin configurable via CORS_ORIGIN env var (was hardcoded to *)
  • HTTP body size limit — 1MB max with 413 response (was unbounded)
  • Version consistency — reads from package.json at runtime

🟢 Minor Fixes

  • whoami category counts corrected
  • Removed dead visibilityMap code
  • Updated User-Agent from Chrome 120 → 131

📦 Infrastructure

  • 49 tests (up from 42), all passing
  • Fixed deprecated npm flags in Dockerfile
  • Added HEALTHCHECK to Dockerfile
  • Corrected all supporting docs

Install

npx -y linkedin-mcp-tools

Full Changelog: v1.0.1...v1.0.2

v1.0.1

Choose a tag to compare

@github-actions github-actions released this 12 Jun 14:52

Full Changelog: v1.0.0...v1.0.1

v1.0.0

Choose a tag to compare

@github-actions github-actions released this 11 Jun 18:02

🔗 LinkedIn MCP v1.0.0

The most reliable LinkedIn MCP server for AI assistants — 36 tools, remote-first, zero dependencies.

✨ Highlights

  • 🚀 36 LinkedIn tools across 7 categories: Profile, Messaging, Company, Jobs, Network, Feed, Utility
  • 🔒 Dual auth: OAuth 2.0 + Cookie authentication with one-time --login setup
  • API-native: No browser, no Chromium, no Playwright — pure LinkedIn API
  • 🌍 Remote-first: Streamable HTTP + stdio transport
  • 📦 ~50KB bundle vs 500MB+ browser-based alternatives

🚀 Quick Start

# One-time setup
npx linkedin-mcp-tools --login

# Use with Claude Desktop (download claude-desktop-config.json below)

📥 Downloads

  • claude-desktop-config.json — Drop this into your Claude Desktop config
  • index.js — Standalone server bundle

📋 Full Tool List

Category Tools
👤 Profile get_profile, get_my_profile, get_profile_skills, get_profile_recommendations, get_profile_activity, get_sidebar_profiles, search_people
💬 Messaging get_inbox, get_conversation, search_conversations, send_message, reply_to_thread, mark_conversation_read
🏢 Company get_company, get_company_posts, get_company_employees, search_companies, get_company_jobs
💼 Jobs search_jobs, get_job_details, get_saved_jobs, get_job_applicants
🤝 Network connect_with_person, get_connections, get_pending_invitations, withdraw_invitation, accept_invitation, get_network_stats
📰 Feed get_feed, create_post, react_to_post, comment_on_post, search_posts
🔧 Utility whoami, health_check, get_notifications