job-search-mcp
Related Servers
Alternatives to job-search-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server that aggregates job listings from Remotive and Arbeitnow, with local SQLite caching, application tracking, and saved searches.36 npmMIT
- AlicenseNot gradedqualityDmaintenanceUnified job search MCP server that aggregates live listings from multiple job boards with deduplication, enabling AI agents to find and filter jobs by keyword and location.MIT
- AlicenseBqualityDmaintenanceA fast, secure, and LLM-friendly Model Context Protocol (MCP) server that scrapes job listings from major platforms (LinkedIn, Indeed, Google) and converts them into structured Markdown format.11MIT
- AlicenseAqualityCmaintenanceMCP server that scours job openings from public, ToS-clean sources (Greenhouse, Lever, Ashby, HN, RemoteOK, Adzuna, USAJobs) and provides tools for job search, company listings, and salary context.4MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that provides tools to search and retrieve remote jobs from Remotive's public job board, with no API key required.MIT
- AlicenseNot gradedqualityAmaintenanceMCP server that enables AI assistants to search and normalize job offers from portals like InfoJobs, while keeping the user in control of decisions. It provides read-only tools and respects official APIs and credentials.MIT
TDQS
Scored across 13 tools
The search/research cluster is confusing: portal_suche, mehrportal_suche, portal_recherche, and analysiere_echtes_portal have overlapping purposes, and erstelle_bericht overlaps with portal_recherche in report generation. An agent would struggle to distinguish when to use each.
Tool names mix verb-first (lade_profil, liste_portale) and noun-first (anmeldedaten_hinterlegen, portal_sitzung_loeschen) patterns, with some tools using English terms (portal_login) and inconsistent verb placement. There is no predictable naming convention.
13 tools is within a reasonable range for a job search MCP, but several tools appear redundant (multiple search/report variants), suggesting the count could be trimmed without losing core functionality.
Core workflows like credential storage, login, search, evaluation, and report writing are covered, but there are gaps such as no profile update capability and no clear way to list raw offers separate from evaluation. The presence of a legacy tool (analysiere_echtes_portal) indicates incomplete refactoring.