Step by step
Check the app needs this
Most agent apps connect to https://jobhunt.app/mcp and open the JobHunt sign-in page themselves; use the guide for your app. This path is for apps that cannot, such as LM Studio and Jan, which start a local program instead.
Install the command and sign in
Install the jobhunt command (npm install --global jobhunt) and run: jobhunt auth login. Review the access on the JobHunt consent screen and allow it. It must be a version of jobhunt whose help lists "mcp".
Add the bridge to your app
In the app's MCP settings, add a local server that runs the command: jobhunt mcp. Where the app takes a JSON configuration, use {"mcpServers": {"jobhunt": {"command": "jobhunt", "args": ["mcp"]}}}. No token, key or password goes in this configuration; the bridge uses the sign-in saved by the command and keeps it fresh.
Check your saved work
Ask: Check which JobHunt account is connected, then show my saved applications. Continue only when it reads the intended account and returns a real result.
Disconnect
Run jobhunt auth logout to revoke the saved sign-in and remove it from your computer, or open Integrations in the JobHunt sidebar and choose Disconnect. Then remove the local server from your app.
What happens next
The bridge has the same access as the sign-in saved by the command, and anything running as you on this computer can use it, as with the command itself. It is not a separate connection with narrower access.
This path is released with the jobhunt command version that adds the mcp command.
Troubleshooting
If the app says it is signed out or JobHunt refused the saved sign-in, run jobhunt auth login again and restart the server in your app. If the app cannot start the server, check that the jobhunt command is on the path the app uses. Never paste tokens or authorization codes into the app's configuration or a chat.
Technical detailsAPI operations and permissions
These operation details and permissions come from the API contract.
READget connected account
Identify the JobHunt account connected by these credentials. The opaque account ID stays unchanged across renaming, reconnection and token refresh. This does not select or change a resume contact profile.
GET /api/v1/journey/get_connected_accountread:profile
READget job hunt view
Read the current owned hunt or an explicitly selected application, its role documents, screening drafts, PDF preparation state and user-reported submissions. Filters and pagination never change saved defaults. Supplied IDs are selection hints, not permissions. Document content is included only when document_id selects an owned master or a member of the selected application package. No read creates a job, document, submission or task. Unavailable tasks are not an empty list.
GET /api/v1/journey/get_job_hunt_viewread:profileread:campaignsread:documentsread:applications