LinkedIn Jobs Feed MCP Server
Related Servers
Alternatives to LinkedIn Jobs Feed MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents and MCP clients to search live LinkedIn job postings by role, location, recency, salary, recruiter, and company details, returning structured rows with full descriptions and metadata. It connects to a hosted endpoint with OAuth or token authentication and requires no LinkedIn account, cookies, or API access.MIT
- FlicenseNot gradedqualityDmaintenanceEnables job search on LinkedIn through MCP tools, including keyword and location search, filtering by remote, easy apply, experience level, job type, and date, and retrieving job details.-
- AlicenseAqualityCmaintenanceEnables users to search LinkedIn's public job listings with advanced filters like location, salary, and experience level. It allows MCP-compatible clients to retrieve real-time job opportunities without requiring LinkedIn authentication or API keys.12MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to search LinkedIn job, internship and work-study listings and to turn Job IDs or LinkedIn URLs into complete offer details such as title, company, location, contract type, applicant count, direct apply link and full description, all without a LinkedIn account or API key.MIT
- AlicenseNot gradedqualityAmaintenanceSearches LinkedIn for job posts, filters out non-vacancies and out-of-market roles, and provides a local dashboard to triage and rate the remaining openings.1ISC
- AlicenseNot gradedqualityDmaintenanceProvides tools for automating LinkedIn job post search and management. Job opportunities often appear in LinkedIn posts first, before they're posted on traditional job boards. By monitoring LinkedIn posts, you can discover opportunities earlier and get a competitive advantage in your job search.20 npm7ISC
TDQS
Scored across 1 tool
With only one tool there is no possibility of misselection; its purpose (keyword+location LinkedIn job search with employer domain enrichment) is stated unambiguously. An agent cannot confuse it with anything else in the set.
The single name `search_linkedin_jobs` follows a clean snake_case verb_noun pattern with a clear platform qualifier. There is no competing convention to clash with.
One tool is thin for a server, even though the tool itself is extremely feature-dense (filters, dedup state, enrichment). The scope is narrow enough that a single entry point is defensible, but it sits at the borderline of 'too few tools'.
Search covers a lot of ground, but the surface is a single operation: there is no fetch-by-job-id for detail refresh, no company/employer lookup tool, and no way to page or resume beyond the coarse only_new state. Agents can work around this, but the lifecycle is not fully covered.