JobHound
Enables autonomous job search by scanning, scoring, and applying to jobs via APIs like Ashby, Greenhouse, and Lever, with a TUI dashboard for tracking.
README
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
- Why I Built This
- What It Does
- Current Pain Points
- End Goals
- Install
- Connect to Claude Code
- MCP Tools
- Workflow
- TUI Dashboard
- Config
- Stack
- License
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 details
Connect 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 |
|---|---|
jobhound_scan() |
Fetch all sources, score jobs, queue high-scoring ones |
jobhound_list(status) |
List jobs by status (queued, applied, failed, etc.) |
jobhound_get(id) |
Full job details + generated docs |
jobhound_get_for_tailoring(id) |
Job description + your resume for Claude to tailor |
jobhound_apply_tailored(id, cv, letter) |
Submit a tailored application |
jobhound_update(id, status) |
Manually set status (interviewing, rejected) |
jobhound_pause() |
Pause the daemon scan loop |
jobhound_resume() |
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 + record
TUI Dashboard
jobhound-tui
Live 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 |
|---|---|
s |
Scan sources (fetch + score, no auto-apply) |
p |
Pause / resume daemon |
f |
Cycle filter: all → new → queued → applied → failed → interviewing |
o |
Open highlighted job URL in browser |
x |
Export current view to ~/jobhound_export_YYYYMMDD.md + .csv |
q |
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
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。