Job search MCP servers in 2026 compared: JobSpy, Indeed, Himalayas, Remoet

The first thing everyone built when agents got the ability to call tools was a firehose. Plug your agent into eight job boards, let it pull thousands of listings at machine speed, hand the pile to you. The pitch was "AI-powered job search." What you actually got was the same problem you already had, except now it arrives faster and there is more of it.

I run Remoet, which is one of the things on this list, so read accordingly. But I have connected my own agent to most of these, and the honest version of the landscape is more useful to you than another vendor ranking itself first. The existing comparisons out there are mostly written by data companies, and they all happen to conclude that the data company won. So here is the map without that particular thumb on the scale.

Updated October 6, 2026. New this month: the at-a-glance table below, and the Remoet section now reflects that searching it needs no key. The other entries were last re-checked in September 2026.

At a glance

The details, and the catches, are below.

The firehose: JobSpy MCP server

JobSpy is the open-source scraper everyone builds on, and the JobSpy MCP server is one of the more established ways to hand it to an agent. It scrapes across the big boards (LinkedIn, Indeed, Glassdoor, ZipRecruiter, Google Jobs, and a few regional ones), filters by title, location, posting date and remote status, and hands your agent structured results. Free. No account. Run it locally and point Claude at it.

Two practical notes. The MCP wrapper is a community project rather than an official one, and there are half a dozen forks of it, so check the last commit date on whichever you pick. And "run it locally" means Node plus Python plus JobSpy itself, which is more setup than a remote server you paste a URL for.

If you want everything, this is everything. That is also the catch. JobSpy does not have an opinion about which of those thousands of jobs is worth your attention, because it cannot. It is a pipe. The judgment is still entirely yours, and "read every listing on the internet, but through an agent" is not actually a smaller job than it was before. For a lot of people that is fine. If you are casting the widest possible net and you trust yourself to sort it, start here.

The one that logs in as you: LinkedIn MCP Server

LinkedIn MCP Server is the popular open-source answer to "most of the jobs are on LinkedIn anyway." It drives a real browser session, either by importing cookies from your logged-in browser or walking you through a fresh login, and gives your agent profile lookups, company pages, job search, job details, and now your LinkedIn inbox and messages too. Free, Apache-licensed, very actively maintained.

The caveat is the author's own, stated right in the README: LinkedIn's user agreement prohibits automated access, and accounts using automated tools can be restricted or banned. This is you automating your own account against the platform's wishes, with no guarantee of safety. Plenty of people accept that trade with their eyes open. Just know it is the trade, because no marketing page will tell you.

The official board connectors: Indeed and Himalayas

Two job boards now run connectors you do not have to install in the traditional sense.

Indeed is in Claude's connector directory. You add it from the directory page, sign in with your Indeed account, and your agent gets Indeed's inventory. It is the largest catalogue on this list by a wide margin, and the integration is four tools deep: job search, job detail, company data and your resume. No applying, no pipeline of your own. It is also Claude-only by Indeed's own framing, so it is a directory listing rather than a server you can point any client at.

Himalayas runs a remote-only job board with an MCP server at https://mcp.himalayas.app/mcp, and it was the first server here that needed no account at all to search: connect and call it. I checked, and an unauthenticated client can list its tools and run a job search straight away. Signing in adds the personal half (your profile, saved jobs, applications), and there is an employer side for posting. If you want remote-only inventory and the shortest possible path from "I heard about MCP" to "my agent answered a job question," this is it.

The market-data tools: TheirStack, Coresignal, Bright Data

This is the group people connect by accident and then wonder why it feels off. TheirStack, Coresignal, and Bright Data all expose enormous job and company datasets over MCP. Hundreds of millions of postings, technographic signals, company enrichment, the works. TheirStack has a free tier and then starts at $49 a month, Coresignal is a short free trial and then credit packs, and Bright Data gives you a few thousand free requests a month before it goes usage-based.

Here is the thing nobody says plainly: these are not job-seeker tools. They are built for salespeople, recruiters, and analysts who want to know who is hiring, for what, using which technologies, in order to sell something or source candidates. The data is real and the MCP integrations are solid. But if you are a person looking for your next role, you are holding a market-intelligence instrument by the wrong end. Great tools. Wrong job.

The board with a front door: Dice

Dice shipped an MCP server over its tech-only job database, and it is a clean piece of work. Natural-language queries, a real set of filters (location radius, workplace type, employment type, visa sponsorship, posting recency), plus resume comparison and upskilling suggestions. It connects to Claude, ChatGPT, and Gemini.

If what you want is a tech job board that your agent can search instead of a website you click through, Dice is the most straightforward answer on this list. The mental model is still "search a board," just with a better interface. That is not a criticism. For a lot of people a good board they can talk to is exactly the upgrade they wanted.

The ATS aggregator: Career Site Jobs

