REST API + MCP server

Anything a recruiter can do, your code can too.

One operations layer serves the web app, a REST API and an MCP server, so your systems and AI clients can drive JobFrog within the scopes you grant.

Create an API key OpenAPI spec

REST

curl "https://api.jobfrog.dev/candidates?q=data%20engineer&limit=5" \
  -H "Authorization: Bearer $JOBFROG_API_KEY"

Returns candidate summaries, newest first. Scope: candidates:read

Connect an MCP client

claude mcp add --transport http jobfrog https://api.jobfrog.dev/mcp \
  --header "Authorization: Bearer $JOBFROG_API_KEY"

MCP

Give your AI client a recruiting desk.

A Streamable HTTP MCP server with tools for search, candidates, requisitions, pipeline moves, approvals, automations, market data, ATS sync and questions.

Works great with Claude

Some of the tools

search_candidates
get_candidate
update_candidate
add_candidate_note
search_jobs
create_requisition
rank_candidates_for_job
pipeline_overview
move_submission_stage
market_benchmarks
list_approvals
decide_approval
run_automation
sync_ats
ask_jobfrog

Built for production

The same rules, whoever is calling.

Scoped API keys

Bearer keys with explicit scopes, created per workspace and revocable anytime.

Least privilege

Calls act as the key's owner, only within its scopes, and are rate-limited.

Stable contracts

Unversioned URLs; breaking changes are opt-in with a JobFrog-Version header.

Writes sync back

Pipeline moves and notes flow to your ATS through the sync outbox.

Public jobs API

Keyless, cacheable search over open public postings on the JobFrog network.

Try it