Connect your AI assistant to JobRipe
JobRipe runs a Model Context Protocol (MCP) server. Add it to an assistant and ask things like “find nursing jobs in Toronto that publish pay” or “save the second one and set a daily alert”.
Server address
https://jobripe.com/api/mcp
Streamable HTTP transport (protocol versions 2025-03-26 to 2026-07-28). Without a key, the assistant can search jobs, read job details and company facts. With an API key it can also do what the key's scopes allow.
Claude Code
claude mcp add --transport http jobripe https://jobripe.com/api/mcp \ --header "Authorization: Bearer jrk_YOUR_KEY"
Claude Desktop (with your key)
Add this to claude_desktop_config.json (Settings → Developer → Edit config), then restart Claude. It uses the open-source mcp-remote bridge, which needs Node.js.
{
"mcpServers": {
"jobripe": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://jobripe.com/api/mcp",
"--header", "Authorization:${JOBRIPE_AUTH}"],
"env": { "JOBRIPE_AUTH": "Bearer jrk_YOUR_KEY" }
}
}
}Claude.ai, ChatGPT and other connector screens (search only)
Add a custom connector with the server address above and no authentication. The assistant can then search jobs and read job and company facts. JobRipe doesn't offer sign-in through connectors yet, so saving, alerts and applying need a key with Claude Code, Claude Desktop or your own client.
Your own client
curl -X POST https://jobripe.com/api/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "MCP-Protocol-Version: 2025-06-18" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'curl -X POST https://jobripe.com/api/mcp \
-H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" \
-H "MCP-Protocol-Version: 2025-06-18" -H "Authorization: Bearer jrk_YOUR_KEY" \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"search_jobs","arguments":{"q":"nurse","where":"Toronto"}}}'Answers are plain JSON. Older clients start with initialize; clients on the 2026-07-28 revision send the version in every request (and Mcp-Method / Mcp-Name headers) and may call server/discover.
Tools
search_jobs
Search open jobs by keywords and place, with pay, trust, freshness and reply speed.
Scope: none needed
get_job
One job in full: description, screening questions, trust reasons and warning flags, how to apply.
Scope: none needed
get_company
Company facts, business-register check, measured reply rates, review signal.
Scope: none needed
save_job
Save a job to the person's list.
Scope: saved:write
create_alert
Create an email job alert for a search.
Scope: alerts:write
apply_to_job
Apply to a job that takes applications on JobRipe. Needs human_confirmed: true; a few a day.
Scope: applications:write
list_my_jobs
Employers: your jobs with applicant counts.
Scope: employer:jobs
list_applicants
Employers: applicants for one job (full resumes stay in the dashboard).
Scope: employer:jobs
update_applicant_stage
Employers: move an applicant or add a private note.
Scope: employer:jobs
Rules the assistant is given
- Pay exactly as given.
pay.publishedis the employer's own figure.pay.estimatecomes from similar jobs: always call it an estimate (“est.”), never the employer's number. When both are empty, say the pay isn't published. - Verified means verified. Only call a job verified when
trust.levelisverified.listedmeans a copy from a public job board that JobRipe can't confirm with the employer. Pass oncautionflags. - No invented numbers. Reply speed is measured only from applications sent through JobRipe, and star ratings exist only with 5 or more verified reviews. If a field is empty, the answer is “not enough data”.
- The person decides. Apply only after the person read the job and approved the exact cover note and answers, then send
human_confirmed: true. Never set it on your own. - Link back. Give the person the job's
urlso they can check it themselves.
Terms of use
- Use the API for the person who owns the key (or, without a key, for your own users' searches). Don't copy JobRipe's listings into another job board or database, and don't try to get around the limits with extra keys or addresses.
- No mass applying. Agents can send a few applications per person per day, only with that person's confirmation of each one.
- Keep keys secret. Anyone with a key can act as you within its scopes: revoke it at once at API keys if it leaks.
- Keys and their limits may be suspended for abuse. The site terms and privacy policy apply.