hh-mcp-ru
Related Servers
Alternatives to hh-mcp-ru
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.1946 npm4MIT
- AlicenseNot gradedqualityFmaintenanceEnables AI assistants to access and manage HeadHunter job platform data, including vacancies, resumes, negotiations, and employer settings via 167+ tools.83 npm5MIT
- 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
- 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
- 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-

100Hires MCP Serverofficial
AlicenseBqualityFmaintenanceOfficial Model Context Protocol server for 100Hires — the applicant tracking system for recruiting teams. Exposes the full 100Hires API v2 as 130 MCP tools, enabling AI assistants to manage candidates, jobs, applications, interviews, messages, and more.10016 npm1MIT
TDQS
Scored across 14 tools
The discovery cluster (hh_list_sections, hh_get_section, hh_search_methods, hh_map, hh_describe_method) has some conceptual overlap in helping orientation, and hh_add_cabinet vs hh_set_key both write credentials from chat, but each tool has a distinct role. The execution tools (hh_call_method vs hh_call_raw vs hh_fetch_all) are well differentiated by catalog vs arbitrary endpoint vs pagination.
All 14 tools use a consistent hh_ prefix with snake_case verb_noun structure (check_auth, list_sections, get_section, search_methods, describe_method, call_method, fetch_all, list_cabinets, add_cabinet, use_cabinet, remove_cabinet). hh_map is the only noun-only name but fits the otherwise uniform convention.
14 tools sit comfortably in the well-scoped 3-15 range. The set cleanly splits into discovery, execution, and credential-management clusters, each earning its place without redundancy.
Credential lifecycle (list/add/set/use/remove plus auth check) is fully covered, discovery is thorough, and execution handles catalog calls, raw calls, and pagination. Minor gap: no bulk/multi-call orchestration, but core workflows have no dead ends.