mcpbeat Sign in

WhatJobs Job Search MCP Server

by whatjobs-mcp Your server? Claim it
answering

WhatJobs Job Search is answering right now. Last checked 9 min ago. It exposes 7 tools.

Search live WhatJobs jobs, salaries and hiring companies in 25 countries from AI assistants.

Uptime history 47 hours of history
47 hours agonow
100.0%
Uptime 24h
91 of 91 checks
7
Tools
read from the server
176 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check WhatJobs Job Search every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add job-search --transport http https://mcp.whatjobs.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.whatjobs.com/mcp
~/.codex/config.toml
[mcp_servers.job-search]
url = "https://mcp.whatjobs.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "job-search": {
      "url": "https://mcp.whatjobs.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "job-search": {
      "type": "http",
      "url": "https://mcp.whatjobs.com/mcp"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

compare
compare_job_counts
Compare how many jobs are live on WhatJobs right now across places and/or roles. Use this when the user asks where the most jobs are, how much demand there is, or to compare cities or roles, e.g. "Where are the most data analyst jobs in Germany?", "More jobs for nurses or carers in Leeds?", "Paris vs Berlin for developers". Inputs: - keywords: one or more job roles (may be [""] to count all jobs). - locations: one or more places to search, not the user's own location unless they ask about jobs near them. Up to 6 keyword x location combinations are compared. - market: optional. Leave empty to let each location use its own country (so "Paris" and "Berlin" compare France and Germany). Each row includes a link to that search on WhatJobs.
compare_salaries
Compare what a job pays across places, or what different jobs pay in one place, from the salaries in current WhatJobs listings: the typical range and median for each, side by side. Use this when the user wants pay compared, e.g. "Nurse salary in London vs Manchester", "Do developers earn more in Berlin or Munich?", "Which pays more in Toronto, accountant or bookkeeper?". Inputs: - keywords: one or more job roles only (e.g. ["nurse"], or ["accountant", "bookkeeper"]). - locations: one or more places to compare (city, region or country), not the user's own location unless they ask about jobs near them. - market: optional. Leave empty to let each location use its own country (so "Paris" and "Berlin" compare France and Germany). Supported values: uk (United Kingdom), us (United States), ca (Canada), de (Germany), in (India), pk (Pakistan), br (Brazil), es (Spain), ae (United Arab Emirates), mx (Mexico), ar (Argentina), za (South Africa), at (Austria), au (Australia), be (Belgium), bh (Bahrain), cl (Chile), co (Colombia), cr (Costa Rica), ch (Switzerland), do (Dominican Republic), dz (Algeria), ng (Nigeria), nl (Netherlands), fr (France). Up to 4 role x place combinations are compared. Each row is in that country's own currency (amounts are not converted between currencies) and says its pay period (per year in most countries). Each row links to that search on WhatJobs.
jobs
search_jobs
Search WhatJobs for public job listings using separate structured search fields. Use this tool only when the user is looking for jobs, vacancies, roles, internships, work opportunities, or asks to see more job results. The location is the job search location requested by the user, such as a city, region, country, or remote preference. It is not the user's current physical location unless the user explicitly asks to search near them. Inputs: - keyword: the job role, job function, skill, or industry only. - location: the city, region, country, or remote preference only. - market: optional. The country market for the search. If omitted it is inferred from location (e.g. "Johannesburg, South Africa" -> za). Supported values: uk (United Kingdom), us (United States), ca (Canada), de (Germany), in (India), pk (Pakistan), br (Brazil), es (Spain), ae (United Arab Emirates), mx (Mexico), ar (Argentina), za (South Africa), at (Austria), au (Australia), be (Belgium), bh (Bahrain), cl (Chile), co (Colombia), cr (Costa Rica), ch (Switzerland), do (Dominican Republic), dz (Algeria), ng (Nigeria), nl (Netherlands), fr (France). - chunk_number: the result batch number. Use 1 for the first search and increment when the user asks to see more. Do not include the location inside keyword. Do not include filler words like jobs, vacancies, roles, hiring, in, near, around, at, or within in keyword. Examples: - sales in Bracknell -> keyword="sales", location="Bracknell", market="uk" - software engineer jobs near Manchester -> keyword="software engineer", location="Manchester", market="uk" - driver jobs in Toronto -> keyword="driver", location="Toronto", market="ca" - nurse jobs in Berlin -> keyword="nurse", location="Berlin", market="de" - teacher jobs in Sao Paulo -> keyword="teacher", location="Sao Paulo", market="br" - chef jobs in Madrid -> keyword="chef", location="Madrid", market="es" - accountant jobs in Dubai -> keyword="accountant", location="Dubai, United Arab Emirates", market="ae" - marketing jobs in Mexico City -> keyword="marketing", location="Mexico City, Mexico", market="mx" - developer jobs in Buenos Aires -> keyword="developer", location="Buenos Aires, Argentina", market="ar" - sales jobs in Johannesburg -> keyword="sales", location="Johannesburg, South Africa", market="za" - comptable à Paris -> keyword="comptable", location="Paris", market="fr" - nurse jobs in Sydney -> keyword="nurse", location="Sydney", market="au" - verpleegkundige in Amsterdam -> keyword="verpleegkundige", location="Amsterdam", market="nl" - engineer jobs in Zurich -> keyword="engineer", location="Zürich", market="ch" - marketing jobs in Vienna -> keyword="marketing", location="Wien", market="at" - accountant jobs in Lagos -> keyword="accountant", location="Lagos", market="ng" Returns structured job listings with title, company, location, salary when provided, posted date, summary, description, apply URL and pagination metadata for the WhatJobs widget UI.
latest
search_latest_jobs
Show only recently posted WhatJobs listings for a role and place, newest first. Use this when the user asks for new, fresh, recent or today's jobs, e.g. "Any electrician jobs posted today in Manchester?" or "New marketing jobs this week in Madrid". Inputs: - keyword: the job role only. - location: the place to search (city, region or country), not the user's own location unless they ask for jobs near them. - posted_within_days: 1 for today/yesterday, 7 for this week (default), up to 30. - market: optional country code; if empty it is inferred from location. Supported values: uk (United Kingdom), us (United States), ca (Canada), de (Germany), in (India), pk (Pakistan), br (Brazil), es (Spain), ae (United Arab Emirates), mx (Mexico), ar (Argentina), za (South Africa), at (Austria), au (Australia), be (Belgium), bh (Bahrain), cl (Chile), co (Colombia), cr (Costa Rica), ch (Switzerland), do (Dominican Republic), dz (Algeria), ng (Nigeria), nl (Netherlands), fr (France). The result includes a link to all matching jobs on WhatJobs.
match
match_jobs_to_profile
Find WhatJobs listings that fit a person's background: searches up to 4 target job titles at once and ranks the jobs by how well the title matches and how many of their skills each listing mentions. Use this when the user shares their CV, experience or skills and asks what jobs suit them, e.g. "Here's my CV, what should I apply for in Manchester?". Inputs: - job_titles: 1-4 job titles that fit the person (you choose them from what they shared). - skills: up to 10 key skills or tools (e.g. "Python", "SQL", "forklift licence"). - location: where they want to work (the place to search). - market: optional country code; if empty it is inferred from location. Supported values: uk (United Kingdom), us (United States), ca (Canada), de (Germany), in (India), pk (Pakistan), br (Brazil), es (Spain), ae (United Arab Emirates), mx (Mexico), ar (Argentina), za (South Africa), at (Austria), au (Australia), be (Belgium), bh (Bahrain), cl (Chile), co (Colombia), cr (Costa Rica), ch (Switzerland), do (Dominican Republic), dz (Algeria), ng (Nigeria), nl (Netherlands), fr (France). Pass only titles and skills. Never pass CV text, names, contact details or other personal data. The result includes a link to all matching jobs on WhatJobs.
salary
get_salary_insights
Show what a job pays, from the salaries in current WhatJobs listings: typical range, median, lowest and highest, plus a few listings with salaries. Use this when the user asks how much a role pays or earns, salary ranges, or whether a salary is good, e.g. "How much does a nurse earn in Paris?" or "Data analyst salary in London". Inputs: - keyword: the job role only (e.g. "nurse", "software engineer"). - location: the place to search (city, region or country), not the user's own location unless they ask for jobs near them. May be empty for the whole country. - market: optional country code; if empty it is inferred from location. Supported values: uk (United Kingdom), us (United States), ca (Canada), de (Germany), in (India), pk (Pakistan), br (Brazil), es (Spain), ae (United Arab Emirates), mx (Mexico), ar (Argentina), za (South Africa), at (Austria), au (Australia), be (Belgium), bh (Bahrain), cl (Chile), co (Colombia), cr (Costa Rica), ch (Switzerland), do (Dominican Republic), dz (Algeria), ng (Nigeria), nl (Netherlands), fr (France). Figures are in the country's own currency, for the pay period most listings use (per year in most countries, per month in some); the result says which. The result includes a link to all matching jobs on WhatJobs.
top
get_top_hiring_companies
List the companies posting the most jobs for a role and place right now on WhatJobs, with their job counts and example listings. Use this when the user asks who is hiring, which companies or employers have openings, or the biggest employers for a role, e.g. "Who's hiring software engineers in Berlin?". Inputs: - keyword: the job role only. - location: the place to search (city, region or country), not the user's own location unless they ask for jobs near them. - market: optional country code; if empty it is inferred from location. Supported values: uk (United Kingdom), us (United States), ca (Canada), de (Germany), in (India), pk (Pakistan), br (Brazil), es (Spain), ae (United Arab Emirates), mx (Mexico), ar (Argentina), za (South Africa), at (Austria), au (Australia), be (Belgium), bh (Bahrain), cl (Chile), co (Colombia), cr (Costa Rica), ch (Switzerland), do (Dominican Republic), dz (Algeria), ng (Nigeria), nl (Netherlands), fr (France). Counts come from the latest 50 listings. The result includes links to each company's listings and to all matching jobs on WhatJobs.

