JobAdder MCP Server
JobAdder 帳戶的候選人、申請、備註和任務。
託管 MCP 伺服器
npx add-mcp 'https://cotlet.dev/mcp/v1/jobadder'可安裝到 Claude Code、Codex、Cursor 等客戶端
文件
Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up
JobAdder API and MCP server: Let your AI agent clear the JobAdder applicant queue.
JobAdder has no MCP server (checked 27 Oct 2026). Its API v2 has 395 operations and covers every job on this page, but credentials go only to a partner whose developer account JobAdder approves, an admin must grant the app access, and Lite has no API at all. Cotlet runs 12 JobAdder tools hosted, over MCP for agents and REST for scripts, in your own login on any plan.
Candidates, applications, notes and tasks for your JobAdder account. 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 JobAdder
- Page: https://cotlet.dev/integrations/jobadder-api-mcp-server
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by JobAdder. JobAdder is a trademark of its owner. If JobAdder's own integrations cover what you need, use them first.
What can you automate in JobAdder?
- Rate new applicants against your brief
- Reject clear mismatches after your OK
- Log call notes on the right candidate
- Add candidates from emails and CVs
- Set check-in tasks for new starters
- List open jobs with unrated applicants
Does JobAdder have an MCP server or an API?
- JobAdder's partner guide says "Do not ask the JobAdder users to register their own developer account", so a recruiter cannot get keys alone. API + Sandbox is "only available for contracted customers (free for Pro customers)".
- Zapier has a JobAdder app with 25 actions and 13 searches, among them Add Candidate Note, Update Application Status and Create User Task. It has no action to rate an application and none to list your tasks.
- Adder Intelligence (Smart Summaries, Smart Floats and more) runs inside JobAdder from Essential up. No outside agent can call it.
| What you need | JobAdder API | Zapier and Zapier MCP | Cotlet |
|---|---|---|---|
| Search candidates and jobs | Yes | Find and Get searches | Yes |
| Add notes, create candidates and tasks | Yes | Yes | Yes, after your OK |
| Move an application to a status | Yes | Yes | Yes, after your OK |
| Rate applications out of 5 | Yes | No | Yes |
| Works on Lite | No | Uses the API, not stated | Yes |
| What you need first | Approved partner app and admin consent | Admin consent and a Zapier plan | Your own JobAdder login |
Checked 27 Oct 2026. Sources: JobAdder API v2 reference, JobAdder API (partner help center), JobAdder API Terms, JobAdder plans, JobAdder on Zapier
How does Cotlet connect to JobAdder?
- Sign in to JobAdder. 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 JobAdder password, and no status change, note, candidate or task is saved before you approve it.
Connect JobAdder 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 JobAdder in a Cloud Browser. Create a Cotlet account, open JobAdder in its Cloud Browser, sign in with your own JobAdder user on any plan, Lite included, and press Enable for agents.
- Add the Cotlet address. Put https://cotlet.dev/mcp/v1 into your agent's MCP server or connector settings.
- Allow the connection. Chat apps open a Cotlet sign-in page. Code editors, n8n and scripts use an API key from the console instead.
https://cotlet.dev/mcp/v1 serves every Cotlet app you enable, JobAdder included. Enable JobAdder after connecting and the connector needs a refresh before its tools show up.
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: jobadder_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: jobadder_write
How to use the JobAdder REST API
Create your Cotlet API key
Create a Cotlet API key with access to JobAdder and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.
Connect JobAdder in Cotlet and enable it for agents. Account access: Your own JobAdder user. What the agent can see and change follows that user's permissions in JobAdder.
Make your first JobAdder API request
REST:
curl https://cotlet.dev/api/v1/jobadder/jobs/search \
-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": "jobadder",
"tool": "search_jobs",
"result": {
"jobs": [
{
"job_id": "job_5521",
"title": "Senior Accountant",
"company": "Harbour Partners",
"status": "Open",
"applications": 17
}
],
"next_cursor": null
}
}
Returns a page of jobs your JobAdder user can see, each with job_id, title, company, status and the number of applications. Pass next_cursor back as cursor for the next page.
The job_id goes into get_job, list_job_applications and list_placements.
limit: Maximum jobs to return.
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.
JobAdder workflows for agents and automations
| Tool | Connect through | Example workflow |
|---|---|---|
| n8n | HTTP Request | One job with its description, company, contact and status. Use get_job in your configured team report. |
| Make | HTTP > Make a request | Applications on one job with candidate, status, rating and date. Use list_job_applications in your configured team report. |
| Python or Node.js | REST API | Your JobAdder tasks by view: active, priority, unscheduled, overdue or complete. 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 JobAdder; 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.
JobAdder API endpoints and MCP tools
Jobs and applications
Status names are the ones in the job's own workflow, custom rejection statuses included. A rating reaches no candidate.
- Search jobs (
search_jobs, read): Jobs matching a title or keyword, with company and status. - Get job (
get_job, read): One job with its description, company, contact and status. - List job applications (
list_job_applications, read): Applications on one job with candidate, status, rating and date. - Rate application (
rate_application, write): Set the rating out of 5 on a job application. - Update application status (
update_application_status, write, asks first): Move a job application to another status of its workflow.
Candidates and notes
Resume files are neither read nor uploaded. Search before you create: duplicates are not merged.
- Search candidates (
search_candidates, read): Candidates matching a name, email, phone or resume keyword. - Get candidate (
get_candidate, read): One candidate record with skills, employment history, applications and recent notes. - Add candidate note (
add_candidate_note, write, asks first): Add a text note to a candidate record. - Create candidate (
create_candidate, write, asks first): Create a candidate record with name and contact details.
Placements and tasks
Tasks are created for the signed-in user only, never for a colleague.
- List placements (
list_placements, read): Placements, optionally of one job, with candidate, start date and status. - List tasks (
list_tasks, read): Your JobAdder tasks by view: active, priority, unscheduled, overdue or complete. - Create task (
create_task, write, asks first): Create a task for you, optionally linked to a candidate.
Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/jobadder-api-mcp-server#tools
Who can see my JobAdder session, and how do I revoke it?
- What we store. Your signed-in JobAdder profile, encrypted with AES-256-GCM, in Finland. Never the password.
- What your agent gets. 12 JobAdder tools. No cookie, no login, no API token.
- What the session sees. What your JobAdder user sees. Permissions follow your role in JobAdder.
- What no tool touches. Invoices, timesheets, job ads, emails, SMS, users and admin settings.
- If JobAdder 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, and under JobAdder's terms your agency is the data controller. Cotlet processes it only to run the calls you make (DPA). The Cotlet site has A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
Approvals, undo and mistakes
- Reads the intake. Every application on the job, page by page, with the job description as the brief.
- Rates each one. A score out of 5 with the line of the profile it relied on.
- Waits for your OK. Each rejection waits in your Cotlet console, because a status can fire an automatic reply.
- Reports back. Who scored 4 or 5, who was rejected, and the grey zone left for you.
| Action | Undo |
|---|---|
| Rate an application | Rate again; nobody outside your team saw it |
| Update an application status | Set the old status back; an automatic reply may have gone out |
| Add a candidate note | Edit it in JobAdder; no Cotlet tool deletes notes |
| Create a candidate | No Cotlet tool deletes it; handle it in JobAdder |
| Create a task | Complete or delete it in JobAdder |
4 of the 5 write tools ask first. rate_application runs at once, because a rating reaches no candidate and changes with one more call. Reads run at once too. For a scheduled run you can switch the wait off per tool.
A status the job's workflow does not have makes update_application_status fail, so a typo never moves anyone. The agent lists that applicant for you instead.
MCP call:
{
"name": "update_application_status",
"arguments": {
"application_id": "app_48213",
"status": "Phone screen"
}
}
REST:
curl -X PATCH https://cotlet.dev/api/v1/jobadder/applications/app_48213/status \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"status":"Phone screen"}'
Response:
{
"application_id": "app_48213",
"previous_status": "New",
"status": "Phone screen"
}
A nightly script or your careers site handler can call the same tools over REST at /api/v1/jobadder, with the same key and price as MCP. A record your JobAdder user cannot open returns an error and costs nothing. Each tool row above shows its REST path.
How much does the JobAdder MCP server cost?
About $55 a month for one recruiter with about 6 open jobs, 9,420 credits. JobAdder itself is quote only; third-party estimates run from $95 to over $200 a user a month.
| Job | Calls | Credits |
|---|---|---|
| Rate new applicants on 6 jobs, each workday | 20 × 22 | 4,400 |
| Log call notes on 4 candidates, each workday | 12 × 22 | 2,640 |
| Add candidates from the inbox | 4 × 10 | 400 |
| Open jobs and unrated applicants, weekly | 7 × 4 | 280 |
| Check-in tasks for new placements, weekly | 5 × 4 | 200 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 9,420 |
- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
The month is our example: one recruiter at a 10-user agency, about 6 open jobs, applicants rated and call notes logged on 22 workdays, plus weekly digests and placement tasks. Essential is sold for 6 to 20 users; Compono budgets $12,000 to $24,000 a year for 10. Dollars at the $29 pack rate.
JobAdder MCP server on GitHub, Zapier or hosted: which to use
| Option | What it does | Where it stops |
|---|---|---|
| StackOne JobAdder MCP | Hosted MCP with 247 actions on the JobAdder API, OAuth per user. Built for software companies that embed agents. | Runs on the API, so Lite is out; no rating action listed; price on request. |
| Apideck JobAdder MCP | Unified ATS tools for jobs, applicants and applications. | Three resources only, no notes, ratings or tasks. |
| Intiqo/jobadder-go-sdk | A Go SDK for the API, Apache-2.0. 1 star, last commit 11 Feb 2026. | No MCP; needs approved partner credentials. |
| varspool/jobadder-api-client | A PHP API client. 7 stars, last commit 27 Jun 2017. | No license, unmaintained, same credentials problem. |
If you sell software to recruiters, apply to be a JobAdder partner and build on the API. If one event in JobAdder should start one action elsewhere, Zapier is enough on Essential or Pro. If your agent should read applicants, rate them against a brief and do the follow-up in your own login, Cotlet does that hosted, Lite included.
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). Questions about the JobAdder tools go to contact@cotlet.dev.
JobAdder API and MCP: questions
How do I get access?
Sign up free at https://cotlet.dev, open JobAdder under Integrations in the console and sign in to JobAdder in its Cloud Browser. The trial starts when you sign up, no card.
How do I connect JobAdder to ChatGPT or Claude?
Sign up at cotlet.dev, log in to JobAdder 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 JobAdder account through Cotlet, in their phone apps too.
What can ChatGPT do in JobAdder?
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in JobAdder: screen new job applicants; log call notes on candidate records; weekly open jobs and applicants digest. You ask in plain words, and anything that reaches other people waits for your OK first.
Do I need JobAdder API access or the Pro plan?
No. Cotlet works in your own JobAdder login and does not use the API. JobAdder's pricing page lists API access on Essential and Pro and calls the API + Sandbox add-on not available on Lite. What you can see and change still follows your user's permissions in JobAdder.
Can the agent email or message candidates?
No tool sends an email or an SMS. A status change can still trigger an action in JobAdder, such as an automatic reply, because JobAdder lets a status update trigger actions. That is why update_application_status waits for your OK by default.
Does JobAdder have webhooks?
Yes, for API partners: 42 events such as an application status change or an approved placement. Cotlet sends no webhooks, so to react to new applicants, run your agent on a schedule.
Can the agent read resumes?
It reads the parsed profile: skills, employment history and education. The original resume file is not returned, and create_candidate uploads none.
Is the MCP server different from the REST API?
Only in how you call it. Both expose the same 12 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts use REST.
Is Cotlet affiliated with JobAdder?
No. Cotlet is independent and not affiliated with JobAdder Operations Pty Ltd.
Can I use the JobAdder 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.