"Find candidates with Elixir experience who were rejected over salary" is a filter no ATS interface makes easy, and it is the shape this server is built around — search, summarise, compute, rather than create and update. Pairing it with a charting server turns the statistics side into something you can put in front of people.
A Recruitee server aimed at the analytical end of recruitment data rather than record editing. It searches and filters candidates, assembles pipeline reports, and computes statistics, with prompt templates so the summaries come out consistent across clients.
- Candidate search across skills, status, talent pool, job and tags — including why someone was rejected
- Recruitment summaries: time in each stage, total process duration, stage-by-stage breakdown
- Statistics such as average expected salary for a role type, average time to hire, and contract type splits
- General search over candidates, recruitments and talent pools by name or attribute
- Prompt templates exposed to the client, so the same question yields a comparable summary
- Tool schemas generated from Pydantic models, carrying metadata written for a model to read
Access to Recruitee's Careers Site API. Three transports: stdio for local work, streamable HTTP for deployment, and SSE. A hosted instance runs at https://recruitee-mcp-server.fly.dev/mcp and takes a bearer token — pass it directly if your client supports bearer authorization, or through `mcp-remote` with an `Authorization` header. Self-hosting is on Fly.io with secrets in `.env`. MIT licensed.