huntflow-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Порт HTTP-сервера (по умолчанию 3000) | 3000 |
| HUNTFLOW_TOKEN | Yes | API-токен (Настройки → API) | |
| HUNTFLOW_BASE_URL | No | По умолчанию https://api.huntflow.ru/v2. Для международного аккаунта — https://api.huntflow.ai/v2 | https://api.huntflow.ru/v2 |
| HUNTFLOW_USER_AGENT | No | Заголовок User-Agent (HuntFlow его требует). Дефолт huntflow-mcp/<версия> (+repo); рекомендуется указать контактный email |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_accountsB | List of available HuntFlow accounts. |
| list_vacanciesC | List of vacancies (open/all), with pagination. |
| get_vacancyC | Full information about a vacancy. |
| list_applicantsA | Account applicants filtered by vacancy and/or status (stage). Pagination: page, count≤30. For "applicants for vacancy X" pass vacancy. |
| search_applicantsC | Text search for applicants (name/email/resume). Pagination: page, count≤100. The q parameter actually filters results. |
| get_applicantC | Full applicant card (external[], links[]). |
| get_applicant_resumeA | Applicant resume (CV) with body. external_id is taken from get_applicant → external[].id. |
| list_stagesC | Recruitment funnel stages (vacancy statuses): code → name. |
| list_rejection_reasonsC | Directory of rejection reasons: code → name. |
| list_account_sourcesA | Applicant resume sources (e.g. "RG", "HeadHunter"): id → name/type. Use the numeric id for create_applicant → externals[].account_source and update_applicant_external. |
| list_applicant_commentsB | Comments about an applicant (log, by default only type=COMMENT). Pagination page/count≤100. |
| add_applicant_commentA | Add a comment to an applicant (WRITE operation: creates a log entry; it cannot be edited or deleted via the API). |
| create_applicantA | Create an applicant card (WRITE operation: POST /applicants). first_name+last_name are required. Resume — as text (externals[].data.body) and/or file IDs from upload_resume. Repeating creates a DUPLICATE (no idempotency) — check doubles[] in the response. |
| attach_applicant_to_vacancyA | Attach an applicant to a vacancy and place them on a funnel stage (WRITE operation). vacancy + status (stage ID from list_stages) are required. For rejection — rejection_reason; for hiring — fill_quota + employment_date. |
| upload_resumeA | Upload a resume file (WRITE operation: multipart). Source: file_path (local path) OR content_base64+file_name. parse=true parses the CV (returns text/fields/photo). Put the id from the response into create_applicant → externals[].files / photo. |
| update_applicant_externalA | Update an EXISTING resume (external) of an applicant (WRITE operation: PUT). Set the source (account_source from list_account_sources), resume text (body) and/or files. external_id comes from get_applicant → external[].id. NOTE: there is no API to ADD a new resume to an applicant created without one — attach the resume at creation via create_applicant → externals[]. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| skill-applicants | Applicants for a vacancy — show all applicants attached to the specified vacancy. |
| skill-vacancy-stats | Vacancy statistics — funnel, timing, conversion. |
| skill-vacancy-analytics | Vacancy analytics: days in progress, applicants at customer-facing stages, timing of CV submission to the client. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Gaivoronsky/huntflow-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server