
Official HireLayer MCP server: resume & CV parsing, job criteria extraction, candidate matching &
Official HireLayer MCP server: resume & CV parsing, job criteria extraction, candidate matching & ranking, and skills normalization for AI agents in Claude, Cursor, VS Code and Codex. Built for recruiting, ATS and HR tech.
·
Resume parsing, resume scoring and talent pool search for AI agents.
The official Model Context Protocol server for HireLayer. Parse resumes and CVs, turn job descriptions into criteria, score and rank resumes against a job, and search the candidates and jobs you already have, from Claude, ChatGPT, Cursor, VS Code, Codex or any MCP client.
Server URL: https://hirelayer.co/mcp · sign in with your HireLayer account, no API key to copy.
"Screen these 3 resumes against the Senior React job and tell me who to interview."
Your assistant parses each CV, scores every candidate against the job criterion by criterion and explains the shortlist.
Use it to screen applicants in a chat, build a recruiting agent, enrich an ATS, or prototype HR tech features without writing integration code.
https://hirelayer.co/mcp in your AI app, or click a one-click install button above.To try it without your own data, use the sample job and resumes in examples/. The repository ships a .mcp.json: clone it, export HIRELAYER_API_KEY, open the folder in Claude Code and it offers to enable the local server.
Connect to https://hirelayer.co/mcp and sign in to HireLayer. Nothing to install, nothing to keep up to date.
| Client | How to connect |
|---|---|
| Claude (web, desktop, mobile) | Settings → Connectors → Add custom connector, paste the URL, then Connect |
| ChatGPT | Settings → Apps → turn on developer mode, create an app with the URL and OAuth authentication |
| Claude Code | claude mcp add --transport http hirelayer https://hirelayer.co/mcp, then /mcp to sign in |
| Cursor | Click Install in Cursor above, or add { "mcpServers": { "hirelayer": { "url": "https://hirelayer.co/mcp" } } } to ~/.cursor/mcp.json |
| VS Code | Click Install in VS Code above, or add { "servers": { "hirelayer": { "type": "http", "url": "https://hirelayer.co/mcp" } } } to .vscode/mcp.json |
| Codex CLI | codex mcp add hirelayer --url https://hirelayer.co/mcp, then codex mcp login hirelayer |
Clients that cannot sign in with OAuth can send a HireLayer API key instead: Authorization: Bearer your-api-key.
The hosted parse_resume takes a file attached in ChatGPT, a public HTTPS URL, a small file in base64 or the resume text. To parse files from your disk, run the server locally.
Runs on your machine with an API key: sign up, then copy your key from Dashboard → API keys and replace your-api-key below.
claude mcp add hirelayer --env HIRELAYER_API_KEY=your-api-key -- npx -y hirelayer-mcpOpen Settings → Developer → Edit Config and add the server to claude_desktop_config.json:
{
"mcpServers": {
"hirelayer": {
"command": "npx",
"args": ["-y", "hirelayer-mcp"],
"env": { "HIRELAYER_API_KEY": "your-api-key" }
}
}
}Restart Claude Desktop.
Add this to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):
{
"mcpServers": {
"hirelayer": {
"command": "npx",
"args": ["-y", "hirelayer-mcp"],
"env": { "HIRELAYER_API_KEY": "your-api-key" }
}
}
}Add this to .vscode/mcp.json. VS Code asks for your API key and stores it securely:
{
"inputs": [
{ "type": "promptString", "id": "hirelayer_api_key", "description": "HireLayer API key", "password": true }
],
"servers": {
"hirelayer": {
"type": "stdio",
"command": "npx",
"args": ["-y", "hirelayer-mcp"],
"env": { "HIRELAYER_API_KEY": "${input:hirelayer_api_key}" }
}
}
}Add this to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"hirelayer": {
"command": "npx",
"args": ["-y", "hirelayer-mcp"],
"env": { "HIRELAYER_API_KEY": "your-api-key" }
}
}
}codex mcp add hirelayer --env HIRELAYER_API_KEY=your-api-key -- npx -y hirelayer-mcpgemini mcp add -e HIRELAYER_API_KEY=your-api-key hirelayer npx -y hirelayer-mcpAny client that runs stdio MCP servers works with this command and environment variable:
npx -y hirelayer-mcpHIRELAYER_API_KEY=your-api-keyCline users can also ask Cline to install the server: llms-install.md has the steps.
docker build -t hirelayer-mcp .
docker run -i --rm -e HIRELAYER_API_KEY=your-api-key hirelayer-mcpIn Docker, parse_resume only reads files that you mount into the container. Otherwise, pass file_url or resume_text.
| Tool | Product | What it does | Typical input |
|---|---|---|---|
parse_resume | Resume Parser | Parses a resume or CV into structured JSON: contact details, experience, education, languages, skills and the full text, stored under an application_id | A local file_path, a public file_url or the resume_text. Accepts PDF, DOC, DOCX, ODT, RTF, TXT, HTML, Markdown, PPT, PPTX, ODP, XLS, JPG, PNG or BMP files under 4.5 MB. |
extract_job_criteria | Job Criteria Extractor | Turns a job description into the typed criteria it states, each with a requirement (required, preferred or bonus) and a weight from 0 to 3, and stores the job under a job_id | Job description text, at least 30 characters |
score_resumes | Resume Scorer | Scores 1 to 50 resumes against one job, best first: a score from 0 to 1, a verdict, a summary, the required criteria missing and the evidence for each criterion. precise_ranking re-ranks the 10 best with a reason each | The job as job_text (optionally with your own criteria) or a job_id, and each resume as text or an application_id; at least one resume of 30 characters or more |
search_resumes | Talent Pool Search | Finds the stored resumes closest to a job, with optional city, radius and date filters. Proximity only: score the ones worth it with score_resumes | A job_id or job_text |
search_jobs | Job Recommendations | Finds the stored open jobs closest to a resume. Proximity only | An application_id or resume_text |
normalize_skills | Skills Normalizer | Maps free-text skills to taxonomy skills, with their families and domains, named in French or English | Free text, from one skill to a whole skills section |
HireLayer keeps the resumes, jobs and scores in your HireLayer account, as the REST API does, so a resume or a job-resume pair already processed costs nothing the second time and the two searches have something to search. normalize_skills stores nothing. No tool deletes anything or changes your other systems.
Several client companies? Every tool except normalize_skills takes an optional workspace (for example acme-corp), sent as the HireLayer-Workspace header: each client's jobs, resumes and scores stay apart. A new id creates a new workspace; without one, calls use your default workspace.
Upgrading from 1.x: match_candidate and rank_candidates became score_resumes, and resolve_skills became normalize_skills. See the changelog.
The server also ships prompts that clients show as ready-made commands:
| Prompt | What it does |
|---|---|
screen_candidates | Parses the resume files, scores every resume against the job in one call with a precise ranking, and writes a shortlist |
summarize_resume | Parses one resume and writes a recruiter summary |
normalize_skills | Normalizes a skills section and groups it by domain |
flowchart LR
J[Job description] --> S[score_resumes]
R[Resume files] --> P[parse_resume]
P -- application_id --> S
T[Resume texts] --> S
J -. review criteria first .-> C[extract_job_criteria]
C -. job_id .-> S
D[(Your talent pool)] --> Q[search_resumes]
Q -- application_ids --> S
S --> L[Shortlist with evidence]score_resumesTrimmed to one resume and one criterion:
{
"job": {
"job_id": "job_8f14e45fceea167a5a36dedd4bea2543",
"title": "Senior React Developer",
"language": "en"
},
"precise_ranking": true,
"scores": [
{
"rank": 1,
"application_id": "text_c4ca4238a0b923820dcc509a6f75849b",
"reference": "alex-morgan",
"evaluation_status": "completed",
"score": 0.91,
"verdict": "highly_relevant",
"summary": "Strong fit: 8 years of React and TypeScript, team lead, automated testing with Jest and Playwright. Health tech experience to confirm.",
"ranking_reason": "The only candidate who has led a React and TypeScript team in production.",
"required_missing": [],
"to_verify": [],
"criteria": [
{
"criterion_id": "crit_2",
"label": "React experience",
"requirement": "required",
"weight": 3,
"status": "met",
"score": 1,
"evidence": "Lead Front-End Engineer, Medisoft: 'Lead a team of 4 developers on a React 18 + TypeScript appointment platform'",
"explanation": "Over 3 years of React, the last ones leading a team on a production platform."
}
]
}
],
"credits_used": 3
}Criteria, summaries and explanations are written in the job's language (English, French, German, Spanish or Portuguese; English for any other) unless you pass language; evidence quotes the resume in its own language.
Recruiters and hiring managers
~/Downloads/jane-doe.pdf and summarize her experience in five bullet points."~/candidates/ against this job and give me a shortlist table with scores and main gaps."acme-corp), score these resumes against their Product Manager job."Developers and HR tech teams
{ name, email, current_title, skills[] }."Try it now with the sample files
examples/ against examples/job-senior-react-developer.md."| Tool | Credits |
|---|---|
parse_resume | 1 per resume, 0 for a file already stored |
extract_job_criteria | Free (a new text for a job already scored evaluates its scores again, 1 credit each) |
score_resumes | 1 per resume evaluated, 0 for a job-resume pair already scored; 1 more per call with precise_ranking |
search_resumes, search_jobs | 1 per search |
normalize_skills | 1 |
Failed calls and resumes that fail are not charged, and a call refused for lack of credits processes nothing.
| Plan | Credits | Price |
|---|---|---|
| Free | 50 a month | Free, no card required |
| Paid plans | More credits and higher limits | See hirelayer.co/pricing |
parse_resume reads only the file you name. HireLayer stores the resume in your account under its application_id, keeps the original file and returns a link to it in resume.info_resume.url. On the Enterprise plan, set do_not_store_data: true in a call so nothing of the parse is kept.Resumes contain personal data. Use the tools in line with your hiring process and the rules that apply to you, such as GDPR. Scores support human decisions; they don't replace them.
| Variable | Required | Default | Description |
|---|---|---|---|
HIRELAYER_API_KEY | Yes | Your HireLayer API key | |
HIRELAYER_BASE_URL | No | https://hirelayer.co | API base URL, for testing |
| Symptom | Fix |
|---|---|
HIRELAYER_API_KEY is not set | Add the env block with your key to the client config, then restart the client. |
HireLayer API returned 401 | The key is wrong or revoked. Copy it again from Dashboard → API keys. |
HireLayer API returned 403 (insufficient_credits) | You have used your monthly credits. Wait for the reset or upgrade your plan. |
HireLayer API returned 403 (enterprise_plan_required) | do_not_store_data needs the Enterprise plan. Call again without it if storing the resume is fine. |
HireLayer API returned 410 | You run a 1.x version, which calls retired endpoints. Update to the latest version with npx -y hirelayer-mcp@latest. |
| Parsing or scoring seems slow | Parsing usually takes about 30 seconds, and longer for scans that need OCR; scoring 50 resumes takes about a minute. The server sends progress updates so clients don't time out. |
npx not found or an old Node.js | Install Node.js 20 or later from nodejs.org. |
| The file is not found | Use an absolute path, for example /Users/me/Downloads/cv.pdf rather than ~/Downloads/cv.pdf. |
To debug, run the server in the MCP Inspector:
HIRELAYER_API_KEY=your-api-key npx @modelcontextprotocol/inspector npx -y hirelayer-mcpIs HireLayer an ATS? No. HireLayer provides the AI building blocks of recruiting software: resume parsing, scoring and ranking, talent pool search and skills. Use them on their own through MCP, or plug them into your ATS or HR tech product through the REST API.
Which language are the results in?
The text that HireLayer writes (criteria, summaries, explanations and ranking reasons) is in the job's language: English, French, German, Spanish or Portuguese, and English for a job written in another language. Choose it with language (en, fr, de, es or pt). Evidence quotes the resume in its own language. Skills normalization returns French or English labels.
Which resume languages are supported?
The parser detects the main language of each resume and returns it in resume.info_resume.language.
Can I use the REST API directly?
Yes. See the API reference, the OpenAPI spec and llms.txt for agents.
Do I need an API key? Not with the hosted server: you sign in to HireLayer and allow access, and the app's calls use your plan's credits. Each connected app appears as an "(MCP)" key in Dashboard → API keys; revoke it to disconnect the app. The local server uses an API key.
git clone https://github.com/hirelayer/hirelayer-mcp.git
cd hirelayer-mcp
npm install
npm test
HIRELAYER_API_KEY=your-api-key npx @modelcontextprotocol/inspector node dist/index.jsSee CONTRIBUTING.md. Report bugs in GitHub issues and vulnerabilities as described in SECURITY.md.
Pick your client and paste the snippet. Each one is the same server, written the way that client expects it.
claude mcp add hirelayer -- npx -y hirelayer-mcp{
"mcpServers": {
"hirelayer": {
"env": {
"HIRELAYER_API_KEY": ""
},
"args": [
"-y",
"hirelayer-mcp"
],
"command": "npx"
}
}
}code --add-mcp '{"name":"hirelayer","env":{"HIRELAYER_API_KEY":""},"args":["-y","hirelayer-mcp"],"command":"npx"}'[mcp_servers.hirelayer]
command = "npx"
args = ["-y", "hirelayer-mcp"]Runs locally on your device. Your client starts the server itself, so nothing has to be hosted.
Paste this prompt into your agent. It reads this page and does the setup for you.
Read https://aiagentslisting.com/mcp/hirelayer-mcp-server to learn what the "HireLayer MCP Server" MCP server does and how to install it. Add it to my coding agent's MCP configuration as documented on that page, then confirm the server connects and list the tools it exposes.Agents can also browse this directory over MCP at https://aiagentslisting.com/api/mcp
claude mcp add hirelayer --env HIRELAYER_API_KEY=your-api-key -- npx -y hirelayer-mcpdocker run -i --rm -e HIRELAYER_API_KEY=your-api-key hirelayer-mcpThis server runs locally, so we can't read its tool list over the web yet.
We could not run this server: its endpoint did not list its tools to an anonymous client, which usually means it asks for an API key or a sign-in. The four checks that need a live server are left out, and the grade tops out at B until we can read its tools.
Maintain this server? Claiming proves you own the listing and earns the last 4 points.
Claim this listingPaste this line near the top of your repository's README. The badge always renders the current score.
[](https://aiagentslisting.com/mcp/hirelayer-mcp-server)Nothing comparable is listed yet.
v2.1.0Release notesv2.0.0Release notesv1.1.1Release notesv1.1.0v1.1.0: hosted server at hirelayer.co/mcpRelease notesConnect to the AI Agents Listing MCP server at https://aiagentslisting.com/api/mcp using the HTTP transport and complete the sign-in when it asks. Then call the submit_review tool for the listing "hirelayer-mcp-server" with a rating from 1 to 5 and a short note on what worked and what did not.No reviews yet
Be the first to share your experience with this tool.
One email a week. New agents, MCP servers and skills, and what is actually getting traction.