hh-mcp
Related Servers
Alternatives to hh-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables searching and retrieving job vacancies, resumes, employers, and salary statistics from the hh.ru API (Russia/CIS) via 19 tools, with optional token access for resume search.1967 npm4MIT
- AlicenseAqualityBmaintenanceEnables LLM agents to query and analyze hh.ru job vacancies via full-text and semantic search, with tools for vacancy lookup, skill statistics, market overview, and candidate profile comparison.7MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to search job vacancies, manage resumes, and apply to jobs on HeadHunter (hh.ru), Russia's largest job search platform. Includes OAuth 2.0 integration for secure job applications and an automated vacancy hunter agent with intelligent matching.30MIT
- AlicenseNot gradedqualityFmaintenanceEnables AI assistants to access and manage HeadHunter job platform data, including vacancies, resumes, negotiations, and employer settings via 167+ tools.112 npm5MIT
- FlicenseAqualityDmaintenanceEnables to interact with hh.ru (a Russian job platform) through browser automation, allowing users to search for jobs, manage resumes, apply to vacancies with cover letters, and track application statuses via natural language.93-
- FlicenseNot gradedqualityCmaintenanceEnables searching for jobs in Russia and remote positions from AI assistants using multiple job platforms (hh.ru, Trudvsem, SuperJob, and remote job aggregators).1-
TDQS
Scored across 52 tools
Most tools target a distinct resource+action, and descriptions clarify boundary cases like get_employer_vacancies vs list_active_vacancies. A few similar-sounding statistics and list tools (e.g., get_negotiations_statistics vs get_manager_negotiations_statistics vs get_vacancy_stats) require close reading but are ultimately distinguishable.
The overall verb_noun pattern holds (get_, list_, search_, suggest_), but the use of get_ vs list_ is inconsistent: list operations like get_areas, get_languages, get_employer_vacancy_areas, and get_employer_departments use get_, while others like list_employer_addresses and list_active_vacancies use list_. Names are readable but the convention is not uniform.
At 52 tools, this is a very large surface, far exceeding the 25+ threshold. The breadth of the hh.ru domain justifies more tools than a typical server, but 52 still feels heavy and likely overwhelms agents, especially with many near-duplicate reference-data getters.
The read/search/monitoring surface is remarkably comprehensive: vacancies, resumes, employers, negotiations, templates, suggestions, statistics, and reference data. However, the set lacks any write or mutation tools (no create_vacancy, update_negotiation, send_message, or create_saved_search), leaving common ATS workflow dead ends.