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
- 1 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The server reads candidate resumes and profiles with a Huntflow token, which is personal data
- Refreshes the access token on its own with the refresh token
- There are no tools that write to Huntflow
Install
- Works in
- Services
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/huntflow-mcpDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The server reads candidate resumes and profiles with a Huntflow token, which is personal data
- Refreshes the access token on its own with the refresh token
- There are no tools that write to Huntflow
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 HuntflowMCP
- Transport
- stdio, http
- Authentication
- API key
Environment variables
HUNTFLOW_TOKENrequired, secret- Huntflow API access token.
HUNTFLOW_REFRESH_TOKENsecret- 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.
Discussion
No questions or reviews yet.
Related
MCP serversMCP server that searches job boards and the career sites of 41,000 companies on Workday, Greenhouse, Lever and other ATS.
SuperJob MCP server
superjob-mcp
An MCP server for the SuperJob job site: vacancies, employers, cities and professions through an AI agent
Attio MCP Server: Attio CRM for Claude and ChatGPT
Attio MCP Server
An MCP server for Attio CRM: companies, people, deals, tasks, lists and notes through 19 universal tools
A remote MCP server with B2B data: companies, contacts and work addresses inside the chat, browser sign-in, no API keys
MCP server for the amoCRM (Kommo) API v4: leads, contacts, companies, tasks, pipelines, unsorted inbox and analytics
Planfix MCP server with prompts and resources
Planfix MCP Server
A Python Planfix MCP server: tasks, projects, contacts and reports, plus ready MCP resources and planning prompts
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.