mcp-lever
Related Servers
Alternatives to mcp-lever
- AlicenseAqualityBmaintenanceSearch and read public Ashby job boards for named companies, with filtering, full job details, and side-by-side compensation comparison. No API key required.5210 npmMIT
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server that aggregates and deduplicates job listings from multiple public sources, ranks them against a user's resume, and exposes tools for searching, viewing details, explaining fit, and tracking applications.MIT
- AlicenseNot gradedqualityAmaintenanceMCP server that exposes job search data from multiple boards, enabling clients to query and manage job listings via natural language.7MIT
- AlicenseAqualityDmaintenanceMCP server that scours job openings from public, ToS-clean sources (Greenhouse, Lever, Ashby, HN, RemoteOK, Adzuna, USAJobs) and provides tools for job search, company listings, and salary context.4MIT
- FlicenseNot gradedqualityCmaintenanceMCP server that automates applying to jobs on Lever and Greenhouse ATS systems. It fills forms from a candidate profile, verifies fields, and supports dry-run or live submission, with optional chat integration via Hermes.-
- AlicenseAqualityCmaintenanceMCP server for interacting with the CleanJobData Job API, enabling job searches, company lookups, location suggestions, and candidate profile prompts.5MIT
- 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
TDQS
Scored across 4 tools
search_jobs and resolve_company share the company-name-resolution step, but the descriptions clearly separate probing which companies are on Lever from actually reading job boards. get_job and list_filter_values have distinct purposes. There is still a small moment of hesitation over whether to call resolve_company first, but otherwise the tools are easy to tell apart.
All four tools use a consistent snake_case verb_noun pattern: search_jobs, resolve_company, get_job, list_filter_values. The convention is predictable and readable throughout.
Four tools is a well-scoped set for a read-only Lever job-search server. Each tool earns its place: search, company resolution, job detail, and filter vocabulary lookup.
The read-only lifecycle is covered: resolving company names, searching openings, reading a full job, and listing filter vocabularies. Minor gaps remain, such as no direct department-vocabulary listing and no way to browse all Lever companies without naming them, but agents can work around these.