Huntflow MCP server

huntflow-mcp

An MCP server for the Huntflow ATS: vacancies, candidates, resumes and hiring stages through an AI agent instead of clicking through cards

MCP serverRussian stack

theyahia/huntflow-mcpAuthor:theYahia

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/huntflow-mcp

Detects the agents on your machine, checks the risk and pins the version.

Other ways to install

Run in a terminal

claude mcp add --transport stdio --env 'HUNTFLOW_TOKEN=<your HUNTFLOW_TOKEN>' huntflow -- npx -y @theyahia/huntflow-mcp

Or add to the file .mcp.json, in the project

{
  "mcpServers": {
    "huntflow": {
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/huntflow-mcp"
      ],
      "env": {
        "HUNTFLOW_TOKEN": "<your HUNTFLOW_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

HUNTFLOW_TOKENsecret, required
HUNTFLOW_REFRESH_TOKENsecret, optional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Install in Cursor

The button opens the agent and offers to add the server. If nothing happens, copy the config below.

Add to the file ~/.cursor/mcp.json, for all projects

{
  "mcpServers": {
    "huntflow": {
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/huntflow-mcp"
      ],
      "env": {
        "HUNTFLOW_TOKEN": "<your HUNTFLOW_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.

Keys and settings

HUNTFLOW_TOKENsecret, required
HUNTFLOW_REFRESH_TOKENsecret, optional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Install in VS Code

The button opens the agent and offers to add the server. If nothing happens, copy the config below.

Run in a terminal

code --add-mcp '{"name":"huntflow","type":"stdio","command":"npx","args":["-y","@theyahia/huntflow-mcp"],"env":{"HUNTFLOW_TOKEN":"<your HUNTFLOW_TOKEN>"}}'

Or add to the file .vscode/mcp.json, in the project

{
  "servers": {
    "huntflow": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/huntflow-mcp"
      ],
      "env": {
        "HUNTFLOW_TOKEN": "<your HUNTFLOW_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the servers key.

Keys and settings

HUNTFLOW_TOKENsecret, required
HUNTFLOW_REFRESH_TOKENsecret, optional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Run in a terminal

codex mcp add huntflow --env 'HUNTFLOW_TOKEN=<your HUNTFLOW_TOKEN>' -- npx -y @theyahia/huntflow-mcp

Or add to the file ~/.codex/config.toml, for all projects

[mcp_servers.huntflow]
command = "npx"
args = ["-y", "@theyahia/huntflow-mcp"]
env = { HUNTFLOW_TOKEN = "<your HUNTFLOW_TOKEN>" }

If the file already exists, append the block to the end.

Keys and settings

HUNTFLOW_TOKENsecret, required
HUNTFLOW_REFRESH_TOKENsecret, optional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.gemini/settings.json, for all projects

{
  "mcpServers": {
    "huntflow": {
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/huntflow-mcp"
      ],
      "env": {
        "HUNTFLOW_TOKEN": "<your HUNTFLOW_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

HUNTFLOW_TOKENsecret, required
HUNTFLOW_REFRESH_TOKENsecret, optional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.config/devin/mcp_config.json, for all projects

{
  "mcpServers": {
    "huntflow": {
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/huntflow-mcp"
      ],
      "env": {
        "HUNTFLOW_TOKEN": "<your HUNTFLOW_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.

Keys and settings

HUNTFLOW_TOKENsecret, required
HUNTFLOW_REFRESH_TOKENsecret, optional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Formerly Windsurf.

Add to the file cline_mcp_settings.json, for all projects

{
  "mcpServers": {
    "huntflow": {
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/huntflow-mcp"
      ],
      "env": {
        "HUNTFLOW_TOKEN": "<your HUNTFLOW_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.

Keys and settings

HUNTFLOW_TOKENsecret, required
HUNTFLOW_REFRESH_TOKENsecret, optional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file .roo/mcp.json, in the project

{
  "mcpServers": {
    "huntflow": {
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/huntflow-mcp"
      ],
      "env": {
        "HUNTFLOW_TOKEN": "<your HUNTFLOW_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

HUNTFLOW_TOKENsecret, required
HUNTFLOW_REFRESH_TOKENsecret, optional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

A fork of Roo Code, same .roo folders.

Add to the file opencode.json, in the project

{
  "mcp": {
    "huntflow": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@theyahia/huntflow-mcp"
      ],
      "environment": {
        "HUNTFLOW_TOKEN": "<your HUNTFLOW_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcp key.

Keys and settings

HUNTFLOW_TOKENsecret, required
HUNTFLOW_REFRESH_TOKENsecret, optional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.config/zed/settings.json, for all projects

{
  "context_servers": {
    "huntflow": {
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/huntflow-mcp"
      ],
      "env": {
        "HUNTFLOW_TOKEN": "<your HUNTFLOW_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the context_servers key.

Keys and settings

HUNTFLOW_TOKENsecret, required
HUNTFLOW_REFRESH_TOKENsecret, optional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file .codeassistant/mcp.json, in the project

{
  "mcpServers": {
    "huntflow": {
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/huntflow-mcp"
      ],
      "env": {
        "HUNTFLOW_TOKEN": "<your HUNTFLOW_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

HUNTFLOW_TOKENsecret, required
HUNTFLOW_REFRESH_TOKENsecret, optional

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

You will need: Node.js

Checked against the repository on Sep 25, 2026, commit 11b3f3e.

Text for your agent

Create a token in the API Tokens section of Huntflow settings, set the HUNTFLOW_TOKEN and HUNTFLOW_REFRESH_TOKEN variables, then connect the server with npx -y @theyahia/huntflow-mcp in your MCP client config.

Other ways from the author

{
  "mcpServers": {
    "huntflow": {
      "command": "npx",
      "args": ["-y", "@theyahia/huntflow-mcp"],
      "env": {
        "HUNTFLOW_TOKEN": "ваш-access-token",
        "HUNTFLOW_REFRESH_TOKEN": "ваш-refresh-token"
      }
    }
  }
}

Config from the README for Claude Desktop.

Security check

How we review

Low riskWe rate an entry low when it mostly gives the agent instructions and reference material.

All tools are read-only, no changes are made in Huntflow
The token grants access to candidates' personal data, keep it secret

This is third-party code. Review the repository files before installing.

What it does

The server talks to the Huntflow API using an access and refresh token and gives an agent 14 read tools: account listing, vacancies filtered by status or ownership, a vacancy card, candidate search and per-vacancy candidate lists, a candidate card, their resumes, hiring pipeline stages, coworkers, and reference lists for sources, rejection reasons, divisions and tags. Two Claude Code skills show candidates for a vacancy as a table and pipeline statistics. The server refreshes the access token automatically on expiry and saves the rotated pair to a state file so it survives restarts.

Who it is for. For recruiters and HR managers running hiring in Huntflow who want vacancy and candidate summaries through an agent.

Good fit when

You want to quickly see which candidates are stuck at a given pipeline stage
You need vacancy statistics: timing, conversion, candidate counts
You want to read a candidate's resume without opening the Huntflow interface

Not a fit when

You need to create vacancies, move candidates between stages or change other data: all 14 tools are read-only
Your company does not use Huntflow

Example request

Show me which candidates for this vacancy are stuck at the technical interview stage in Huntflow

MCP

Transport: stdio, http
Authentication: API key

Environment variables

HUNTFLOW_TOKEN required, secret: Huntflow API access token.
HUNTFLOW_REFRESH_TOKEN secret: Refresh token for automatic renewal on expiry.

Limitations

The project has a single author and is part of the WWmcp series. All tools are read-only; the server cannot write to Huntflow. The access token lasts about a week and the refresh token about two weeks; without a refresh token, access must be renewed manually. A client-side 10 requests-per-second limit can be turned off via an environment variable.

How to disable. Remove the huntflow server from your MCP client config.

FAQ

What happens if only the access token is set without a refresh token?

The server works until the access token expires, about a week, and then a new token is needed.

Can the server move a candidate to a different stage?

No, all 14 tools only read vacancy, candidate and reference data.

MCP servers

Salesforce DX MCP Server

Official

Salesforce's official DX MCP server: work with orgs, metadata, data, users and Apex tests from your agent

MCP serverHigh risk483

Yandex Kit skills for store management

kit-skills

Official

Yandex's official skill set: catalog, prices, stock, orders, storefront and a weekly checkup for a Yandex Kit store, through Claude Code or Codex

PluginHigh risk28

YouGile MCP by Indalo

YouGile MCP

Editors’ pick

Full 65-operation YouGile API coverage with configurable permissions, write confirmation and a shared company rate limit

MCP serverHigh risk

Bitrix24 portal MCP server

MCP-сервер портала Битрикс24

Official

Bitrix24's official per-portal MCP: an external agent uses OAuth or a token to read and change tasks, deals, meetings and mail

MCP serverHigh risk

README in short

The Russian README describes configs for Claude Desktop, Streamable HTTP and installation via Smithery, gives a table of 11 environment variables and 14 tools, noting that list tools return a trimmed field set to save tokens with a raw flag for the full response. It separately covers the token auto-refresh mechanism and two Claude Code skills. Part of the same author's WWmcp series.

Install

Security check

What it does

Good fit when

Not a fit when

Example request

MCP

Environment variables

Limitations

FAQ

Related

Salesforce DX MCP Server

Yandex Kit skills for store management

YouGile MCP by Indalo

Bitrix24 portal MCP server

README in short