Log inSubmit server
Huntflow MCP logo

Huntflow MCP

Connects AI clients to Huntflow ATS for vacancies, applicants, resumes, recruiting stages, and account reference data.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Huntflow MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "huntflow-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/huntflow-mcp"
      ],
      "env": {
        "HUNTFLOW_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 4 tools correctly (6d ago).

Overview

The huntflow-mcp MCP server connects AI clients to the Huntflow ATS API for vacancy, applicant, resume, and recruiting reference data. It runs through stdio or streamable HTTP, using Huntflow access credentials and optional automatic token refresh. Its 14 tools support searching candidates, reading resumes, inspecting stages, and retrieving account directories, while two prompts provide applicant and vacancy statistics views. Reach for it when an agent needs to answer recruiting questions from Huntflow without exporting data manually.

Use cases

  • Search candidates across Huntflow vacancies
  • Read an applicant’s external resume
  • List candidates by recruitment stage
  • Inspect vacancy funnel statistics
  • Retrieve Huntflow recruiting reference data

Key features

  • 14 Huntflow ATS data and directory tools
  • Applicant, vacancy, and resume retrieval
  • Vacancy and applicant filtering with pagination
  • Automatic access-token refresh with persisted state
  • Stdio and streamable HTTP transports
  • Two recruiting analysis prompts

Tools4

What Huntflow MCP lets your agent do. Expand a tool for its parameters.

Verified live~367 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

5/5 checks healthy over the last 39d

What it can do

From the 4 tools this server returned when we ran it.

Read-only tools · 4
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age201 days
Maintainers1

Observed 2026-10-17 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 7d ago via OSV.dev · @theyahia/huntflow-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads117Package downloads in the last 30 days.
Last commit1mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed4Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Huntflow MCP works

What the huntflow-mcp MCP server does

The huntflow-mcp MCP server exposes Huntflow ATS data through the Model Context Protocol. It covers vacancies, applicants, external resumes, recruitment stages, account users, and several Huntflow reference directories. The server is intended for AI clients that need to retrieve recruiting information conversationally or use structured results in an agent workflow.

Its read-oriented tool set includes vacancy listing and detail retrieval, applicant search, vacancy-specific applicant lists, candidate profiles, and resume access. It also provides account, coworker, stage, source, rejection-reason, division, and tag lookups. Two prompts are included: one organizes applicants for a vacancy into a table with stage information and a summary, while the other produces vacancy funnel, timing, and conversion statistics.

How it works

The server authenticates requests against the Huntflow API v2. HUNTFLOW_TOKEN supplies the access token. When a refresh token is also configured, the client can exchange it after an authorization failure and save the rotated token pair to a state file, allowing the refreshed credentials to persist across restarts.

Two transport modes are documented. In stdio mode, an MCP client launches the package with npx. In streamable HTTP mode, the process listens for MCP requests at /mcp and exposes /health; the default bind address is 127.0.0.1:3000, with the port configurable. HTTP access can also be protected with a bearer secret when HUNTFLOW_HTTP_SECRET is set.

List operations accept pagination through page and count. They normally return a selected set of fields together with structuredContent; callers can request the complete API response with raw: true.

Setup and configuration

Install the package through the documented npx command and add it to an MCP client configuration, such as Claude Desktop. Set HUNTFLOW_TOKEN to an access token created in Huntflow’s API token settings. Adding HUNTFLOW_REFRESH_TOKEN, which lasts about fourteen days, enables automatic renewal; without it, the server stops working when the access token expires.

Optional settings control the token-state file, API base URL, user agent, request timeout, client-side rate limiting, HTTP port and host, HTTP authorization, and allowed hosts. The default request timeout is 10,000 milliseconds, the default API endpoint is https://api.huntflow.ru/v2, and the client-side request limit is 10 requests per second unless disabled.

Tools and capabilities

The 14 tools are:

  • List accounts, vacancies, stages, coworkers, sources, rejection reasons, divisions, and tags.
  • Retrieve complete vacancy and applicant records.
  • Search applicants by text and vacancy, status, or tag filters.
  • List applicants attached to a specific vacancy.
  • List a candidate’s external resumes and retrieve a specific resume body.

Vacancy listing supports opened, state, and mine filters. The applicant search accepts a query plus vacancy, status, and tag filters.

Limitations and notes

The server requires a valid Huntflow access token, and the API requires a user agent; the package supplies a default unless overridden. A refresh token is optional, but omitting it means credentials must be replaced after access-token expiration. HTTP mode binds locally by default, and remote exposure requires deliberate host and authorization configuration.

The huntflow-mcp MCP server documents data retrieval and lookup tools rather than write operations such as creating vacancies, editing candidates, or moving applicants between stages. Its provided tools should therefore be evaluated primarily for reading Huntflow recruiting data and generating summaries from it.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Huntflow MCP

huntflow-mcp is an MCP server that connects AI clients to the Huntflow ATS API. Its main tools list and inspect vacancies, search applicants, retrieve candidate profiles and external resumes, and access stages, coworkers, accounts, and reference directories. It also provides prompts for applicant summaries and vacancy funnel statistics.

Install it with npx by configuring the package as an MCP server in Claude Desktop, or run it with the documented streamable HTTP command. Smithery installation is also supported through the Smithery CLI. Provide the required Huntflow access token through the environment.

Only HUNTFLOW_TOKEN is required. HUNTFLOW_REFRESH_TOKEN enables automatic access-token renewal, while HUNTFLOW_TOKEN_FILE controls where the rotated credentials are saved. Other optional variables configure the API URL, timeout, HTTP listener, authorization secret, and host restrictions.

Yes, automatic refresh requires HUNTFLOW_REFRESH_TOKEN in addition to HUNTFLOW_TOKEN. After the access token expires or a 401 response occurs, the server refreshes the credentials through Huntflow and stores the rotated pair in the configured token file. Without a refresh token, a new access token is needed after expiration.

It documents standard stdio and streamable HTTP MCP transports, so compatibility depends on the client’s support for those transports and its MCP configuration format. Claude Desktop is the client explicitly shown in the installation example.

Related MCP servers

All in Workplace & Productivity All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewHuntflow MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/huntflow-mcp?style=directory)](https://allmcps.com/mcp/huntflow-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/huntflow-mcp"><img src="https://allmcps.com/api/badge/huntflow-mcp?style=directory" alt="Huntflow MCP on AllMCPs" /></a>