ati-hh-mcp
Related Servers
Alternatives to ati-hh-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables 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.1996 npm9MIT
- AlicenseBqualityBmaintenanceEnables AI agents to search and retrieve hh.ru vacancies, resumes, employer profiles, salary statistics, ATS/application data, and reference directories across Russia and CIS.5520 npmMIT
- 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.38MIT
- AlicenseNot gradedqualityFmaintenanceEnables AI assistants to access and manage HeadHunter job platform data, including vacancies, resumes, negotiations, and employer settings via 167+ tools.5MIT
- AlicenseNot gradedqualityDmaintenanceExposes iiko restaurant management system REST API as 42+ LLM-callable tools over stdio, enabling natural language interaction with products, employees, orders, payments, OLAP reports, and assembly charts.3MIT
TDQS
Scored across 62 tools
Most tools target a distinct resource+action, but with 62 tools there are several near-pairs that require careful reading: dict_areas vs suggest_areas vs suggest_area_leaves, dict_metro vs dict_metro_city, suggest_positions vs suggest_vacancy_positions vs suggest_professional_roles, and list_negotiations vs list_collection_negotiations. Descriptions do clarify the boundaries (resume-side vs vacancy-side, legacy negotiations vs chats), but an agent can still misselect without close attention.
Names follow a predictable, readable pattern of domain prefix + verb/noun (dict_*, suggest_*, auth_*, chat_*, negotiation_*), with clear verb_noun forms like get_resume, list_chats, send_chat_message, delete_chat_message. Minor deviations exist (e.g. get_me, similar_vacancies, related_vacancies lack a domain prefix, and auth_get_login_url mixes prefix and verb), but the overall scheme is coherent.
62 tools far exceeds the 3-15 sweet spot and makes the surface hard for an agent to navigate; many niche dictionary/suggest endpoints could be consolidated or lazily exposed. Each tool does map to a real hh.ru endpoint, so it is not arbitrary bloat, but the count is still excessive for practical selection.
Coverage is broad across dictionaries, OAuth, negotiations, and chats (including message CRUD, file uploads, and participant management), so core workflows are reachable. However, key lifecycle operations are missing: resumes and vacancies are read-only (no create/update/publish), and applicant-side/employer-side applicant search tools are absent, leaving notable gaps.