Endpoints

URLTransportStateLatencyChecked
https://mcp.whatjobs.com/mcp streamable-http answering 192 ms 9 min ago

Alternatives to WhatJobs Job Search

same job, measured the same way
R
Remote Dev Jobs
by angelnikolov

Live remote frontend, backend and Java developer jobs: search, salaries, hiring companies.

answering
Arihaan Jobs
by arihaan

Live job postings from employer career sites: search, count and compare jobs and companies.

answering
aitrainer.work AI training jobs
by aitrainer

Search open AI training and RLHF jobs from 20+ platforms, with pay, countries and hiring stats.

6 tools answering
Voxjobs (Portugal)
by voxs

Job listings in Portugal: search, salary statistics, comparables and companies.

6 tools answering
Naukri Jobs Scraper
by saulius876-lgtm

Search Naukri.com jobs in India: titles, companies, salaries, skills, and which companies hire most.

answering
Inblog
by inblog

Run your company blog for SEO and AI search from your AI assistant.

answering
HeadStart Jobs
by sarthakjain004

Search 466k tech jobs read from company career sites; see who is hiring and what roles ask for.

8 tools answering
Codealive MCP
by codealive-ai

Semantic code search and analysis from CodeAlive for AI assistants and agents.

local only

WhatJobs Job Search — questions

Answers built from our own checks of this server.

What can WhatJobs Job Search do?
It exposes 7 tools, read directly from the server on our last check. Among them: compare_job_counts, compare_salaries, get_salary_insights, get_top_hiring_companies, match_jobs_to_profile, search_jobs and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is WhatJobs Job Search working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 176 ms. The bar chart above shows every period we have measured.
How do I connect WhatJobs Job Search?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does WhatJobs Job Search need an API key?
No. WhatJobs Job Search completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is WhatJobs Job Search?
It answers our handshake in 176 ms on average, which is faster than 77% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.