linkedin-prospection-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROSPECTION_DIR | No | Path to prospection scripts directory | ./lib/prospection |
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
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_leadsA | 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). |
| score_leadA | Score a LinkedIn lead based on fit (ICP match), intent (burnout signals), and urgency (crisis markers). Returns priority P1-P4 and recommended offer. |
| qualify_leadsA | Score and qualify all unscored leads from the latest search. Uses the rule-based scoring engine (fit + intent + urgency). |
| personalize_messageA | 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). |
| run_pipelineA | 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. |
| get_pipeline_statusA | Get the current state of your LinkedIn prospection pipeline: lead counts by status, invitations sent, DMs sent, acceptance rates, and next actions. |
| manage_leadA | Update a lead's status in the pipeline. Use this to mark leads as contacted, replied, not_interested, or to add notes. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| daily_prospection | Guided daily prospection workflow for LinkedIn lead generation |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| daily-log | Current day's LinkedIn prospection data: leads, invitations, DMs, statuses |
| leads | All leads discovered from LinkedIn search (latest batch) |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/gomessoaresemmanuel-cpu/linkedin-prospection-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server