Job Search MCP server

mcp-job-search

<!-- mcp-name: io.github.michalper/mcp-job-search -->

An MCP server that automates the repetitive mechanics around job-hunting with an AI coding assistant, while deliberately not automating the parts that need a human: drafting your CV/cover letter, fact-checking claims against your real history, and submitting an application.

It answers the question that keeps eating a job search's time: "this CV draft looks fine, but did it quietly fabricate something, and is this one specific posting even worth reading?"

Status: early stage. Built for personal use, published because the

configurable anti-fabrication linter and application-registry tooling are

generically useful beyond one person's job search. All seven tools are

working. See CHANGELOG.md for what changed and what was verified live.

How this differs from other job-search MCP servers

A few open-source MCP servers already do job search + CV tailoring (not-boring-resume-mcp, resume-mcp, Workopia MCP, IAM MCP Server, LinkedIn MCP Server, among others). This one targets what they don't:

JustJoin.it and similar Polish IT boards have no public search API — fetchjobposting reads one URL you already found instead of indexing their listings, and on boards confirmed to sit behind an active Cloudflare challenge (Pracuj.pl, Indeed), it fails loudly rather than trying to solve the challenge automatically. See the verified coverage table below — this is a documented boundary, not a silent gap.

1. It won't scrape past a bot-detection wall, even quietly. NoFluffJobs,

hardcoded prose. None of the surveyed alternatives ship a way to enforce your own banned-phrase list, achievement-weight rules, or required clauses — lintcv reads them from a YAML file you control, so the mechanism is reusable even though the facts it checks against are personal (see "Why a configurable linter" below).

1. **The anti-fabrication linter is a configurable rules engine, not

CV/cover-letter text and adversarially verifying every claim traces back to something true stays with whatever AI assistant calls these tools — this server is a mechanics layer (search, fetch, render, lint, log), not a weaker bundled LLM call duplicating judgment the calling assistant already does better with full context.

1. It doesn't draft or fact-check for you, on purpose. Writing the

What this server doesn't pretend to be: it doesn't cover every job board — only ones with a real API, or a single posting URL a human already found. It never submits anything on your behalf. And a clean lint_cv run doesn't mean a CV is honest, only that it passes the specific rules you wrote — semantic fabrication (two true facts combined into a false-sounding one) still needs a human or an independent adversarial review to catch.

Install

From PyPI (published as mcp-job-search-mp — mcp-job-search was already taken by an unrelated project; the command stays mcp-job-search):

Shortened. The full README is on GitHub.