search_jobsLABSCO 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 — uvx hirebase-mcp
USE CASES
01
Finding roles that match a resume
Turn the candidate details into a brief, then search on the titles and keywords it produces.
02
Screening on pay before reading postings
Set the salary floor and currency and only look at what clears it.
03
Checking whether a company is hiring in a city
Filter by company and location, including remote.
04
Reading one posting in full after a shortlist
Fetch the job by its ID once the search has narrowed things down.
2 tools
Listed in project docs. Your client may show a different list.
get_jobBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Requires
uvx on PATH
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
uvx hirebase-mcpMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"hirebase": {
"command": "uvx",
"args": [
"hirebase-mcp"
],
"env": {
"HIREBASE_API_KEY": ""
}
}
}
}
