simplyapply-jobs-mcp
# simplyapply-jobs-mcp
An MCP server for real, live job search — search open roles from Greenhouse, Lever, Ashby, and SmartRecruiters career pages across thousands of companies, refreshed daily. Backed by [SimplyApply](https://www.simplyappl.ai)'s job aggregation API.
No API key required.
## Tools
- **`search_jobs(keyword?, location?, remote?, company?, employment_type?, posted_since?, limit?)`** — full-text search over currently-open job postings.
- **`get_company_jobs(company)`** — a company's profile and every currently-open role, by slug (as used in `https://www.simplyappl.ai/companies/{slug}`).
## Install
```bash
git clone https://github.com/tsushanth/simplyapply-jobs-mcp.git
cd simplyapply-jobs-mcp
npm install
npm run build
```
Add to your MCP client config:
```json
{
"mcpServers": {
"simplyapply-jobs": {
"command": "node",
"args": ["/absolute/path/to/simplyapply-jobs-mcp/dist/index.js"]
}
}
}
```
No environment variables needed — the server talks to SimplyApply's public API directly.
## Why this exists
Job search is a genuinely good fit for an agent: "find me remote staff engineer roles posted this week" is exactly the kind of multi-constraint query a human would otherwise do by hand across a dozen career pages. This server exposes the same aggregated listings that power [simplyappl.ai](https://www.simplyappl.ai) directly to any MCP client.
## License
MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one performs a global search across all aggregated job boards, while the other retrieves jobs for a specific company. There is no ambiguity or overlap in their intended use cases.
Both tool names follow the consistent verb_noun pattern (search_jobs, get_company_jobs), using snake_case and action-first naming. This makes the tool set predictable and easy to reason about.
With only two tools, the surface feels minimal but not unreasonable for a narrow job-search aggregation domain. However, the count is at the low end of the spectrum and may limit agent flexibility—additional capabilities like filtering or retrieving specific job details would make it more useful.
The tools cover global search and company-specific retrieval, which are the core operations for job browsing. However, there is no way to retrieve a single job's full details, apply filters within search, or access other lifecycle operations like saving or applying, leaving notable gaps for a complete job-search workflow.