find_leads
Search LinkedIn for leads posting about burnout, stress, or exhaustion. Uses Playwright to scrape LinkedIn posts matching burnout keywords. Requires an active LinkedIn session (run setup-session first).
LABSCO SUMMARY
The targeting signal is people publicly describing burnout, and that is worth being clear-eyed about before deciding to run it.
Mechanically this is a competent pipeline — scoring separated into fit and intent, qualification applied in bulk, status tracked by stage, and the whole thing runnable on a schedule. What distinguishes it from any other outreach automation is who it looks for: the tool searches for people posting about exhaustion and stress, which means the automation is pointed at people at a low moment. Whether that is legitimate depends entirely on what you are offering them and how, and it is a judgement to make deliberately rather than by installing a pipeline. Also worth noting: automated connection requests at volume are against LinkedIn's terms and are what account restrictions are for.
What it is
A daily outreach pipeline for LinkedIn: it searches for leads by a stated signal — posts about burnout, stress or exhaustion — scores and qualifies them, generates personalised messages, and runs the whole sequence on a schedule.
What you get
- find_leads searches LinkedIn for people posting about burnout, stress or exhaustion — the targeting criterion is stated plainly in the tool itself.
- score_lead rates a lead on fit against an ideal customer profile, on intent from those signals, and qualify_leads applies the rules across everything unscored from the latest search.
- personalize_message generates the invitation note or direct message for a specific lead.
- run_pipeline triggers the full daily sequence — find, then send invitations — as one call.
- get_pipeline_status reports lead counts by stage, and manage_lead moves a lead's status as it progresses.
Requirements
PROSPECTION_DIR for local state. The pipeline sends real connection requests and messages to real people on a schedule once triggered.
Setup effort
One command — npx -y linkedin-prospection-mcp
USE CASES
01
Seeing where the pipeline stands
Read lead counts by stage rather than a total, and move individual leads as they progress.
02
Scoring a list you already have
Rate leads on fit and intent separately, and apply the rules across everything unscored in one pass.
03
Writing to one person
Generate the invitation note or message for that specific lead rather than sending a template.
04
Running the whole sequence
Trigger the daily pipeline — find then send — knowing it contacts real people automatically once started.
7 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get_pipeline_status
Get the current state of your LinkedIn prospection pipeline: lead counts by status, invitations sent, DMs sent, acceptance rates, and next actions.
manage_lead
Update a lead's status in the pipeline. Use this to mark leads as contacted, replied, not_interested, or to add notes.
personalize_message
Generate a personalized LinkedIn invitation note or DM for a specific lead. Returns a message ready to copy-paste (max 200 chars for invitations, longer for DMs).
qualify_leads
Score and qualify all unscored leads from the latest search. Uses the rule-based scoring engine (fit + intent + urgency).
run_pipeline
Trigger the full daily prospection pipeline: find leads → send invitations → check acceptances → send DMs. Uses the daily-orchestrator.js script. Can skip lead search with skip_leads=true.
score_lead
Score a LinkedIn lead based on fit (ICP match), intent (burnout signals), and urgency (crisis markers). Returns priority P1-P4 and recommended offer.
BEFORE YOU INSTALL
What to know first
Tools you get
7 tools when we connected.
Requires
- npx on PATH
- PROSPECTION_DIR in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 7 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"linkedin-prospection": {
"command": "npx",
"args": [
"-y",
"linkedin-prospection-mcp"
],
"env": {
"PROSPECTION_DIR": "<YOUR_PATH_TO_PROSPECTION>/scripts"
}
}
}
}npx
TERMINAL
npx -y linkedin-prospection-mcp
