Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words Sign in

LinkedIn Sales Navigator

by nick-choudharyversion 1.2.0i★ 2iRuns on your computerRepository ↗
Registry nameio.github.nick-choudhary/linkedin-sales-nav-mcp

How to install

What it does

LinkedIn Sales Navigator contact and account search from your logged-in browser.

  • Connects Runs on your computer
  • Account or key No key needed
  • Category Marketing & social media

Use together with

Skills that teach the AI this kind of work; they work alongside this one

scroll-world

A skill that turn any brand into a scrollable 3D world landing page

by oso95★ 11,0651 skills

Skill · How-to guide

social-auto-upload

自动化上传视频到社交媒体:抖音、小红书、视频号、tiktok、youtube、bilibili

by dreammis★ 16,698 (whole repo)4 skills

Skill · How-to guide

native-subtitle-quote-image

保留视频内嵌字幕,精确取帧并生成 3:4 社交长图的 Agent Skill

by chengyi-ai★ 2,8911 skills

Skill · How-to guide

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity6/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score18/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install LinkedIn Sales Navigator. Follow https://mcp.popnx.com/i/nick-choudhary-linkedin-sales-nav-mcp.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 13, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server LinkedIn Sales Navigator for Claude on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "linkedin-sales-nav": { "command": "uvx", "args": [ "linkedin-sales-nav-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the LinkedIn Sales Navigator tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  3. Paste these settings and save the file

    {
      "mcpServers": {
        "linkedin-sales-nav": {
          "command": "uvx",
          "args": [
            "linkedin-sales-nav-mcp"
          ]
        }
      }
    }
  4. Quit Claude and open it again

  5. Try it

    Use LinkedIn Sales Navigator and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using LinkedIn Sales Navigator or shows a LinkedIn Sales Navigator tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect LinkedIn Sales Navigator yet

LinkedIn Sales Navigator runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect LinkedIn Sales Navigator

  • Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • Install Python (uv) on your computer first (one time)
  • Install Python (uv) on your computer first (one time)
  • Install Python (uv) on your computer first (one time)

B · Others in Marketing & social media that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

Install Python (uv) on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server LinkedIn Sales Navigator for Claude Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user linkedin-sales-nav -- uvx linkedin-sales-nav-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the LinkedIn Sales Navigator tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  3. Paste this command and press Enter

    claude mcp add --scope user linkedin-sales-nav -- uvx linkedin-sales-nav-mcp
  4. Type /mcp in Claude Code

    You should see LinkedIn Sales Navigator listed as connected

  5. Try it

    Use LinkedIn Sales Navigator and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using LinkedIn Sales Navigator or shows a LinkedIn Sales Navigator tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

