The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the HireLayer listing page.
Resume parsing, candidate matching and candidate ranking for AI agents.
The official Model Context Protocol server for HireLayer. Parse resumes and CVs, turn job descriptions into criteria, then score and rank candidates 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, extracts the job criteria, scores every candidate 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.
Open Settings → Developer → Edit Config and add the server to claude_desktop_config.json:
Restart Claude Desktop.
Add this to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):
Add this to .vscode/mcp.json. VS Code asks for your API key and stores it securely:
Add this to ~/.codeium/windsurf/mcp_config.json:
Any 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.
In Docker, parse_resume only reads files that you mount into the container. Otherwise, pass file_url.
| Tool | What it does | Typical input |
|---|---|---|
parse_resume | Parses a resume or CV file into structured JSON: contact details, experience, education, languages, skills and the full text | A local file_path or a public file_url. Accepts PDF, DOC, DOCX, ODT, RTF, TXT, PPT, PPTX, ODP, XLS, JPG, PNG or BMP files under 4.5 MB. |
extract_job_criteria | Turns a job description into weighted criteria: a weight from 1 to 3, a mandatory flag and a rationale for each | Job description text |
match_candidate | Scores one candidate against a job from 0 to 1, with a summary and a status and explanation for each criterion | Job text, resume text and criteria |
rank_candidates | Ranks up to 10 candidates for one job, with a score and a rationale for each | Job text and up to 10 resume texts |
resolve_skills | Maps free-text skills in French or English to taxonomy skills, with their families and domains | Free text, from one skill to a whole skills section |
All tools only read and analyse data. They never change anything in your systems.
The server also ships prompts that clients show as ready-made commands:
| Prompt | What it does |
|---|---|
screen_candidates | Runs the full screening workflow (criteria, parsing, matching) 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 |
match_candidateCriteria labels, rationales, summaries and explanations are written in French. Your assistant translates them when it answers you in another 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."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."Each successful tool call costs 1 HireLayer credit. A rank_candidates call costs 1 credit whatever the number of candidates. Failed calls are not charged.
| 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. By default HireLayer stores the original file and returns a link to it in info_resume.url. Set do_not_store_data: true in a call so the file is not stored.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 | You have used your monthly credits. Wait for the reset or upgrade your plan. |
| Parsing seems slow | Parsing usually takes about 35 seconds, and longer for scans that need OCR. 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:
Is HireLayer an ATS? No. HireLayer provides the AI building blocks of recruiting software: resume parsing, matching, ranking 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 labels and rationales, match summaries and explanations, ranking rationales) is in French; your assistant translates it when it answers in another language. Skills resolution returns French or English labels.
Which resume languages are supported?
The parser detects the main language of each resume and returns it in 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.
See CONTRIBUTING.md. Report bugs in GitHub issues and vulnerabilities as described in SECURITY.md.