Summary
Job search with the filters people actually screen on.
Salary range, years of experience, visa support and remote status are parameters rather than things to read past, so an agent can narrow a list without scraping a board. The API key is optional, which makes it cheap to try before deciding it belongs in a workflow.
What it is
An MCP server over the HireBase job API, with two tools: run a filtered job search, and fetch a single posting by its HireBase ID.
What you get
- Search on keywords, including and, or and not keyword sets, plus title, category, company, country and city (search_jobs)
- Filters for salary range and currency, years of experience, visa support and location type (search_jobs)
- One job's full detail retrieved by ID (get_job)
- A candidate-profile prompt that turns a name, LinkedIn URL, personal website and resume text into a structured search brief
Requirements
Uv, then uvx hirebase-mcp. A HireBase API key is optional: the documented config leaves HIREBASE_API_KEY empty.
Setup effort
One command plus a key — uvx hirebase-mcp, then supply credentials