jobs-mcp
Provides live search of US software-engineering job openings from Greenhouse ATS boards, returning company, title, location, URL, and posted date, with US-only and clearance/citizenship filtering.
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., "@jobs-mcp find recent backend engineer jobs in Seattle"
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.
jobs-mcp
An MCP server that gives any LLM live access to US software-engineering job openings.
Point Claude (or any Model Context Protocol client) at this server and it can search current postings — pulled live from company ATS boards (Greenhouse / Lever / Ashby) and a community new-grad feed — right inside your conversation. US-only, security-clearance / citizenship-required roles filtered out, newest first. No API keys: every source is a public endpoint.
Claude ──calls──▶ jobs-mcp
• search_jobs(query, location, limit)
• list_sources()
└─▶ Greenhouse · Lever · Ashby · SimplifyJobs feed
└─▶ US-only · clearance/citizenship roles excluded · dedupedTools
Tool | What it does |
| Live search; |
| The ATS boards + community feed this server pulls from. |
Related MCP server: trackly-cli
Install & connect to Claude Code
git clone https://github.com/Ashishkosana/jobs-mcp && cd jobs-mcp
python3 -m venv .venv && .venv/bin/pip install -e .
# register it (stdio transport):
claude mcp add jobs -- "$(pwd)/.venv/bin/python" -m jobs_mcpThen just ask Claude things like "find me fresh backend software engineer roles in New York"
— it calls search_jobs and answers from live data.
Works with any MCP client (Claude Desktop, etc.) — point it at
python -m jobs_mcp over stdio.
How it works
An MCP server exposes tools a client can discover and call. Here each tool is a
plain Python function decorated with @server.tool(); its type hints become the input
schema the model sees. On a call, the server fetches every source concurrently (a dead
board is skipped, not fatal), applies the US + clearance filters, dedupes, and returns
structured rows. See src/jobs_mcp/server.py.
Scope / honesty
Sources are a curated company list + one community feed, not "every job on the internet" — LinkedIn/Indeed block scraping, so this uses public ATS APIs instead.
The clearance filter is lexical (keywords + known defense employers); it catches the common cases, not every phrasing.
License
MIT
Available Tools
2 toolslist_sourcesA
List the job sources this server pulls from (ATS boards + community feed).
Inputs: no named parameters.
search_jobsA
Search live US software-engineering job openings.
Pulls current postings from company ATS boards (Greenhouse/Lever/Ashby) and a community new-grad feed, filters to US roles, excludes security-clearance / US-citizenship-required postings, de-duplicates, and returns newest first.
Args: query: words that must all appear in the job title, e.g. "backend engineer", "new grad software engineer". Default "software engineer". location: "us" for anywhere in the US, or a city/state substring like "New York" or "remote". limit: max results (1-100).
Returns a list of {company, title, location, url, posted, source}.
Inputs: limit, query, location. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools serve clearly distinct purposes: one lists data sources and the other searches for jobs. There is no overlap or ambiguity between them.
Both tool names follow the same verb_noun snake_case pattern: list_sources and search_jobs. This is perfectly consistent and predictable.
With only two tools, the server feels minimal, but the scope is very narrow—job searching and source listing. This is borderline, as the rule suggests 1-2 tools feels thin, yet each tool serves a necessary role.
The server fully covers its stated purpose: list the job sources and search live US software-engineering job openings. There are no obvious missing operations for this narrow domain.
Maintenance
Related MCP Connectors
Public MCP server for discovering open jobs. Search, filter, and get application links.
GetJobzi MCP server for job search, application tracking, and career forecasting.
Free live multi-ATS + HN job search. Comp & hiring-signal depth metered via x402/USDC. Hosted MCP.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceMCP server that exposes job search data from multiple boards, enabling clients to query and manage job listings via natural language.8MIT

trackly-cliofficial
AlicenseNot gradedqualityBmaintenanceMCP server for job search and application tracking, enabling AI agents to search jobs, get details, manage applications, and find contacts across 128K+ jobs and 1,900+ companies.1,315 npm3MIT- AlicenseNot gradedqualityDmaintenanceUnified job search MCP server that aggregates live listings from multiple job boards with deduplication, enabling AI agents to find and filter jobs by keyword and location.MIT
- AlicenseNot gradedqualityDmaintenanceA job-search MCP server that ranks roles, drafts cover letters, and rehearses Q&A answers using a candidate profile, with live listings from five public sources.66 npmMIT