MCP LinkedIn Sales Navigator
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LSN_HEADLESS | No | Run browser in headless mode | false |
| LSN_AUTH_METHOD | No | Authentication method: cdp, session, or cookies | cdp |
| LSN_CDP_ENDPOINT | No | Chrome DevTools Protocol endpoint | http://localhost:9222 |
| LSN_COOKIES_PATH | No | Path to cookies JSON file (for cookies method) | |
| LSN_USER_DATA_DIR | No | Path to Chrome user data directory (for session method) | |
| LSN_ACTION_TIMEOUT | No | Action timeout in ms | 10000 |
| LSN_VIEWPORT_WIDTH | No | Browser viewport width | 1280 |
| LSN_VIEWPORT_HEIGHT | No | Browser viewport height | 900 |
| LSN_NAVIGATION_TIMEOUT | No | Navigation timeout in ms | 30000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| linkedin_session_statusA | Check LinkedIn Sales Navigator browser connection, authentication, and today's usage budgets. Call this before other tools to verify the session (auth method, browserConnected, authenticated, usageToday). Attaches to the existing browser if needed. Never navigates the user's own tab; opens an owned dedicated tab when no Sales Navigator tab exists (same as other tools). |
| linkedin_search_leadsA | Search for leads on LinkedIn Sales Navigator with filters (title, company, location, industry, seniority, etc.) |
| linkedin_get_lead_profileB | Get detailed profile information for a LinkedIn Sales Navigator lead |
| linkedin_save_leadA | Save a lead to a list on LinkedIn Sales Navigator. Always preview first with dryRun=true before saving (default dryRun=false preserves prior behaviour). |
| linkedin_send_inmailA | Send an InMail message to a lead on LinkedIn Sales Navigator. Requires available InMail credits. Always preview first with dryRun=true before sending (default dryRun=false preserves prior behaviour). |
| linkedin_list_lead_listsA | List all lead lists in LinkedIn Sales Navigator |
| linkedin_create_lead_listB | Create a new lead list in LinkedIn Sales Navigator |
| linkedin_export_leadsB | Export leads from LinkedIn Sales Navigator search results or a specific list to JSON or CSV format |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool addresses a distinct operation: profile retrieval, session health, lead saving, InMail sending, exporting, list creation, list enumeration, and searching. There is no functional overlap; even export_leads and search_leads have clear boundaries (export vs. discover). An agent can unambiguously select the correct tool for each task.
All tools share the 'linkedin_' prefix and use snake_case. Most follow a clear verb_noun pattern (get_lead_profile, save_lead, send_inmail, export_leads, create_lead_list, list_lead_lists, search_leads). The exception is linkedin_session_status, which uses a noun_noun structure and lacks a verb, creating a minor but noticeable inconsistency.
With 8 tools, the server is well-scoped for a LinkedIn Sales Navigator integration. Each tool covers a core workflow (searching, profiling, list management, outreach, and session monitoring) without unnecessary bloat. The count is firmly within the ideal 3-15 range and feels neither thin nor overloaded.
The surface covers the primary Sales Navigator operations: search, profile views, list CRUD (create/list, and save implies add to list), InMail sending, and export. Minor gaps exist—such as removing leads from lists or updating list metadata—but agents can accomplish most sales workflows without dead ends. The only notable omission is a list-lead enumeration function (e.g., list leads in a specific list), which is a secondary workflow.