Headcount Labs MCP Server

Count the current jobs matching the filters, without listing them. No account needed. To answer "which companies are hiring for X", pass group_by: "employer": the answer then also has employers (the top 25 by number of matching jobs, each with employer_name, company_id and jobs), employers_from_jobs (how many matching jobs were grouped, at most 1,000, taken in the default list order), employers_sampled (true when more jobs matched than were grouped, so the counts are from a sample) and employers_unknown_jobs (grouped jobs with no known employer name).

Ask a question about Headcount Labs (filters, limits, MCP setup, errors) and get the best-matching sections of the headcountlabs.com docs, each with its URL. Free, and works without an account.

Find the search_jobs filters and the job fields that match some keywords, with each one's type and a short description. Pass words such as ["pay", "remote"]; no keywords lists everything. kind is filter (pass it in search_jobs filters) or field (a property of each returned job; postings[].x is a property of each linked posting). A field state is an object whose state says whether the source published the value (known), Atlas derived it, the source omitted it, or extraction failed. Free.

Get a job by its job_id, including every linked posting and its links. No account needed. Use fields to select top-level job properties; job_id is always included.

Search current job postings by keyword, title, company, place, pay, date and more. No account needed. Call list_fields (free) to find the filter names. Country and employment_type accept comma-separated values or arrays and match any listed value. Pages return up to 25 jobs (limit, default 10); pass next_cursor as cursor to see the next page. One search shows up to 100 jobs in total, so narrow it with filters to find the right ones; count_jobs tells you how many jobs match without listing them. sort is relevance (best match) or updated (most recently updated). Each job has its employer, title, locations, pay with its period, dates, and the posting link in postings[].posting_url and postings[].application_url. Use fields to select top-level job properties; job_id is always included. Each job's description is cut to its first 400 characters (description_truncated: true); pass descriptions: "full" for the whole text of every job, or call get_job for one job. For job titles, title matches the words as one phrase in that order, so "senior software engineer" misses "Software Engineer, Senior"; title_advanced matches words in any order with AND, OR and NOT, for example senior AND ("software engineer" OR "software developer"), and usually finds more.

Answer job-market questions from a precomputed snapshot of current US jobs, rebuilt after each full pass over the job boards and checked by recomputing sample answers a second way. Ten ready-made questions (top employers, pay, remote share, top metros, jobs by state, top roles, new postings this week, pay transparency, posting age, employers hiring in the most states) plus a generic lookup of any metric (job count, pay 10th to 90th percentile, share showing pay, remote/hybrid/in-person shares, posting age, new postings, top employers) by one or two dimensions (title, place, company, seniority, employment type, remote), a breakdown that ranks one dimension, a negotiate question ("what salary should I ask for?" for a title, a place and an optional seniority) and a dimensions call that lists what can be asked. Cells with fewer than 30 jobs, and pay figures from fewer than 30 jobs with pay, are left out; every answer carries its sample size, as_of, a one-line method, the check result and search filters for search_jobs or count_jobs. Free.