MCP server for LinkedIn prospection automation — find leads, score, qualify, personalize outreach messages, and manage your sales pipeline from any
Linkedin Prospection MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. MCP server for LinkedIn prospection automation — find leads, score, qualify, personalize outreach messages, and manage your sales pipeline from any AI agent.
Once Linkedin Prospection MCP is connected, these are the calls the assistant has available:
find_leads — Search LinkedIn for leads matching burnout/stress signalsscore_lead — Score a single lead (fit 0-30 + intent 0-40 + urgency 0-30 = /100)qualify_leads — Batch qualify leads with P1-P4 priority classificationpersonalize_message — Generate personalized invitation notes and DM sequencesrun_pipeline — Run the full daily prospection pipelineget_pipeline_status — Get current pipeline status and daily logmanage_lead — Update lead status in the pipelineYou will need one environment variable: PROSPECTION_DIR. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
The server ships on npm as linkedin-prospection-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Linkedin Prospection MCP's toolset — find_leads, score_lead, qualify_leads and 4 more — is a fair guide to whether it matches your workflow. It is maintained by gomessoaresemmanuel-cpu; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| find_leads | Search LinkedIn for leads matching burnout/stress signals |
| score_lead | Score a single lead (fit 0-30 + intent 0-40 + urgency 0-30 = /100) |
| qualify_leads | Batch qualify leads with P1-P4 priority classification |
| personalize_message | Generate personalized invitation notes and DM sequences |
| run_pipeline | Run the full daily prospection pipeline |
| get_pipeline_status | Get current pipeline status and daily log |
| manage_lead | Update lead status in the pipeline |
{
"mcpServers": {
"linkedin-prospection": {
"command": "npx",
"args": ["-y", "linkedin-prospection-mcp"],
"env": {
"PROSPECTION_DIR": "/path/to/your/prospection/scripts"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| PROSPECTION_DIR | Filesystem location the server is allowed to use. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.