JobDiva API and MCP server

JobDiva's API only works with a client ID from JobDiva and has no webhooks. Sign in to JobDiva once in your own Cloud Browser, and your AI agent does the work there for you. The same tools work over MCP for agents and as a REST API for scripts.

Not affiliated with JobDiva.

JobDiva's own API leaves this out. So we run one for you.

JobDiva's own API, a GitHub MCP server and Cotlet compared
What you need JobDiva's APIGitHub MCP serverCotlet
Candidate search, notes, hotlists, submittals No No Yes, 14 tools
Acts as you, signed in 24/7 No No Yes, Cloud Browser
Fixed for you when JobDiva changes N/A No Yes, tested every 6h
Runs with your laptop off N/A No Yes, hosted

Checked Oct 23, 2026. Sources: JobDiva API (Swagger UI, Version 1 and Version 2) · JobDiva: Integrate with JobDiva · JobDiva + AI · JobDiva: FAQ

Your own Cloud Browser, on 24/7. Sign in once. We keep it connected.

  1. 01Sign in to JobDiva in your own Cloud Browser

  2. 02Connect it for your agents

  3. 03Cotlet keeps it signed in and working

How do I connect JobDiva to Claude, ChatGPT or my code?

AI agents connect over MCP, scripts call the REST API. Both reach the same 14 tools with one API key.

For AI agents: MCP

Add Cotlet to your agent once. JobDiva and every other app you connect show up as its tools.

  • Claude
  • ChatGPT
  • OpenClaw
  • Hermes
  • GrokBot
  • Cursor
  • n8n
  • Any MCP client
  1. 1

    Add Cotlet to your agent

    Claude Code
    claude mcp add --transport http cotlet \
      https://cotlet.dev/mcp/v1 \
      --header "Authorization: Bearer $COTLET_API_KEY"
    Cursor
    {
      "mcpServers": {
        "cotlet": {
          "url": "https://cotlet.dev/mcp/v1",
          "headers": {
            "Authorization": "Bearer ${COTLET_API_KEY}"
          }
        }
      }
    }
    Codex
    # ~/.codex/config.toml
    [mcp_servers.cotlet]
    url = "https://cotlet.dev/mcp/v1"
    bearer_token_env_var = "COTLET_API_KEY"

    Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

For scripts: REST API

Every tool is an endpoint under /api/v1/jobdiva with its own method and path, such as POST /api/v1/jobdiva/candidates, with the same API key. Our open-source repo has ready scripts to start from.

REST API docs

What can the JobDiva API and MCP server do?

14 tools on your own JobDiva account. Agents call them as operations of the MCP tools jobdiva_read and jobdiva_write; scripts call each one at its own REST endpoint, with the same inputs and answers.

JobDiva tools in Cotlet's MCP server and REST API
Tool What it does Access
search_candidates Candidates from a Talent Search by skills, titles and distance from a location. read
find_candidate Quick search for a candidate by name, email, phone or address. read
get_candidate One candidate record with contact fields, location, skills and work history. read
list_candidate_notes The notes on a candidate record, newest first. read
search_jobs Jobs by title, company, city and state, open jobs only if you ask. read
get_job One job with its description, company, location and dates. read
list_submittals Submittals filtered by job, candidate or company. read
list_hotlists The candidate hotlists you can see. read
create_candidate A new candidate record with name, contact fields and skills. write
add_candidate_note A note on a candidate record, with an action type and an optional job link. write
create_hotlist A new candidate hotlist, optionally linked to a job. write
add_candidates_to_hotlist Put candidates into a hotlist. write
remove_candidates_from_hotlist Take candidates out of a hotlist. write
create_submittal Submit a candidate to a job with status, rates and notes. writeasks first

Scroll the table for all 14 tools.

Ask in plain words. Your agent does the rest.

Is it safe to connect JobDiva?

You sign in yourself in your own Cloud Browser, we never save your password, and anything that reaches your readers waits for your OK. The browser profile is encrypted in the EU. Independent scanners grade cotlet.dev A+.

How much do the JobDiva API and MCP server cost?

One price for both: a tool call costs the same over MCP or REST. Free 7-day trial with 2,000 credits, no card needed. Then one-time credit packs, no subscription, valid 12 months. Each call uses 10 credits, and your Cloud Browser uses 50 credits a day while JobDiva is enabled for agents, so 20 calls a day come to 250 credits.

Cotlet credit packs: price, credits and calls at 10 credits each
Credits Price, one time Calls at 10 credits Per 1,000 credits
5,000 $29 500 $5.80
15,000 $79 1,500 $5.27
32,000 $149 3,200 $4.66
60,000 $249 6,000 $4.15

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.

Questions

Does JobDiva have an API?

JobDiva has a REST API with public Swagger docs, 759 paths across two versions, but it only works with a client ID that JobDiva provides, and JobDiva has no official MCP server (checked 23 Oct 2026). The API has no webhooks, so changes have to be polled, and updates and deletes are POST calls.

How do I get access?

Sign up free, open JobDiva under Integrations in the console and press Request access. Your free trial starts with your account, no card needed.

Is the MCP server different from the API?

No, only the way in. Cotlet builds each integration as a REST API and puts an MCP server on top, so both have the same 14 tools, the same inputs and answers, one API key and one price. AI agents such as Claude, ChatGPT or Cursor use MCP; scripts, cron jobs and HTTP steps in n8n, Make or Zapier use the REST API.

What is the Cloud Browser?

Your own Chrome that Cotlet runs for you in the EU, around the clock. You open it from the console, sign in to JobDiva yourself and press Enable for agents. Your agent's calls go through it, from its IP with its cookies, so JobDiva sees the browser you signed in with. Password saving is off and the profile is stored encrypted with AES-256-GCM.

Can my agent act without asking me?

Not on anything that reaches other people: create_submittal wait for your OK by default. You can switch that off per tool for scheduled runs.

Does it work with Azure Sign In?

Yes. JobDiva's sign-in page offers Azure Sign In next to email and password, and a Choose Your Team step. You complete both yourself in your Cloud Browser. Cotlet keeps only the session, never your password.

Can the agent change timesheets, billing or pay records?

No. The tools cover candidates, notes, jobs, hotlists and submittals. JobDiva's API also has financial endpoints for timesheets, billing and payroll, but Cotlet has no tool for them.

Should I use a JobDiva MCP server from GitHub instead?

Pick one if you want the code on your own computer and do not mind the upkeep: you install it, sign it in and fix it when JobDiva changes. Pick Cotlet if you want it hosted and kept working for you.

Can I use it in n8n, Make or Zapier?

Yes. Add https://cotlet.dev/mcp/v1 in n8n's MCP Client node, or call the REST endpoints from an HTTP step in Make or Zapier.

Who runs Cotlet?

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

Is Cotlet affiliated with JobDiva?

No. Cotlet is independent and not affiliated with JobDiva.

Give your agent access to JobDiva.

Free 7-day trial with 2,000 credits, no card needed.