Best MCP Servers for Recruiting and Hiring in 2026
A recruiter asks an agent which candidates need a follow-up before Friday. The answer lives in the applicant tracking system (ATS), not in the agent’s memory. An MCP server can give the agent a way to search that system and return a source-linked shortlist. Moving a candidate to another stage, sending a rejection, or drafting an offer is a different level of authority.
These six AgentNDX listings connect to specific recruiting platforms. Start with your ATS and inspect permissions before connecting candidate records. Some community listings have unknown health; a directory entry is not a security review.
What to look for
- Your system of record: An agent cannot answer pipeline questions accurately if the server talks to a different ATS or only sees a public job feed.
- Permission boundaries: Candidate search and interview summaries are easier to pilot than stage changes, archival, offers, or messages to applicants. Check the tool list and API scopes, not just the product description.
- Candidate-data handling: Resumes, notes, interview feedback, and protected personal information should be available only to authorized users. Review your vendor’s data policy, retention settings, and the AI client’s handling of tool results.
- Maintenance and setup: Official and community integrations have different support paths. Confirm the repository or vendor instructions, authentication flow, and current availability before installing. Directory commands are starting points, not installation guarantees.
Top MCP servers for recruiting and hiring
1. Workable
Workable is listed as an official integration covering jobs, candidates, pipeline stages, requisitions, offers, and employee records. That breadth helps when a recruiting operations team needs to answer both “Where is this candidate?” and “Which requisition is this role tied to?” It also means the connection may expose more HR data than a narrow candidate-search assistant needs.
Start with read access. Offers and employee records can wait.
Best for: Teams already running recruiting and HR workflows in Workable.
Install: npx @workable/mcp-server (confirm the current vendor setup).
Auth: API key, per directory listing.
2. Ashby MCP
Ashby MCP is listed as an official remote HTTP connection for job postings, candidate pipelines, interview schedules, and hiring analytics. It suits questions such as which interviews are scheduled for a role or where candidates are waiting in the pipeline. The directory describes it as open beta and available across Ashby plans; verify present eligibility and permissions with Ashby before relying on that description.
There is no local install command in the AgentNDX entry. Ashby’s setup information is the better starting point; don’t guess a package name or endpoint.
Best for: Ashby teams pulling recruiting context into an OAuth-capable MCP client.
Connect: Follow Ashby’s current remote MCP setup; no directory install command is listed.
Auth: OAuth, per directory listing.
3. Greenhouse MCP Server
Greenhouse MCP Server is a community project wrapping the Greenhouse Harvest API. Its listing describes job and candidate search, applications, notes, and stage progression. A practical first use is to assemble a review queue with candidate IDs and links back to Greenhouse, leaving hiring-stage changes to the recruiter.
The uncomfortable part: a clone command tells you how to download code, not whether someone still maintains it. AgentNDX marks this entry unverified with unknown health. Review the project and Greenhouse API scopes before granting access to applicant records.
Best for: Greenhouse teams willing to assess and operate a community integration.
Install: git clone https://github.com/alexmeckes/greenhouse-mcp.git && cd greenhouse-mcp && pip install -r requirements.txt (directory command; verify upstream instructions).
Auth: API key, per directory listing.
4. Lever MCP Server
Lever MCP Server is a community listing for candidate search, profile and application lookup, and pipeline operations in Lever. The use case is straightforward: let a recruiter ask for a particular candidate or role, then return the underlying record and status. Archiving a candidate or changing a stage should require separate approval, not follow automatically from a chat summary.
Unknown health, unverified listing. If you cannot audit the tools and their Lever permissions, don’t put applicant data through it.
Best for: Lever users who can maintain a reviewed community connector.
Install: git clone https://github.com/the-sid-dani/lever-mcp-server.git && cd lever-mcp-server && pip install -r requirements.txt (verify upstream instructions).
Auth: API key, per directory listing.
5. Recruitee MCP Server
Recruitee MCP Server lists candidate filtering by skills, status, talent pool, and tags, plus recruiting statistics. That makes it a candidate for questions about an existing pipeline: who is waiting for review, which talent pool contains a particular profile, and what the recorded hiring metrics show. Metrics still need a defined time period and a check against the ATS report.
This one is also unverified with unknown health. Resumes and interview notes are a poor way to discover that a connector has broader permissions than expected.
Best for: Recruitee teams seeking candidate search and pipeline summaries.
Install: git clone https://github.com/appunite/recruitee-mcp-server.git && cd recruitee-mcp-server && pip install -r requirements.txt (verify upstream instructions).
Auth: API key, per directory listing.
6. FastMCP Jobvite
FastMCP Jobvite is a community project exposing Jobvite candidate and job-feed tools. Its directory entry notes configurable tool allow-lists and local stdio or HTTP transport. An allow-list is useful for a recruiting assistant that should look up jobs and candidate records but not receive every action a connector could expose.
Here, active health is recorded, but verification is not. Inspect the repository, limit the tools, and check authentication and network binding before running it. The command below inspects the server; it does not establish a working authenticated Jobvite connection.
Best for: Jobvite teams that want a narrow, reviewable tool surface.
Inspect: git clone https://github.com/evolvconsulting/fast-mcp-jobvite.git && cd fast-mcp-jobvite && uv run --frozen fastmcp inspect src/fast_mcp_jobvite/server.py:create_server.
Auth: API key, per directory listing.
How to choose
Choose by ATS first. Workable and Ashby have vendor-listed connections in the directory; Greenhouse, Lever, Recruitee, and Jobvite entries require closer inspection of community code and maintenance. Do not migrate recruiting data just to use an MCP server. If your ATS has no suitable connector, a scoped API integration may be safer than an unreviewed bridge.
For a first test, compare one read-only answer with the ATS record. Capture its ID, date, and link. Hiring judgments, communications, and offers stay with accountable people.
FAQ
Q: Can an MCP server decide which applicant to hire?
A: It can retrieve records if authorized, but access to data is not authority to make a hiring decision. Treat any summary as material for human review, and check it against the source record and your hiring policy.
Q: Does an AgentNDX listing mean a recruiting server is verified?
A: No. Check the listing’s verification and health fields. Several community entries above are unverified and have unknown health. Independently assess code, permissions, data handling, and current vendor compatibility.
Q: Should I connect my production ATS on day one?
A: Not by default. Inspect the server and client, test with appropriately protected data, scope credentials to the smallest necessary access, and confirm that applicant records will not be exposed to unauthorized users or tools.