Content
# MCP LinkedIn Sales Navigator
[](https://github.com/globodai-group/mcp-linkedin-sales-navigator/actions/workflows/ci.yml)
[](https://www.npmjs.com/package/globodai-mcp-linkedin-sales-navigator)
**MCP server for LinkedIn Sales Navigator** — Browser automation via Playwright.
> LinkedIn Sales Navigator doesn't provide a public API. This MCP server uses browser automation (Playwright) to control Sales Navigator through an authenticated browser session. It enables AI assistants to search leads, view profiles, manage lists, send InMails, and export data — all through the standard [Model Context Protocol](https://modelcontextprotocol.io/).
## ⚠️ Important Disclaimers
- **This tool requires an active LinkedIn Sales Navigator subscription**
- **Browser automation**: This operates by controlling a real browser — no API hacking
- **Session required**: You must be logged into LinkedIn in the browser instance
- **Rate limiting**: Use responsibly. LinkedIn may restrict accounts that perform excessive automation
- **Terms of Service**: Review LinkedIn's ToS before using automation tools
- **No credentials stored**: This tool never stores or handles LinkedIn passwords
## Features
| Tool | Description |
|------|-------------|
| `linkedin_search_leads` | Search leads with filters (title, company, location, industry, seniority, etc.) |
| `linkedin_get_lead_profile` | Get detailed profile information for a lead |
| `linkedin_save_lead` | Save a lead to a list |
| `linkedin_list_lead_lists` | List all lead lists |
| `linkedin_create_lead_list` | Create a new lead list |
| `linkedin_send_inmail` | Send an InMail message (with dry-run support) |
| `linkedin_export_leads` | Export leads to JSON or CSV format |
| `linkedin_session_status` | Check browser connection, Sales Navigator auth, and today's usage budgets (call this first when debugging) |
## Quick Start
### Prerequisites
- **Node.js** ≥ 20
- **LinkedIn Sales Navigator** subscription with active session
- A browser with an active LinkedIn login (Chrome recommended)
### Install
```bash
npm install globodai-mcp-linkedin-sales-navigator
```
Or clone and build from source:
```bash
git clone https://github.com/globodai-group/mcp-linkedin-sales-navigator.git
cd mcp-linkedin-sales-navigator
npm install
npm run build
```
### Configuration
The server is configured via environment variables (read in `src/index.ts`):
| Variable | Default | Description |
|----------|---------|-------------|
| `LSN_AUTH_METHOD` | `cdp` | Auth mode: `cdp` (attach to running Chrome), `session` (Playwright + user data dir), or `cookies` (JSON cookie file) |
| `LSN_CDP_ENDPOINT` | `http://localhost:9222` | CDP HTTP endpoint when `LSN_AUTH_METHOD=cdp` |
| `LSN_COOKIES_PATH` | *(unset)* | Path to exported cookies JSON when `LSN_AUTH_METHOD=cookies` |
| `LSN_USER_DATA_DIR` | *(unset)* | Chrome profile directory when `LSN_AUTH_METHOD=session` |
| `LSN_HEADLESS` | `false` | Set to `true` to run Chromium headless (`session` / `cookies` modes) |
| `LSN_NAVIGATION_TIMEOUT` | `30000` | Page navigation timeout (ms) |
| `LSN_ACTION_TIMEOUT` | `10000` | Click/fill/wait timeout (ms) |
| `LSN_VIEWPORT_WIDTH` | `1280` | Viewport width (px) |
| `LSN_VIEWPORT_HEIGHT` | `900` | Viewport height (px) |
| `LSN_DAILY_PROFILE_VIEWS` | `80` | Daily cap for `linkedin_get_lead_profile`. `0` = unlimited |
| `LSN_DAILY_SEARCHES` | `30` | Daily cap for `linkedin_search_leads`, plus each results page fetched by `linkedin_export_leads`. `0` = unlimited |
| `LSN_DAILY_SAVES` | `50` | Daily cap for `linkedin_save_lead` + `linkedin_create_lead_list`. `0` = unlimited |
| `LSN_DAILY_INMAILS` | `15` | Daily cap for `linkedin_send_inmail` sends (dry runs do not count). `0` = unlimited |
| `LSN_MIN_ACTION_INTERVAL_MS` | `4000` | Minimum delay between page navigations/actions, plus 0–50% random jitter |
| `LSN_USAGE_FILE` | `~/.mcp-linkedin-sales-navigator/usage.json` | Local JSON file for daily counters (dates and counts only) |
## Rate limits and account safety
This server throttles **your own** Sales Navigator activity so a Claude session does not fire actions back-to-back. It is not anti-detection: there is no fingerprint spoofing, user-agent rotation, or proxy support.
| Budget | Default | What counts |
|--------|---------|-------------|
| Profile views | 80 / local day | Each `linkedin_get_lead_profile` call |
| Searches | 30 / local day | Each `linkedin_search_leads` call, and each results page fetched by `linkedin_export_leads` |
| Saves | 50 / local day | `linkedin_save_lead` (real save) and `linkedin_create_lead_list` |
| InMails | 15 / local day | `linkedin_send_inmail` calls that actually send. Dry runs do not count |
| Action pacing | 4000 ms + 0–50% jitter | Minimum gap between navigations/actions across all tools |
`0` on a daily budget means unlimited. Raise a cap by setting the matching `LSN_DAILY_*` variable; check `usageToday` on `linkedin_session_status` for used / cap / remaining. Counters reset at the next local midnight and live in `LSN_USAGE_FILE` (or `~/.mcp-linkedin-sales-navigator/usage.json`). That file stores only dates, category names, and counts.
LinkedIn does not publish official automation limits and restricts automated activity in its User Agreement. **No tool can guarantee an account will not be restricted.** Start with the defaults, spread activity over working hours, and stay within your Sales Navigator InMail credits.
## Authentication Methods
### 1. CDP (Chrome DevTools Protocol) — Recommended
Connect to an already-running Chrome browser with an active LinkedIn session.
Start Chrome with remote debugging:
```bash
# macOS
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome \
--remote-debugging-port=9222
# Linux
google-chrome --remote-debugging-port=9222
# Windows
& "C:\Program Files\Google\Chrome\Application\chrome.exe" --remote-debugging-port=9222
# If Chrome is installed elsewhere, quote the full path. Node.js 20+ is required.
```
Use PowerShell or Command Prompt. Keep the debugging port free (default `9222`) and match `LSN_CDP_ENDPOINT`.
Then log into LinkedIn Sales Navigator manually. The MCP server connects to this browser.
**Shutdown behavior (CDP):** when the MCP server exits, it **detaches** from your Chrome instance only. It does **not** close your tabs or quit the browser.
```bash
LSN_AUTH_METHOD=cdp LSN_CDP_ENDPOINT=http://localhost:9222 npx globodai-mcp-linkedin-sales-navigator
```
### 2. User Data Directory
Use an existing Chrome profile that's already logged into LinkedIn:
```bash
LSN_AUTH_METHOD=session LSN_USER_DATA_DIR=/path/to/chrome/profile npx globodai-mcp-linkedin-sales-navigator
```
### 3. Cookie-Based
Export your LinkedIn cookies and provide them as a JSON file:
```bash
LSN_AUTH_METHOD=cookies LSN_COOKIES_PATH=/path/to/linkedin-cookies.json npx globodai-mcp-linkedin-sales-navigator
```
## MCP client setup
Use the same `command`, `args`, and `env` block in any MCP client. Replace paths and endpoints for your machine.
### Claude Desktop
Edit the config file:
| OS | Path |
|----|------|
| macOS | `~/Library/Application Support/Claude/claude_desktop_config.json` |
| Windows | `%APPDATA%\Claude\claude_desktop_config.json` |
Example entry:
```json
{
"mcpServers": {
"linkedin-sales-navigator": {
"command": "npx",
"args": ["-y", "globodai-mcp-linkedin-sales-navigator"],
"env": {
"LSN_AUTH_METHOD": "cdp",
"LSN_CDP_ENDPOINT": "http://localhost:9222"
}
}
}
}
```
Restart Claude Desktop after saving.
### Claude Code
From a shell (adjust env vars as needed):
```bash
claude mcp add linkedin-sales-navigator -- \
env LSN_AUTH_METHOD=cdp LSN_CDP_ENDPOINT=http://localhost:9222 \
npx -y globodai-mcp-linkedin-sales-navigator
```
### Generic MCP client
Point the client at the package binary via `npx` or `node /path/to/mcp-linkedin-sales-navigator/dist/index.js`, stdio transport, with the environment variables from the table above.
## Clawdbot / CORTX Integration
This MCP server is designed to work seamlessly with [Clawdbot](https://clawd.bot) browser relay:
```json
{
"mcpServers": {
"linkedin-sales-navigator": {
"command": "npx",
"args": ["globodai-mcp-linkedin-sales-navigator"],
"env": {
"LSN_AUTH_METHOD": "cdp",
"LSN_CDP_ENDPOINT": "http://localhost:9222"
}
}
}
}
```
When using Clawdbot's browser relay, the AI assistant can directly control a browser tab where you're logged into Sales Navigator — no additional setup needed.
## Tool Examples
### Search for leads
```json
{
"tool": "linkedin_search_leads",
"arguments": {
"title": "VP of Engineering",
"location": "San Francisco Bay Area",
"companySize": "201-500",
"industry": "Computer Software"
}
}
```
### Get a lead's profile
```json
{
"tool": "linkedin_get_lead_profile",
"arguments": {
"profileUrl": "https://www.linkedin.com/sales/lead/ACwAAAxxxxxx"
}
}
```
### Send an InMail (with dry run)
```json
{
"tool": "linkedin_send_inmail",
"arguments": {
"profileUrl": "https://www.linkedin.com/sales/lead/ACwAAAxxxxxx",
"subject": "Quick question about your team",
"body": "Hi, I noticed your team is growing...",
"dryRun": true
}
}
```
### Export leads to CSV
```json
{
"tool": "linkedin_export_leads",
"arguments": {
"source": "current_search",
"format": "csv",
"limit": 50
}
}
```
## Troubleshooting
Start with the `linkedin_session_status` tool. It connects lazily (same as other tools), reports `authMethod`, `browserConnected`, `authenticated`, `usageToday`, and a short hint for the next step.
| Symptom | What to check |
|---------|----------------|
| **Browser not initialized** | Fixed in **0.2.0**: the browser connects on each tool call if startup failed. Ensure Chrome is running with remote debugging (CDP) or paths are set for `session` / `cookies`. Retry after fixing the environment. |
| **Not authenticated** | Sales Navigator’s shell renders a few seconds after load. Log in at [linkedin.com/sales](https://www.linkedin.com/sales) in the same browser profile the server uses, then call `linkedin_session_status` again. |
| **CDP endpoint unreachable** | Confirm Chrome was started with `--remote-debugging-port=9222` (or your port), nothing else bound to that port, and `LSN_CDP_ENDPOINT` matches (including `http://`). |
| **Expired session / cookie** | Re-authenticate in the browser or refresh exported cookies. An expired `li_at` cookie produces auth failures until you sign in again. |
See [CONTRIBUTING.md](CONTRIBUTING.md) for reporting selector breakage without sharing secrets.
## Architecture
```
┌─────────────────────────────────────────────────┐
│ AI Assistant (Claude, GPT, etc.) │
│ ↕ MCP Protocol (stdio) │
├─────────────────────────────────────────────────┤
│ MCP Server (this package) │
│ ├── Tools (search, leads, inmails, lists, etc.)│
│ ├── Browser Controller (Playwright) │
│ └── Selectors & Auth │
├─────────────────────────────────────────────────┤
│ Playwright → Chromium / Chrome │
│ ↕ CDP or Direct │
├─────────────────────────────────────────────────┤
│ LinkedIn Sales Navigator (web app) │
└─────────────────────────────────────────────────┘
```
## Development
```bash
# Install dependencies
npm install
# Install Playwright browsers
npx playwright install chromium
# Development mode (watch)
npm run dev
# Build
npm run build
# Lint
npm run lint
# Type check
npm run typecheck
# Unit tests
npm test
```
## Selector Maintenance
LinkedIn rotates hashed CSS module classes on every deploy. Selectors in this project follow a fixed priority (see PR #3 and `src/browser/selectors.ts`):
1. **`data-anonymize="..."`** and similar LinkedIn field markers (`person-name`, `headline`, `title`, `company-name`, …)
2. **`data-x--...`**, `data-sn-view-name`, `data-control-name` — product hooks tied to behavior
3. **Semantic HTML / ARIA** and shared **`artdeco-*`** design-system classes
4. **Playwright text matchers** (`:has-text()`, `:text-matches()`) only when nothing else is stable
Field locators are **prioritised arrays**, resolved in order by `src/browser/query.ts` (not comma-separated CSS lists, which follow document order).
The lead profile **topcard** headline and location often lack stable hooks. `src/browser/dom-extract.ts` walks structure from stable anchors (name `h1`, Save button) and reads text by position, with selector fallbacks afterward.
When tools break after a LinkedIn UI change:
1. Reproduce on the affected page and tool
2. Inspect DOM hooks (`data-anonymize`, `data-control-name`) before class names
3. Update selectors, query arrays, or dom-extract heuristics as needed
4. Open a PR with a redacted HTML snippet (see [CONTRIBUTING.md](CONTRIBUTING.md))
## License
MIT — see [LICENSE](LICENSE)
## Disclaimer
This project is not affiliated with, endorsed by, or sponsored by LinkedIn Corporation. LinkedIn and Sales Navigator are trademarks of LinkedIn Corporation. Use this tool responsibly and in accordance with LinkedIn's Terms of Service.
Connection Info
You Might Also Like
No recommendations available