jobhunt.app/mcp

Organize your pipeline

Use stages for progress and Hunts for separate searches.

Updated

Step by step

  1. Choose a Hunt

    Open Hunt Campaigns to choose the search you want to see. All Hunts is a combined view. The current Hunt cannot be paused or finished, so make another Hunt current first. A Hunt with no applications yet shows one line in the first column of the board, such as No applications in 2026 Job Search yet. The Add an application button below it opens Quick Add for that Hunt.

  2. Move a role as things change

    Move the role to the stage that reflects where you actually are. Open the role for its full timeline. Two stages ask for something first, whatever you call them: an Applied stage needs the submission you made recorded on the role, and a Closed stage needs your reason. Every other stage, including ones you added, can follow any stage. You can ask your agent: "Which stages can this job move to now?" It should answer from the job itself and, when a move is refused, say what is missing and which stages you can choose instead.

  3. Keep empty stages out of the way

    Once your board has a job, a stage with none is shown as a narrow column with its name and a count of 0, and it opens when a job is added or dropped on it. You can still open an empty stage yourself, and that choice is kept. To show every stage at full width, turn off Collapse empty columns in Settings, under Preferences then Applications, or in Board settings on the board.

  4. Keep the next action nearby

    Use notes and tasks on the application for preparation, follow-ups and reminders.

  5. Come back to your board

    When you open Hunt Pipeline again, this browser shows the board as you last saw it while the current one loads, with Updating your board… at the top until it is confirmed. That copy is read-only, stays in this browser, and belongs to your signed-in account. Logging out deletes it; so does another account signing in on the same browser, and it expires after twelve hours.

What happens next

Stages describe each application; Hunts help you separate searches without duplicating the work.

Troubleshooting

A role missing from one view may belong to another Hunt. Check All Hunts before adding it again. If the board looks out of date for more than a moment, reload the page; nothing can be changed from the saved copy.

Technical detailsAPI operations and permissions

These operation details and permissions come from the API contract.

READget pipeline configuration

Read pipeline configuration, 25 stages per page, including stable IDs, order, protected/terminal flags and application/checklist impact counts. The fingerprint covers the whole configuration and related state, independently of page. Reads never initialize defaults. Requires read:applications and read:tasks.

GET /api/v1/journey/get_pipeline_configuration_v2

DECLARED PERMISSIONS

  • read:applications
  • read:tasks
View input, output and access requirements →
WRITEmove job stage

Move one job to an exact owned stage ID from get_job_hunt_view navigation, using its current revision and a stable request_id. Closed requires a factual closed_reason. Applied requires an existing user-reported submission; use record_submission to record a new submission and update the stage together. A stage alone is never evidence of submission or an offer.

POST /api/v1/journey/move_job_stage

DECLARED PERMISSIONS

  • write:applications
View input, output and access requirements →
WRITEset current job search

Make an explicitly chosen active hunt the saved current hunt in the website and future chats. Supply its current revision and the exact current_ids from get_job_hunt_preferences. Temporary chat selection should not call this tool. Reuse request_id on uncertainty. No billing, publication or application changes.

POST /api/v1/journey/set_current_job_search_v2

DECLARED PERMISSIONS

  • write:campaigns
View input, output and access requirements →