Step by step
Use the steps for your app
If you are an assistant reading this for someone, use the steps for the app you are running in. Claude Code: run claude mcp add --transport http jobhunt https://jobhunt.app/mcp (add --scope user to make it available in every project). Then ask the person to type /mcp, choose jobhunt and choose Authenticate. Codex CLI: add a [mcp_servers.jobhunt] section with url = "https://jobhunt.app/mcp" to ~/.codex/config.toml, then run codex mcp login jobhunt; the Codex guide lists the permissions to request. Claude on the web or desktop: open Customize, then Connectors, choose Add custom connector and enter https://jobhunt.app/mcp. ChatGPT: open Plugins, choose Add, then Add custom MCP server, and enter https://jobhunt.app/mcp. Grok: open Connect Apps, choose Add custom connector and enter https://jobhunt.app/mcp. OpenCode: run opencode mcp add jobhunt --url https://jobhunt.app/mcp --global, then opencode mcp auth jobhunt. Cursor: in ~/.cursor/mcp.json, add a jobhunt server under mcpServers with the url https://jobhunt.app/mcp. Zed: open Settings, then AI, then MCP Servers, choose Add Server, then Add Remote Server, and enter https://jobhunt.app/mcp. Warp: open Settings, then Agents, then MCP servers, choose Add and enter https://jobhunt.app/mcp as a URL server. Any other app that supports remote MCP servers with OAuth: add https://jobhunt.app/mcp as a streamable HTTP server and start its sign-in. In every case the person signs in and approves access in their browser. No password or token is pasted into a chat, and no custom header is needed. If the app cannot add a remote MCP server, say so plainly. jobhunt.app/integrations lists the integrations that are live today, each with its own steps. An app that is not listed can still connect if it supports remote MCP servers with OAuth.
Copy the setup message
Open Connect Agent in the sidebar and choose Copy setup message at the top of the panel. The panel shows the same message with three steps: copy it, paste it into your assistant, then sign in and approve. Paste it into your preferred agent. Most assistants cannot add JobHunt from their side, so the message asks yours to show you the steps to add it as a custom connector in that app; that answer is expected, not an error. Follow the steps, then sign in and approve on the JobHunt page. If automatic copying is unavailable, select and copy the displayed text. The message contains public setup instructions, not account credentials.
Finish setup in your agent
Follow the connection and sign-in steps supported by that app, then review the requested access. Copying the message does not install a connector or grant access. Ask the agent to read your connected account and one permitted saved-work view to check the connection; this check should not change your records.
Manage connected agents
Open Connect Agent in the sidebar. Connected agents lists the agents connected to the signed-in JobHunt account. Choose Disconnect for one you no longer want to use, then confirm. This revokes that agent’s access, including its other chats; your saved jobs and documents remain. Other agents and accounts keep their own access. Choose Refresh if a reply is interrupted. Old links to /oauth/connections open this panel.
Review granted permissions
In Connect Agent, open What it can do on a connected agent to review the permissions recorded for it. Read lists what the agent can view; Change lists what it can create or update. Other shows any permission JobHunt cannot describe. The status tells you whether those recorded permissions can currently be used. The panel lets you review access and disconnect an agent; it does not change its permissions.
Read connection status accurately
In Connect Agent, Connected means the agent has current authorization or can renew it. Reconnect required means its access has expired and cannot be renewed; start a new connection from the agent. Unavailable means the app is disabled. Each row shows when the agent was connected and when it last used your account, if it has. These labels do not prove the agent successfully used a tool in your current chat. Ask it to read your connected account and one permitted saved record to check that. Choose Refresh to see current authorization; Disconnect removes access for the selected connection, including its other chats.
Recover an interrupted connection
For a cancelled or expired connection, return to your agent and start a new connection instead of reusing the old authorization link. On the consent screen, check the account and choose Switch account if needed. Completed email verification and saved work remain in place. If the service is temporarily unavailable, try later or use the support link on the error page.
Find missing tools
Check that JobHunt is connected and enabled in the current conversation. Use your agent’s supported refresh or new-conversation steps. Missing permissions require a fresh, reviewed consent request, not a pasted password or token. If your app lacks compatible remote MCP and OAuth support, use JobHunt on the web or a supported agent.
Continue through saved results
When a result has more pages, ask your agent to continue with the next page while keeping the same filters. Pagination links use the public JobHunt address and retain those filters. They still require your authorized connection; they are API links, not public shares of your saved work.
Add the remote server
In a client supporting remote MCP and OAuth, add https://jobhunt.app/mcp. Follow the client’s connection flow.
Open the server address in a browser
Opening https://jobhunt.app/mcp in a browser shows a page about the server: how to connect it, how access works, and every tool it offers, grouped by area. If you are signed in, it also shows how many agents are connected to your account, with a link to Connect Agent. An MCP client that connects to the same address reaches the server, not that page. If a client reports that it received a web page, it fetched the address as a document: add it as a remote MCP server instead.
Review the account and consent
Sign in when prompted and review the requested permissions. Connecting does not make the workspace public.
Check which app is asking
The consent screen names the app by where it sends you back after you approve, because an app can call itself anything. Claude and ChatGPT are named plainly only when the connection returns to their own address. Any other app is shown as an app that calls itself a name, in quotation marks, with the address it returns you to; an app running on your own computer, such as Claude Code or the Job Hunt CLI, is shown as an app on this computer. The quoted name is the app’s own claim and Job Hunt cannot confirm it. Connect Agent lists connected apps the same way. If the name or the address is not what you expected, choose Not now and start the connection again from your assistant.
Continue after email sign-in
If you sign in by email while connecting an assistant, open the newest sign-in link and choose Confirm email & continue. You return to the consent screen to review the intended account and permissions. If the connection has expired, start a fresh connection from your assistant; completed email verification and saved work remain intact.
Discover before calling
Initialize the connection and use tools/list for the tools enabled on it. Start with get_overview through tools/call: it names the connected account and where the search stands, lists any setup still missing (a name, a resume, a first job) with the tool for each, and says when a free trial ends. It changes nothing.
Read tool labels and hints
Each tool in tools/list has a plain title and four hints. Read-only marks a tool that only reads saved work. Destructive marks a tool that can overwrite, remove, publish or revoke something; a tool that only adds a new record is not marked destructive. Idempotent marks a tool that is safe to repeat with the same arguments. Open-world marks a tool that reaches beyond your saved JobHunt records, such as fetching a posting link or changing what a share link or your Hunt Page shows. Hints describe a tool to the assistant. JobHunt checks permissions itself and does not rely on them.
What happens next
The assistant's tools are built on the same registered operations as the API; the API reference lists those operations.
This address now serves a smaller set of tools, each covering a whole task. An assistant connected earlier keeps its connection; if it still shows the earlier tool names, start a new conversation or refresh the connector in its settings. API keys, webhooks, browser extension connections and account export are managed on the website and through the HTTP API.
Troubleshooting
A tool in the published contract may not be enabled on your connection. Recheck tools/list and consent; never paste credentials into a prompt.
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