Install Python (uv) on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server LinkedIn Sales Navigator for Cursor on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "linkedin-sales-nav": { "command": "uvx", "args": [ "linkedin-sales-nav-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the LinkedIn Sales Navigator tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  3. Open the AI chat in Cursor in Agent mode

  4. Try it

    Use LinkedIn Sales Navigator and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using LinkedIn Sales Navigator or shows a LinkedIn Sales Navigator tool in the answer, you are connected

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

Install Python (uv) on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server LinkedIn Sales Navigator for VS Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "linkedin-sales-nav": { "type": "stdio", "command": "uvx", "args": [ "linkedin-sales-nav-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the LinkedIn Sales Navigator tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install uv (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    uv --version
    • A version number such as uv … = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required

    Open the uv download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version

    Install once; it works for everything that needs uv

  2. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  3. Open the AI chat in VS Code in Agent mode

  4. Try it

    Use LinkedIn Sales Navigator and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using LinkedIn Sales Navigator or shows a LinkedIn Sales Navigator tool in the answer, you are connected

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use LinkedIn Sales Navigator💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user linkedin-sales-nav -- uvx linkedin-sales-nav-mcp

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "linkedin-sales-nav": {
      "command": "uvx",
      "args": [
        "linkedin-sales-nav-mcp"
      ]
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "linkedin-sales-nav": {
      "command": "uvx",
      "args": [
        "linkedin-sales-nav-mcp"
      ]
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "linkedin-sales-nav": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "linkedin-sales-nav-mcp"
      ]
    }
  }
}

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
21/wk
Connection
Runs on your computer
Latest versioni
1.2.0
Published to registryi
Aug 20, 2026
Code last changedi
Nov 11, 2026
Maker
nick-choudhary
Packages
pypi: linkedin-sales-nav-mcp
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 20, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account nick-choudhary, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 9 days ago

  • ✓ Pass

    Has a licence

    Uses MIT

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for linkedin-sales-nav-mcp@1.2.0

Checks only this package version, not every dependency · checked Nov 15, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/nick-choudhary-linkedin-sales-nav-mcp.svg)](https://mcp.popnx.com/en/servers/nick-choudhary-linkedin-sales-nav-mcp)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Marketing & social mediai

  • More stars than 91% of the other 4243 servers in this category
  • Published to the registry more recently than 20% of the other 4243 servers in this category
  • Basic checks equal to or better than 99% of the other 4243 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is LinkedIn Sales Navigator safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 9 days ago, and the latest version (1.2.0) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Relaticle, ChatbotX, X (Twitter) MCP Server by Xquik, Betterlytics, BibiGPT YouTube Video Summarizer

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

ChatbotX

Omnichannel customer messaging, CRM contacts, flows, sequences, broadcasts, and AI automation.

by ChatbotXIOGrowing★ 1.1K Stars for the whole repoUpdated 14 days ago

Runs in the cloud✓ service owner · chatbotx.io

Betterlytics

Query your Betterlytics web analytics from AI agents: traffic, funnels, journeys, errors, uptime.

by betterlyticsGrowing★ 196Updated 4 months ago

Runs in the cloud✓ service owner · betterlytics.io
Compared with similar ones
This one
LinkedIn Sales Navigator
RelaticleChatbotXX (Twitter) MCP Server by XquikBetterlyticsBibiGPT YouTube Video Summarizer
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyNoNoNoNoYesNo
Add with + in ClaudeNoNoNoNoNoNo
Basic checks3/34/44/44/44/44/4
LicenseMITAGPL-3.0NOASSERTIONMITAGPL-3.0MIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

LinkedIn Sales Navigator MCP Server

MCP server that gives AI assistants (Claude Desktop, Claude Code, any MCP client) access to LinkedIn Sales Navigator contact and account search — by driving a real, logged-in browser on your machine and capturing Sales Navigator's own search API responses.

Why this design (and why not cookie-replay)

The common approach — copy your li_at + JSESSIONID cookies and replay them as HTTP requests from a server — gets you logged out repeatedly. LinkedIn scores each session on IP, browser fingerprint, TLS, and the full cookie set; two replayed cookies from a different machine look like a hijacked session, so it invalidates them.

This server does the opposite. It keeps a persistent browser profile you log into once, by hand, and then lets that genuine session do the work:

MCP client (Claude) ──stdio/HTTP──> this server ──drives──> your logged-in Chromium ──> Sales Navigator

│ captures the JSON the browser itself receives (page.on "response")

Every request to LinkedIn originates from the real browser: your IP, your fingerprint, your full cookie jar, browser-generated CSRF/track headers, and the session is refreshed by the browser as normal. Nothing is replayed or reconstructed. That is what keeps you signed in.

We never automate the login itself — typing credentials is a strong bot signal. You sign in manually once; the profile persists.

Tools

ToolWhat it does
search_contactsPeople/lead search from a Sales Navigator URL. Navigates + paginates in the browser, saves records to SQLite, returns a small progress summary.
search_accountsCompany/account search from a Sales Navigator URL. Same, for accounts.
enrich_leadsAdd Open Profile / InMail status to a saved contact search. By default (method="compose") it opens each lead's message panel and also records contact info and insights (recent posts, job change, shared connections). Opt-in and resumable — see Open Profile status.
fetch_lead_profilesDepth 3: full profiles for drafting (~15 KB/lead). Opt-in via ENABLE_PROFILE.
get_lead_profileRead one stored full profile. Local only, no LinkedIn call.
pipeline_statusOne funnel view: scraped → enriched → open → profiled → sent.
reconcile_outreachSettle sends stuck in sending against LinkedIn itself.
run_outreach_batchDraft and send for several leads in one call via MCP sampling. Same guards; dry_run defaults true.
outreach_nextLive session: walks the search results, opens the next eligible lead's message panel from its row, captures it, and returns the lead's data to draft from. Non-Open-Profile leads and existing conversations are skipped automatically. mode: draft, supervised (30 s countdown) or auto (5 s).
outreach_submitFills the open panel with the draft. draft mode saves it; otherwise a banner in the page counts down with Skip / Send now / Pause, and whatever the panel holds at zero (edits included) is re-checked and sent through the same two-phase commit, cap and dedupe as send_message.
outreach_skipCloses the open panel without sending and records why.

What is code and what is model in a live session. Everything that can be decided from data is decided in code, before any tokens are spent: the ICP screen (FIT_RULES_FILE, applied before a panel is opened, so a rejected lead costs no LinkedIn request either), Open Profile and existing-thread checks, trimming the lead to a fixed budget (summary, current role, three recent posts), and the company block — LinkedIn's own Account IQ dossier boiled down to priorities, challenges, revenue model, workforce and news, or TinyFish news (TINYFISH_API_KEY) when the dossier is empty. The offer is sent once per session, not per lead. The model only writes the message. | check_replies | Read the inbox and mark leads who answered. Sends nothing. | | next_outreach_batch | Leads eligible for a first message — Open Profile first, anyone already contacted excluded. Read-only. | | send_message | Send ONE message. The only tool that writes to LinkedIn: off by default, dry_run=true by default. | | outreach_status | Counts by status and channel, plus remaining daily cap. | | check_session_status | Reports whether the browser profile has a live Sales Navigator session (tells you if you need to re-run --login). | | list_queries | Every saved search with its progress: url_hash, status, last_page, records_count. | | get_results | Pull a bounded slice (1–200) of a saved query's records into the conversation for analysis. | | export_results | Write a saved query's records to JSON and/or CSV under the output folder. |

Both search tools take a full Sales Navigator URL (build the search in the UI, copy it from the address bar) and a pages count (1–10, 25 results each).

Beyond tools, the server exposes one resource (sales-nav://queries — saved queries and their progress as attachable JSON context) and one prompt (sales_nav_search_workflow — the step-by-step prospecting playbook, for clients that support MCP prompts).

Search tools do not return the records

This is deliberate, and it is the thing most likely to surprise you. Records go to SQLite; the tool returns only a status object, so a 250-row scrape doesn't dump 250 rows into the model's context:

{

"url_hash": "a6ca46c9365bce93", "scraper_type": "contacts", "status": "paused", // new | in_progress | paused | complete "new_records_this_call": 25, "total_records": 25, "total_available": 11897313, "pages_fetched": 1, "last_page": 1, "next_page": 2, // null once exhausted "raw_dir": null, // set when include_raw=true "suggestion": "Saved 25 records so far (through page 1) ..." }

To get at the data, call get_results (a sample) or export_results (files), or read the SQLite database directly.

Pipeline depth

How far a query is taken is a property of the query, not of the call that made it, so a run resumed tomorrow knows what the search was collected for.

DepthEndpointsCost per leadGate
searchlead searchone page per 25always on
open_profile+ enrich_leads~240 BENABLE_ENRICH (default on)
full+ fetch_lead_profiles~15 KBENABLE_PROFILE (default off)
search_contacts(url, pages=4, depth="open_profile")

Depth is stored on the query and echoed back with a next_step. Requesting a depth the server has not enabled is refused with an explanation rather than silently downgraded, so a default install cannot be pointed at a list and made to pull thousands of full profiles.

enrich_leads and fetch_lead_profiles hit the *same* endpoint with different projections, and stay separate on purpose: the screen runs across a whole list to find who is free to message, the full fetch runs only for the leads you are about to write to. Merging them would pull heavy payloads for leads you never contact — and would make "recent activity" as stale as the screen.

Sending messages

This is the only capability that writes to LinkedIn, and it is treated differently from everything else here. Reading looks like a person browsing; a burst of messages looks like exactly what it is, and the consequence lands on your account rather than on the code. So every default is the cautious one:

GuardDefault
ENABLE_SENDINGfalse — a fresh install cannot message anyone
dry_runtrue — returns the exact draft, sends nothing
ALLOW_CREDIT_SPENDfalse — refuses anything that costs an InMail credit
SEND_DAILY_CAP40, rolling 24h, across all campaigns
SEND_DELAY_MIN/MAX45–120s between sends
Free vs paid, and why enrichment comes first

Open Profile members can be messaged without spending an InMail credit; everyone else costs one from a finite monthly budget. The compose window states which it is — "Free to Open Profile" versus "Use 1 of N credits" — and the sender reads that line, records the channel, and refuses the paid path unless you have explicitly allowed it.

That is why enrich_leads matters commercially and not just as metadata: next_outreach_batch returns only confirmed Open Profile leads by default, so the free channel is the path of least resistance.

Never twice

Outreach state lives in lead_outreach, keyed on (member_id, campaign), and the exclusion is global: anyone with a sent row in *any* campaign is filtered out of every future batch. Dedupe elsewhere in this server saves a wasted request; here it prevents messaging the same human twice because two searches happened to find them. member_id is the only identifier stable across searches, which is why it is the key.

State is committed per send, never per batch — a crash must not leave a message delivered on LinkedIn but unrecorded here.

The offer file stays yours

The server never generates copy and never learns what you sell. Your positioning lives in a Markdown file that is gitignored and not packaged:

cp offer.example.md offer.md    # then edit it

echo "OFFER_FILE=./offer.md" >> .env

The sales_nav_compose_message prompt renders that file together with the lead record and the drafting rules; your MCP client's model writes the message. With no offer file configured the prompt refuses to render at all.

The evidence gate

The drafting model must return the record fields it drew on:

{"subject": "...", "body": "...", "evidence_used": ["positions[0].title", "companyName"]}

Every entry is resolved against the lead record actually fetched. Name a field that does not exist and the message is rejected unsent. It is a cheap, deterministic check that "personalized" means grounded in data we really have — a message claiming a conference talk gets rejected because nothing supports it. Empty evidence_used is also rejected: that is a template, not personalization.

Unattended batches

Everywhere else the split is deliberate: the server decides *who*, your client's model decides *what to say*. That needs a human-driven turn — fine at a desk, useless on a schedule.

run_outreach_batch closes the gap with MCP sampling. The server asks your client for each draft (ctx.sample), so no model runs here, no API key lives here, and no copy is generated by this process — only a request for one.

Nothing is relaxed for automation. Every draft goes through the same send path as a hand-written one: the evidence gate, global dedupe, the daily cap, the free-channel-only default, two-phase commit. dry_run still defaults to true. A draft that fails to parse or fails validation is recorded and skipped rather than sent or allowed to end the run, and the batch stops early when the cap is reached.

run_outreach_batch(url_or_hash, campaign="q3", limit=5)  # d

Only the beginning is shown; read the rest in the repo