JazzHR MCP Server
Kandidaten verschieben, ihnen E-Mails senden und Jobs in Ihrem JazzHR verwalten.
Gehosteter MCP-Server
npx add-mcp 'https://cotlet.dev/mcp/v1/jazzhr'Installiert in Claude Code, Codex, Cursor und mehr
Dokumentation
Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up
JazzHR API and MCP server: Let your AI agent keep the JazzHR pipeline moving.
JazzHR has no MCP server of its own (checked 27 Oct 2026). Its API comes with every plan and has 35 operations, all GET or POST: it reads jobs, applicants, workflows and tasks, and adds applicants, notes, files and jobs. Cotlet runs 13 JazzHR tools hosted, over MCP for agents and REST for scripts, including the five the API cannot do.
Move candidates, email them and manage jobs in your JazzHR. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.
- Free 7-day trial, no card
- Unofficial, not affiliated with JazzHR or Employ
- Page: https://cotlet.dev/integrations/jazzhr-api-mcp-server
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by JazzHR. JazzHR is a trademark of its owner. If JazzHR's own integrations cover what you need, use them first.
What can you automate in JazzHR?
- Screen new applicants by your rules
- Move candidates to the next stage
- Decline everyone left on a filled job
- Email candidates from your templates
- Create interview feedback tasks
- Report stage counts for each open job
Does JazzHR have an MCP server or an API?
- JazzHR's help article calls its API "technically not RESTful in that it does not have PUT and DELETE requests". Nothing changes a candidate's stage, a job's status or a task once it exists.
- Only Super Administrators, Recruiting Administrators and Developers see the API key, and generating a new key turns off the old ones.
- Zapier says "Jazz has not yet built an integration on Zapier". The only webhook is Candidate Export on Pro, and it only sends data out.
| What you need | JazzHR API | StackOne, Knit | Cotlet |
|---|---|---|---|
| Read jobs, candidates and answers | Yes, 100 a page | Yes | Yes |
| Add a note or a draft job | Yes | Yes | Yes |
| Move a candidate to a stage | No | Knit lists it | Yes, after your OK |
| Bulk change status | No | No | Yes, after your OK |
| Email a candidate | No | No | Yes, from your templates |
| Create a task, open or close a job | No | No | Yes, after your OK |
| What you need first | An admin role and a key | A developer account and the key | Your JazzHR login |
Checked 27 Oct 2026. Sources: JazzHR API reference, JazzHR Help: API Overview, JazzHR API and platform documentation, Jazz on Zapier, JazzHR Help: Building Candidate Export Integrations
How does Cotlet connect to JazzHR?
- Sign in to JazzHR. Use your own account in its Cotlet Cloud Browser.
- Choose MCP or REST. Connect your agent or create a Cotlet API key.
- Run your workflow. Ask your agent or send an HTTP request.
We never keep your JazzHR password, and no stage change, email or task a candidate or teammate would notice happens before you approve it.
Connect JazzHR to your agent or workflow
Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.
- Sign in to JazzHR in a Cloud Browser. Create a Cotlet account, open JazzHR in its Cloud Browser, log in with your own JazzHR user and press Enable for agents. No API key needed.
- Add the Cotlet address. Paste https://cotlet.dev/mcp/v1 into the MCP server or connector field of your agent.
- Approve the connection. Chat apps show a Cotlet sign-in page. Editors, n8n and scripts send an API key you make in the console.
All your Cotlet apps, JazzHR included, share one address: https://cotlet.dev/mcp/v1. Enable JazzHR after you connect and the agent needs a refresh of the connector to see its tools.
Claude:
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY"
ChatGPT:
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
Cursor:
// ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
}
Codex:
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
n8n:
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: jazzhr_read
Make, Zapier:
Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: jazzhr_write
How to use the JazzHR REST API
Create your Cotlet API key
Create a Cotlet API key with access to JazzHR and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.
Connect JazzHR in Cotlet and enable it for agents. Account access: Your own JazzHR user login. What your agent can do follows your role: moving candidates, emailing and job status need the same rights you have by hand. You sign in in your own browser.
Make your first JazzHR API request
REST:
curl https://cotlet.dev/api/v1/jazzhr/jobs \
-H "Authorization: Bearer $COTLET_API_KEY"
Read jobs and apply the operation limits
A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.
Illustrative response excerpt:
{
"status": "success",
"app": "jazzhr",
"tool": "list_jobs",
"result": {
"jobs": [
{
"job_id": "job_20261012_8f3a",
"title": "Senior Support Agent",
"status": "Open",
"department": "Support",
"location": "Austin, TX",
"open_date": "2026-10-12"
},
{
"job_id": "job_20260922_41cb",
"title": "Account Executive",
"status": "Filled",
"department": "Sales",
"location": "Remote",
"open_date": "2026-09-22"
}
],
"next_cursor": null
}
}
Lists jobs of your JazzHR account, 100 to a page; pass next_cursor back as cursor for the next page. status is the job status JazzHR shows, and only Open jobs appear on the careers page and free job boards. Use job_id as the job parameter of the other tools.
cursor: Next page cursor from the previous call.
Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.
JazzHR workflows for agents and automations
| Tool | Connect through | Example workflow |
|---|---|---|
| n8n | HTTP Request | Candidates of a job with stage, rating and apply date, filtered by stage, status or name. Use list_candidates in your configured team report. |
| Make | HTTP > Make a request | One candidate with contact details, questionnaire answers, source and notes on the job. Use get_candidate in your configured team report. |
| Python or Node.js | REST API | Open and done tasks with the candidate, assignee and due date. Use list_tasks in your configured team report. |
Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.
Cotlet reads JazzHR; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.
Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.
The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.
JazzHR API endpoints and MCP tools
Candidates and stages
Stage names differ per workflow, so the agent reads them per job first. A move can fire the workflow helpers on the new stage, which may email the candidate.
- List candidates (
list_candidates, read): Candidates of a job with stage, rating and apply date, filtered by stage, status or name. - Get candidate (
get_candidate, read): One candidate with contact details, questionnaire answers, source and notes on the job. - List workflow stages (
list_workflow_stages, read): The stages of the workflow a job uses, in order, with the closing statuses such as Not Hired. - Change candidate status (
change_candidate_status, write, asks first): Move one candidate to a workflow stage of their job, or to a closing status such as Not Hired. - Bulk change status (
bulk_change_status, write, asks first): Move a group of candidates of one job to a stage or closing status in one pass.
Emails and notes
Emails go from the candidate's Emails tab, so the thread stays in JazzHR. Notes belong to one job and stay with the hiring team.
- Send candidate email (
send_candidate_email, write, asks first): Email one candidate from their profile, from a template or with your own text. - Add candidate note (
add_candidate_note, write, asks first): Add a note to a candidate on one job, visible to your hiring team.
Tasks
With email notice on, the assignee gets a Go to Candidate link.
- List tasks (
list_tasks, read): Open and done tasks with the candidate, assignee and due date. - Create task (
create_task, write, asks first): Create a task on a candidate for a teammate, with a due date and optional email notice.
Jobs
Only Open jobs reach your careers page and the free job boards. A new job starts as Drafting.
- List jobs (
list_jobs, read): Jobs of your account with status, department and location, filtered by status or title. - Get job (
get_job, read): One job with its description, hiring lead, workflow and status. - Create job (
create_job, write): Create a job as Drafting or Open from a title, description and basic fields. - Set job status (
set_job_status, write, asks first): Change a job to Open, On Hold, Drafting, Filled, Cancelled or Closed.
Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/jazzhr-api-mcp-server#tools
Who can see my JazzHR session, and how do I revoke it?
- What we store. Your signed-in JazzHR profile, encrypted with AES-256-GCM, in Finland. Never the password.
- What your agent gets. 13 JazzHR tools. No cookie, login or API key.
- What the session sees. What your JazzHR role sees. An Interviewer sees less than a Super Admin.
- What no tool touches. Offers and eSignatures, billing, users, settings and the API key.
- If JazzHR signs you out. We email you a sign-in link. You sign in yourself, we never do.
- How to cut access. Disable for agents, reset the browser or delete the key. The next call fails.
Candidate records hold personal data your company answers for, so keep the agent's notes to hiring facts. The Cotlet site has A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
Approvals, undo and mistakes
- Reads the stage. New applicants since the last run, with their questionnaire answers.
- Sorts them. Matches, misses and unclear ones, each with the answer it used.
- Waits for your OK. Each move and note waits in your Cotlet console.
- Checks again. If a colleague moved someone in the meantime, it leaves them alone.
| Action | Undo |
|---|---|
| Move a candidate | Move them back; a helper email may already be out |
| Bulk change status | Move the group back; same caveat |
| Email a candidate | No; once sent, it is in their inbox |
| Add a note | No tool removes it; only your team sees it |
| Create a task | Mark it done in JazzHR; the notice email is out |
| Change job status | Set the old status; job boards may have picked it up |
6 of the 7 write tools ask first. create_job runs at once because it saves a Drafting job that no candidate or job board sees; opening it is set_job_status, which asks. Reads run at once. For a scheduled run you can switch the wait off per tool.
Each candidate row is one person on one job. Someone who applied to two jobs is moved on the job you name only.
MCP call:
{
"name": "change_candidate_status",
"arguments": {
"candidate_id": "prospect_20261019_5e2c",
"job_id": "job_20261012_8f3a",
"status": "Phone Screen"
}
}
REST:
curl -X PATCH https://cotlet.dev/api/v1/jazzhr/jobs/job_20261012_8f3a/candidates/prospect_20261019_5e2c/status \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"status":"Phone Screen"}'
Response:
{
"candidate_id": "prospect_20261019_5e2c",
"job_id": "job_20261012_8f3a",
"previous_stage": "New",
"stage": "Phone Screen"
}
A cron job or your HR system can call the same tools over REST at /api/v1/jazzhr, with one key and one price. A call your JazzHR role cannot make returns an error and costs nothing. Every tool row above lists its REST path.
How much does the JazzHR MCP server cost?
About $32 a month for one recruiter with 6 open jobs, 5,500 credits. Works on Hero, Plus or Pro; JazzHR starts at $1,000 a year.
| Job | Calls | Credits |
|---|---|---|
| Screen new applicants, each workday | 10 × 22 | 2,200 |
| Interview follow-up tasks, each workday | 3 × 22 | 660 |
| Close a filled job, 25 declines | 28 × 2 | 560 |
| Pipeline report for 6 jobs, weekly | 13 × 4 | 520 |
| Draft and open a new job | 3 × 2 | 60 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 5,500 |
- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- No API key or admin role needed
The month is our example: 6 open jobs, five applicants screened each workday, a feedback task after each day's interviews, two filled jobs with 25 declines each and a weekly report. JazzHR publishes no typical size; Enlyft says most of its customers have 50 to 200 employees. Dollars at the $29 pack rate.
JazzHR MCP server on GitHub, Zapier or hosted: which to use
| Option | What it does | Where it stops |
|---|---|---|
| StackOne JazzHR MCP | 26 hosted actions on the official API: jobs, candidates, applications, notes, files, users. | The API limits apply: no stage move, email, task or job status. |
| Knit JazzHR ATS MCP | 9 actions from a unified ATS API, including Update Application Stage. 30-day trial. | Built for software companies; the stage action is generic across ATSs, and there is no email or tasks. |
| jordanandree/jazz-api | A PHP wrapper for the old Resumator API. 6 stars, last push 19 Sep 2016. | No MCP, unmaintained, same API limits. |
If your own product syncs JazzHR data, the API key and a unified API like StackOne or Knit fit. If a candidate only needs to reach your HRIS, the Candidate Export webhook on Pro covers it. If your agent should move candidates, email them and add tasks for your team, Cotlet does that hosted.
Who runs Cotlet
Take Group sp. z o.o. runs Cotlet: a software company registered in Poland, EU (VAT PL6342984273), in business since 2019. The founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Write to contact@cotlet.dev with questions about the JazzHR tools.
JazzHR API and MCP: questions
How do I get access?
Sign up free at https://cotlet.dev, open JazzHR under Integrations in the console and log in to JazzHR in its Cloud Browser. The trial starts when you sign up and needs no card.
How do I connect JazzHR to ChatGPT or Claude?
Sign up at cotlet.dev, log in to JazzHR once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your JazzHR account through Cotlet, in their phone apps too.
What can ChatGPT do in JazzHR?
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in JazzHR: reject remaining candidates when a job is filled; advance applicants by your screening rules; create follow-up tasks for new candidates. You ask in plain words, and anything that reaches other people waits for your OK first.
Which JazzHR plan and role do I need for the API key?
JazzHR's API Overview says the API is included with all subscription levels, and the key sits under Settings > Integrations. It names Super Administrators, Recruiting Administrators and Developers as the roles that see it, so check your plan and role in your own account. Cotlet needs neither a key nor a plan feature: it works in your signed-in JazzHR with your role.
Does generating a new JazzHR API key affect Cotlet?
No. Cotlet uses your signed-in session, not the API key. JazzHR's own help warns that generating a new key deactivates the existing ones, which breaks any other tool that holds the old key.
Does JazzHR have webhooks?
One kind: Candidate Export, included on Pro. JazzHR posts a candidate to your URL when someone exports them by hand or an automatic export fires, and it receives nothing back. To react to new applicants, run your agent on a schedule and read the stage.
Does it work with JazzHR's AI Screening or Talent Fit?
They run inside JazzHR and keep working as before. get_candidate returns the rating and answers your agent can see on the profile; no tool starts a VONQ screening.
Is the MCP server different from the REST API?
Only in how you call it. Both have the same 13 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts and HR systems use REST.
Is Cotlet affiliated with JazzHR?
No. Cotlet is independent and not affiliated with JazzHR or Employ Inc.
Can I use the JazzHR API without an AI agent?
Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.
Give your AI agents your signed-in browser.
Product: Integrations · How it works · Pricing · Security
Resources: Blog · API docs · Help center · Changelog · GitHub
Solutions: For developers · For automation agencies
Company: About · AI info: company facts · Contact
Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors
Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub
Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.