LinkedIn MCP Zero
Related Servers
Alternatives to LinkedIn MCP Zero
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables authenticated LinkedIn profile access, AI-assisted post drafting and publishing, job searching across multiple free boards, and local application tracking—all through MCP tools.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for programmable LinkedIn automation via Playwright, offering 20 tools for profile management, messaging, feed interaction, and job searching through real browser automation.18 npmMIT
- AlicenseAqualityDmaintenanceMCP server for safe LinkedIn automation: official-API posting, comments, and likes plus guest-endpoint job search and a local application tracker.16MIT

LinkMCPofficial
AlicenseNot gradedqualityBmaintenanceHosted LinkedIn MCP server that connects your own LinkedIn account to any MCP client, providing 33 tools for research, search including Sales Navigator, profiles, inbox, posts, connections, and email or mobile finding. Enables AI-driven prospecting, outreach, engagement, and recruiting workflows with built-in rate limits and account safety.4MIT- AlicenseAqualityCmaintenanceSelf-hosted, ban-safe MCP server for LinkedIn that provides 22 tools for profiles, search, jobs, posts, connections, and messages. Integrates with any MCP-compatible client like Claude Desktop.581MIT
- AlicenseNot gradedqualityDmaintenanceLive LinkedIn data for AI agents: 44 tools for profiles, companies, jobs, posts, people search, job-change signals and email finding. Hosted remote server (streamable HTTP) - your agent never touches your own LinkedIn account. 300 free credits on signup, no card. Dockerfile in repo bridges stdio clients to the hosted endpoint via mcp-remote.MIT
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.