# Navad Jobs MCP server

Source: https://glimind.com/server/mcp-registry%2Fai.navad%2Fjobs
Registry id: `mcp-registry/ai.navad/jobs`
Status: live (checked 2026-11-22T16:24:14.249Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 137
- Outages (90 days): 0

## Install

```json
{
  "mcpServers": {
    "navad-jobs-mcp-server": {
      "type": "http",
      "url": "https://mcp.navad.ai/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http navad-jobs-mcp-server https://mcp.navad.ai/mcp
```

## Tools (18)

- `check_ats_score`: Score how well a résumé will pass the applicant tracking system for a specific job. Returns the score plus the per-category breakdown, keyword analysis, and con
- `finish_cv_upload`: Complete a CV upload started by start_cv_upload, after the bytes have been PUT to the upload URL. The server verifies the file really is a PDF here, so a failur
- `get_application_run_status`: Poll a run started by start_apply_with_ai. Report per-stage state, not just the overall status — a run can finish 'completed' with one stage failed, and that is
- `get_job`: Fetch one job posting in full, including its description. Accepts either the job's UUID or its URL slug. Free; no account needed.
- `get_job_ai_tools`: For one job, report which AI artifacts already exist (tailored résumé, cover letter, interview prep, ATS score). Costs nothing. Use it to avoid regenerating som
- `get_profile`: Read the signed-in user's name, plan, and job-search preferences (desired roles, seniority, skills, salary, locations). Use this before searching so results ref
- `get_related_jobs`: Given a job UUID, find similar postings. Useful for widening a search after the user shows interest in one role.
- `get_usage`: Show how much of this month's AI allowance is left, per feature. Call this before running several AI tools in a row, and to explain a limit error rather than re
- `list_job_locations`: List the regions and countries that can be passed to search_jobs `location`. Call this before filtering by location rather than guessing values.
- `list_my_resumes`: List the user's stored résumés and their IDs. Call this before start_apply_with_ai, which requires a resume_id. Does not return file contents or download links.
- `prepare_interview`: Generate likely interview questions, suggested answers, company research, and weak spots for a specific job, and return them so you can run a mock interview wit
- `search_jobs`: Search Navad's remote job listings by keyword, location, seniority, salary, and recency. Returns summaries without full descriptions — call get_job for a specif
- `start_apply_with_ai`: Start a background run producing a tailored résumé, a cover letter, and an ATS score for one job. Preferred over calling the individual tools when the user want
- `start_cv_upload`: Get a short-lived URL to upload a PDF CV to. The file does NOT pass through this tool — you upload the bytes yourself with an HTTP PUT, then call finish_cv_uplo
- `tailor_resume`: Rewrite the user's résumé for a specific job. Uses one unit of the monthly résumé allowance. Takes 30–120 seconds. Returns the tailored résumé text — show it to
- `update_job_preferences`: Change the preferences that drive job matching — desired roles, seniority, skills, salary range, locations, timezone flexibility. Only the fields you pass are c
- `update_profile`: Change the user's display name. Requires a token with profile access. Only call this when the user explicitly asks — never to 'correct' a name you think looks w
- `write_cover_letter`: Write a cover letter for a specific job from the user's résumé. Uses one unit of the monthly cover-letter allowance. Takes 30–120 seconds. Returns the letter te

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
