huntflow-mcp
Related Servers
Alternatives to huntflow-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server for SuperJob.ru API that enables searching for vacancies, employers, and reference data like towns and professions.525 npmMIT
- AlicenseNot gradedqualityDmaintenanceLocal MCP server for safe automation of job application responses on hh.ru using the user's Chrome session.13 npmMIT
- AlicenseAqualityAmaintenanceMCP server for VK Ads API: manage ad plans, ad groups, banners, and statistics.2288 npm9MIT
- AlicenseNot gradedqualityNot gradedmaintenanceMCP server for Altegio API — appointments, clients, services, staff schedules1-

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.10015 npm1MIT- FlicenseNot gradedqualityDmaintenanceMinimal MCP server for integrating with amoCRM (API v4): manage deals, contacts, notes, and OAuth2 authentication.12-
TDQS
Scored across 16 tools
Each tool has a distinct purpose: listing sources, accounts, vacancies, applicants, stages, rejection reasons, comments; getting details; creating/appending data. No two tools overlap in functionality, and descriptions clearly differentiate similar operations like list_applicants vs search_applicants.
All tool names follow a consistent verb_noun pattern in snake_case, using verbs like list, get, search, add, create, attach, upload, update. No mixing of conventions, making it predictable for agents.
16 tools cover the core recruitment workflow: accounts, vacancies, applicants, resumes, comments, stages, and rejection reasons. This is well-scoped for an ATS integration, not excessive nor sparse.
Coverage includes listing and creating applicants, uploading resumes, and attaching to vacancies, but missing updates for applicants and vacancies, no deletion operations, and no way to add a resume post-creation. These are notable gaps that could cause agent failures.