LinkedIn MCP Zero
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LINKEDIN_MCP_ENABLE_PATCHRIGHT_FALLBACK | No | Set to 'true' to enable opt-in Patchright fallback when CDP is unavailable. |
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": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_jobsA | Search real-time public LinkedIn job listings without authentication. Returns deduplicated jobs with:
|
| search_jobs_multiA | Search multiple public job boards (LinkedIn, Indeed, Glassdoor, ZipRecruiter) simultaneously. |
| get_job_detailsA | Get full public LinkedIn job details including full description, salary, skills, and applicant count. |
| get_company_jobsA | Get real-time public job listings for a specific hiring company. |
| get_company_profileB | Get public company profile signals including headcount trends and hiring velocity. |
| search_companiesC | Search hiring companies from public job market signals. |
| get_job_salaryB | Extract structured salary and compensation data from public job details. |
| get_job_trendsA | Get hiring trends, demand velocity, and top demanded skills by role/location. |
| get_industry_insightsB | Get public market insights and hiring demand for an industry vertical. |
| search_jobs_advancedB | Advanced public LinkedIn job search with company filtering, date sorting, and relevance scoring. |
| analyze_resumeA | Parse resume PDF/DOCX/text locally into structured skills, experience, and contact info without external calls. |
| get_resume_insightsB | Get resume skill gaps, strengths, and suggestions with optional client LLM reasoning. |
| tailor_resumeC | Universal multi-role ATS resume tailoring, keyword optimization, and real-time gap analysis across 9 industry disciplines. |
| match_jobs_to_resumeB | Rank public jobs against a saved resume using TF-IDF and cosine skill similarity with optional LLM reasoning. |
| compare_jobsA | Compare 2-5 public LinkedIn jobs on requirements, skills, seniority, and viability. |
| export_jobsB | Export public job details to a local CSV, JSON, or Excel file. |
| analyze_job_viabilityB | Assess hiring viability, applicant saturation, and ghost-job probability based on public signals. |
| expand_skill_clusterA | Explore technology ecosystems and related skills via in-process knowledge graph. |
| save_job_alertB | Save a recurring public job search alert to local database. |
| get_saved_alertsA | List all saved job alerts and their last check timestamps. |
| check_saved_alertsA | Run saved alerts against live LinkedIn search and report newly discovered matches. |
| get_engine_statusC | Show available engines. |
| get_helpC | Show tool documentation. |
| get_usage_statsB | Show recent local MCP usage and token estimates. |
| get_tool_usage_summaryB | Show local aggregate MCP usage by tool. |
| reset_usage_statsC | Reset local usage metrics. |
| smart_match_jobsB | AI-powered job matching using the client's LLM for deep reasoning and fit explanation. |
| generate_cover_letterB | Generate a tailored, compelling cover letter (max 200 words) using the client's LLM. |
| analyze_salary_offerC | AI-powered salary analysis using real market data and client's LLM. |
| personalized_job_huntB | Interactive job search that asks you what matters most via MCP elicitation. |
| confirm_exportB | Export jobs with interactive user confirmation dialog. |
| get_resume_insights_advancedC | Get advanced AI-powered insights on a resume using LLM reasoning. |
| deep_industry_analysisC | Full industry analysis with real-time progress updates across active job postings. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| daily_job_digest | Generate a daily job search digest. |
| company_deep_dive | Full intelligence report on a company. |
| career_path_advisor | AI career advisor based on real LinkedIn data. |
| interview_prep | Prepare for an interview using public LinkedIn data. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| saved_alerts_resource | Your saved job alerts as a live resource. |
| engine_status_resource | Engine health — always available as context. |
TDQS
Scored across 33 tools
Several clusters contain near-duplicates whose boundaries require careful reading: search_jobs vs search_jobs_advanced vs search_jobs_multi, get_resume_insights vs get_resume_insights_advanced, and get_industry_insights vs deep_industry_analysis. The descriptions do differentiate them (filters, multi-board, progress updates), so an agent can disambiguate, but misselection risk remains real. Utility tools (get_engine_status, get_help, get_usage_stats, get_tool_usage_summary) also blur into each other.
The dominant pattern is snake_case verb_noun (search_jobs, get_job_details, generate_cover_letter, save_job_alert), applied across most of the 33 tools. A handful deviate from verb-first form — personalized_job_hunt, deep_industry_analysis, confirm_export — and the advanced/basic suffixing is inconsistent, but overall the convention is predictable and readable.
33 tools is heavy for a job-search server and includes marginal entries like get_help, get_engine_status, reset_usage_stats, and two separate usage-summary tools. The core workflow (search, detail, resume, match, export) could be expressed in roughly half the surface. The volume increases selection cost more than it adds capability.
Coverage is broad: search (basic/advanced/multi-board), job and company detail, salary, trends, alerts, resume parsing/tailoring/matching, comparison, export, and viability analysis form a coherent lifecycle. Gaps are minor — no bookmarking of individual jobs or application tracking — but these are reasonable given the public, unauthenticated scope.