JobHound
Connects to Greenhouse job board API to fetch, score, and apply to job listings.
Connects to Wellfound (formerly AngelList) to fetch job listings for scoring and application.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@JobHound scan for new remote backend jobs"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
JobHound ๐
MCP server that lets Claude Code scan, score, and apply to jobs autonomously.
JobHound connects directly to Ashby, Greenhouse, and Lever job board APIs โ no browser required for discovery. It scores every listing with a keyword heuristic, queues high-scoring roles, and uses Claude Code as the tailor to write per-role CVs and cover letters.
Includes a TUI dashboard for tracking your pipeline in real time.
Table of Contents
Related MCP server: Job Copilot MCP Server
Why I Built This
Job searching is miserable. LinkedIn Easy Apply is a black hole โ you click apply, it goes nowhere, you never hear back. Premium job alerts cost money and send you garbage. Manually browsing 5 job boards daily is a part-time job in itself.
The APIs are free. Ashby, Greenhouse, Lever โ they all have public APIs that list every open role. Why am I manually scrolling?
JobHound exists because my agent should handle job discovery, not me. It scans APIs, scores listings against my skills and preferences, queues the good ones, and hands the tailoring work to Claude Code. I review the generated CV and cover letter, say yes or no, and it submits.
The TUI exists because I want to see my pipeline at a glance โ 47 tracked, 3 queued, 12 applied, 2 interviewing โ without opening a browser tab.
What It Does
Feature | What It Does |
Scan | Fetches from Ashby, Greenhouse, Lever, RemoteOK, HN Hiring, Wellfound |
Score | Keyword heuristic matches job description against your skills and preferences |
Queue | High-scoring roles enter a queue for review |
Tailor | Exposes job + your resume to Claude Code for per-role CV and cover letter generation |
Apply | Submits tailored applications via API where supported |
Track | SQLite-backed pipeline tracking with status (new โ queued โ applied โ interviewing โ rejected) |
Dashboard | Real-time TUI with live updates every 30 seconds |
Daemon | Background scan loop runs on a schedule |
Current Pain Points
These are the battles I'm actively fighting:
Keyword scoring is crude โ It's a heuristic: count keyword matches between job description and your config. It doesn't understand that "React" and "frontend" are related, or that "5 years experience" in a job description is flexible. A real scoring model would learn from what you actually applied to and got interviews for.
Not every board has an API โ RemoteOK and HN Hiring require scraping. Scraping breaks when they change their HTML. The browser automation layer (
playwright-stealth) is overkill for simple HTML scraping but necessary because some sites block basic requests.Auto-apply is limited โ Ashby and some Greenhouse instances support direct API application. Most don't. For those, JobHound generates the tailored docs and you apply manually. The "autonomous" part stops at "here's your CV and cover letter, go submit it."
The TUI is Textual-dependent โ Textual is great but heavy. On a slow terminal or over SSH it can lag. The dashboard is pretty but not essential โ the core value is the MCP server and scan queue.
Config management is manual โ
config.yamlneeds your skills, preferences, API keys for each source. Updating it is editing YAML. I want the agent to infer my skills from my GitHub repos and update the config automatically.No integration with Grayson โ Grayson is my outreach automation tool (cold emails, networking). JobHound finds the jobs, Grayson finds the people. They don't talk to each other. A warm referral beats a cold application.
End Goals โ Where This Is Headed
Short Term (now โ 3 months)
Better scoring โ move from keyword heuristic to embedding-based semantic similarity
Auto-config from GitHub โ read my repos, infer my stack, auto-populate config.yaml
Per-source rate limit handling โ respect Ashby/Greenhouse rate limits, back off gracefully
Medium Term (3โ6 months)
Grayson integration โ for every queued job, Grayson finds a mutual connection or relevant person to reach out to
Unified agent pipeline โ Blackreach researches the company, Huginn scrapes their blog/docs, JobHound scores the role, Grayson finds the contact, all in one workflow
Auto-apply expansion โ support more application flows (Lever API, custom forms)
Long Term (6โ12 months)
Fully autonomous job search โ "Find me senior backend roles at AI startups in Toronto, apply to the top 10, network with hiring managers, track everything"
Interview prep integration โ after an application, auto-research the company, generate likely interview questions, prepare answers
Salary negotiation assistant โ track market data, suggest negotiation strategies based on role/company/location
Install
git clone https://github.com/Null-Phnix/jobhound
cd jobhound
pip install -e .
cp config.example.yaml config.yaml # fill in your detailsConnect to Claude Code
Add to your ~/.claude/settings.json (or .claude/settings.json in the project):
{
"mcpServers": {
"jobhound": {
"type": "stdio",
"command": "jobhound-server"
}
}
}MCP Tools
Tool | Description |
| Fetch all sources, score jobs, queue high-scoring ones |
| List jobs by status (queued, applied, failed, etc.) |
| Full job details + generated docs |
| Job description + your resume for Claude to tailor |
| Submit a tailored application |
| Manually set status (interviewing, rejected) |
| Pause the daemon scan loop |
| Resume the daemon scan loop |
Workflow
jobhound_scan() # find what's new
jobhound_list("queued") # see what's waiting
jobhound_get_for_tailoring(42) # get job + resume
[Claude writes tailored CV + letter]
jobhound_apply_tailored(42, cv, letter) # submit + recordTUI Dashboard
jobhound-tuiLive two-pane view of your entire job pipeline. Polls SQLite every 30 seconds, shows status by color.
โโ JobHound โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
โ [LIVE] 47 tracked ยท 3 queued ยท 12 applied ยท 2 interviewing โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโฌโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโค
โ โถ Bree applied โ Bree โ Software Engineer, Backend โ
โ Modal applied โ Applied: 2026-03-11 via Ashby โ
โ LangChain applied โ Score: 87/100 โ
โ Cohere queued โ Method: direct POST โ
โ Anthropic new โ โ
โ Cursor failed โ Cover Letter: โ
โ โ > The line that stood out in your... โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโดโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโค
โ [s]can [p]ause [f]ilter [o]pen URL [x]export [q]uit โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโTUI Keybinds
Key | Action |
| Scan sources (fetch + score, no auto-apply) |
| Pause / resume daemon |
| Cycle filter: all โ new โ queued โ applied โ failed โ interviewing |
| Open highlighted job URL in browser |
| Export current view to |
| Quit |
Config
See config.example.yaml. Supports Ashby, Greenhouse, Lever, RemoteOK, HN Hiring, and Wellfound.
Stack
Python 3.11+
fastmcpโ MCP serverhttpxโ source API callssqlite3โ job trackingtextualโ TUI dashboardrichโ terminal output
License
MIT
Available Tools
9 toolsjobhound_apply_tailoredA
Submit an application using the tailored CV and cover letter. Tries: LinkedIn MCP โ direct POST (Ashby/Lever) โ Blackreach fallback. Records the outcome in the database.
Args: job_id: integer ID of the job tailored_cv: the tailored CV text (markdown) cover_letter: the cover letter text
Inputs: job_id (required), tailored_cv (required), cover_letter (required). Returns: result
jobhound_getC
Get full details for a job including cover letter if applied. Args: job_id: integer ID
Inputs: job_id (required). Returns: result
jobhound_get_for_tailoringA
Get everything needed to write a tailored application for a job. Returns the job description and the full resume. After reading this, generate a tailored CV and cover letter, then call jobhound_apply_tailored(job_id, tailored_cv, cover_letter).
Args: job_id: integer ID from jobhound_list('queued')
Inputs: job_id (required). Returns: result
jobhound_listA
List jobs by status with their database IDs. Args: status: one of new, queued, applied, failed, interviewing, rejected
Inputs: status. Returns: result
jobhound_pauseA
Pause the JobHound daemon (scan loop stops applying).
Inputs: no named parameters. Returns: result
jobhound_resumeB
Resume the JobHound daemon.
Inputs: no named parameters. Returns: result
jobhound_scanA
Fetch jobs from all configured sources, score them, and queue high-scoring ones. Jobs above score threshold are saved with status 'queued'. Returns a summary + list of queued job IDs ready for tailoring. Next step: call jobhound_list('queued') then jobhound_get_for_tailoring(id).
Inputs: no named parameters. Returns: result
jobhound_statusB
Summary of JobHound activity: job counts by status.
Inputs: no named parameters. Returns: result
jobhound_updateA
Manually update a job's status. Use this when you get an interview invite or rejection. Args: job_id: integer ID status: interviewing, rejected, applied, failed, queued
Inputs: job_id (required), status (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogโฆ
TDQS
Scored across 9 tools
Each tool serves a distinct function: scanning, listing, retrieving, updating, applying, and daemon control. The only potential confusion is between `jobhound_get` and `jobhound_get_for_tailoring`, but their descriptions clarify the different outputs.
All tools use the `jobhound_` prefix with snake_case verbs like `get`, `list`, `scan`, `update`, `apply_tailored`. Minor deviations are `jobhound_status` (a noun rather than a verb) and `jobhound_get_for_tailoring` (a longer phrase), but the pattern is consistent enough to predict tool purpose.
9 tools is well-scoped for a job application automation server. Each tool covers a necessary step in the workflow: scanning, queuing, tailoring, applying, tracking, and daemon lifecycle.
The core workflow is fully covered: scan โ list โ get_for_tailoring โ apply_tailored, plus status updates and daemon control. Minor gaps include no tool for manually adding or deleting jobs, but these are not essential for the automated pipeline.
Maintenance
Related MCP Connectors
Job application tracker for developers - AI agents write over MCP, you review in a dashboard.
Auto-Apply That Ends on an Interview. AI job search, tailored resumes, job application tracker.
Tailor resumes, score ATS fit, find hiring leads, and send cold outreach, from your agent.
Automate your job search: find jobs, upload a resume, apply automatically, and track applications.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn AI-powered job search and application assistant that enables multi-source job hunting, OpenAI matching, cover letter generation, and hybrid application automation via Playwright, Chrome CDP, screen OCR, and manual assist.MIT
- AlicenseNot gradedqualityCmaintenanceExposes the entire job-search workflow as 13 chat-driven tools, letting users refresh a ranked feed of live postings from employers' public hiring APIs, view and score job descriptions, tailor and render truthful one-page LaTeX resumes, review skill gaps and screening answers, and log applications. It keeps a human in the loop, since nothing is ever submitted automatically.MIT
- FlicenseNot gradedqualityAmaintenanceLets AI agents search, filter, and apply to salary-transparent tech jobs across nine job boards in eight countries, filtering by pay, remote work, tech stack, and location while tracking applications to avoid duplicates. It returns JSON-first results so an agent can drive job discovery and application end-to-end from the terminal or chat.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to discover postings from watched company boards ranked by keyword fit, tailor and fact-check resumes against a source-cited profile, render ATS-readable PDFs, submit applications through the user's own browser, and track replies and follow-ups. All ranking, claim checking and email classification run as plain code, so LLM tokens are spent only on writing.1Apache 2.0