Career Site Jobs (Fantastic.jobs) pulls postings straight from company career pages across a large set of ATS platforms like Workday, Greenhouse, and Ashby, then enriches them. It reaches your agent as an Apify actor rather than a hosted server of its own, so the pricing is Apify's. The angle is freshness and going direct to the source rather than a board's copy of it. If your frustration is stale or duplicated listings, this is the one built for that specific complaint.

The self-hosted corner: JobSync

If the part you hate is keeping track of where you applied rather than finding the openings, the open-source world has that covered too. JobSync is the substantial one: a self-hosted tracker (one docker compose up) with resume management, job matching, and a built-in MCP server, so your agent can file applications and interview questions straight from the chat, with your approval on every write. Your data stays on your machine, and it can run against a local model through Ollama if you want the whole loop private.

A note on the open source ones

You may have noticed the pattern: the open-source tools on this list run on your machine. That changes what "MCP server" even means. When the data lives on someone else's server, MCP is the access. When the code runs locally, MCP is just one door into it.

The clearest illustration is what happened to AIHawk. It was the auto-apply bot with more than thirty thousand GitHub stars that logged into LinkedIn and fired tailored applications at Easy Apply listings, and it made the news for exactly that in 2024. It has since pivoted: the repo is now an anti-detect browser agent that ships as an MCP server for coding agents, with job application automation as one thing it can be pointed at rather than the product. Same stars, same author, no longer a job tool specifically. If you went looking for it on a two-year-old recommendation, that is what you would find.

If you do want auto-apply over MCP, the current example is JobGPT, 6figr's official server: 34 tools covering search, tailored resumes, outreach and auto-apply, with a browser sign-in instead of an API key. It is well built. Whether firing applications at volume is a good idea is a question I get to further down.

Where Remoet sits, and where it does not

Remoet is a tech job board your agent can search, plus a shortlist that keeps delivering.

The search half is the open board at remoet.dev/jobs, and search_jobs reads all of it: every company, no star needed and no key needed, filtering server-side on free text, tech stack (any of them, or every one of them on the same role), company, location, remote policy, seniority and minimum salary. Ask for senior Go roles in Germany above 90k and that is one query, not a scan.

The curation half is the part nobody else has. Every company carries a tech stack that Remoet scrapes and enriches from the roles it is actually hiring for, not the keyword soup a recruiter pasted onto a posting, so "which companies run Rails on top of React with Postgres" is a real question with a real answer. You star the ones you would genuinely work for, which buys delivery (their new roles into your feed and the roundup email) and the full stack instead of the three-technology teaser, not access, since every role was searchable already.

Now the honest part, because the vendor comparisons skip this. Remoet does not apply to jobs for you. Most listings are scraped from companies' external career pages, so when you find one, you apply on their site like always. Coverage is cleared ATS platforms only: Lever, Greenhouse, Ashby, Recruitee and Workable. Application records are not an agent surface yet; saved jobs with notes is what your agent keeps on file. And if your profile is empty, stack matching has nothing to match against, so there is setup before there is magic. The whole thing is free, with no paid tier to upgrade to, capped at 50 active stars. If you want a tool that auto-blasts applications, this is not it, and I would gently suggest that auto-blasting applications is part of why everyone's inbox is broken.

How to actually pick

Strip away the marketing and it comes down to what you are doing:

None of these is a scam and most of them are well built. The mistake is connecting the wrong category to your problem, which is easy to do when every one of them is filed under "job search MCP server" and half of them are not really for job seekers at all.

If the curation angle is the one that fits, you can connect Remoet to your agent in a few minutes. Point your client at the MCP server (the setup guide has one working config per client, and this post covers the no-key setup) and ask it what is open in your stack. Searching needs no key; a free account at remoet.dev/onboarding adds stars and saved jobs. If one of the others fits better, use that one. The good news, for the first time in a while in job search, is that there is now a real choice.

Frequently Asked Questions

Is there a JobSpy MCP server?

Yes, several. JobSpy itself is a Python scraping library; the MCP servers around it are community wrappers, of which borgius/jobspy-mcp-server is one of the better established. They run locally, need Node and Python, and are free.

Which job search MCP server works without an account?

Himalayas, JobSpy (run locally) and Remoet. Himalayas' server at https://mcp.himalayas.app/mcp answers job searches from an unauthenticated client, verified in September 2026, and Remoet's job search works the same way with no key. Everything else on this list needs either an API key or a sign-in.

Is there an official Indeed or LinkedIn MCP server?

Indeed runs an official connector inside Claude's directory. LinkedIn does not: the widely used LinkedIn MCP server is an independent open-source project that drives your own browser session, and LinkedIn's user agreement prohibits automated access.

Do any of these actually apply to jobs for me?

JobGPT does, and JobSync files applications you have already decided on. Most of the rest, Remoet included, hand your agent the employer's application URL and leave the submit to you, because that is where the form actually lives.