HR & recruiting
Personio
Time off, employees and attendance in Personio, handled by your agent.
13 endpoints
Recruiterflow's official AI connector only reads, so agents cannot move candidates, add notes or create tasks, and API keys come from its support team. Sign in to Recruiterflow 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 Recruiterflow.
| What you need | Recruiterflow's API | GitHub MCP server | Cotlet |
|---|---|---|---|
| Stage moves, notes, tasks, disqualifying | No | Partly | Yes, 14 tools |
| Acts as you, signed in 24/7 | No | No | Yes, Cloud Browser |
| Fixed for you when Recruiterflow changes | N/A | No | Yes, tested every 6h |
| Runs with your laptop off | N/A | No | Yes, hosted |
Checked Oct 23, 2026. Sources: Recruiterflow Help: Connecting Recruiterflow to ChatGPT via MCP · Recruiterflow Help: Build a custom careers page with the Recruiterflow API · Recruiterflow Help: Setting up custom webhook integrations · Recruiterflow Help: Connect Recruiterflow to Zapier
AI agents connect over MCP, scripts call the REST API. Both reach the same 14 tools with one API key.
Add Cotlet to your agent once. Recruiterflow and every other app you connect show up as its tools.
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY" {
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": {
"Authorization": "Bearer ${COTLET_API_KEY}"
}
}
}
} # ~/.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.
Every tool is an endpoint under /api/v1/recruiterflow with its own method and path, such as POST /api/v1/recruiterflow/candidates/{candidate_id}/notes, with the same API key. Our open-source repo has ready scripts to start from.
14 tools on your own Recruiterflow account. Agents call them as operations of the MCP tools recruiterflow_read and recruiterflow_write; scripts call each one at its own REST endpoint, with the same inputs and answers.
| Tool | What it does | Access |
|---|---|---|
| list_jobs | Jobs of your workspace with client company, visibility and candidate count. | read |
| get_job | One job with its hiring team and pipeline stages, each with the number of candidates. | read |
| list_candidates | Search candidates by name, tag, source or job, with title, company and tags. | read |
| get_candidate | One candidate with contact details, tags, custom fields, jobs with stages and latest notes. | read |
| list_job_candidates | Candidates of one job with their stage, the date they entered it and the last activity. | read |
| list_activities | The Activity Log of a candidate: emails, calls, meetings, notes and stage moves, newest first. | read |
| list_tasks | Your tasks: due, overdue or all, with type, priority, due date and the linked record. | read |
| add_candidate | Create a candidate with a name and optional email, phone, company and title. | write |
| add_candidate_to_job | Add one or more candidates to an open job, in its first stage. | write |
| move_candidate_stage | Move a candidate to another stage of a job. | writeasks first |
| disqualify_candidate | Disqualify a candidate from one job with a reason from your workspace list. | writeasks first |
| add_note | Add a note to a candidate, shared with the hiring team or private. | writeasks first |
| create_task | Create a task with a type, priority, assignee and due date, linked to a candidate. | writeasks first |
| close_job | Close an open job and take it off every connected job board. | writeasks first |
Scroll the table for all 14 tools.
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+.
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 Recruiterflow is enabled for agents, so 20 calls a day come to 250 credits.
| 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.
Recruiterflow has an API, but its keys are not self-serve: you ask Recruiterflow support for a key tied to your workspace (checked 23 Oct 2026). Its official MCP for ChatGPT, Claude and Microsoft Copilot is read-only, so an agent can search and read but cannot move candidates, add notes or create tasks.
Sign up free, open Recruiterflow under Integrations in the console and press Request access. Your free trial starts with your account, no card needed.
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.
Your own Chrome that Cotlet runs for you in the EU, around the clock. You open it from the console, sign in to Recruiterflow yourself and press Enable for agents. Your agent's calls go through it, from its IP with its cookies, so Recruiterflow sees the browser you signed in with. Password saving is off and the profile is stored encrypted with AES-256-GCM.
Not on anything that reaches other people: move_candidate_stage, disqualify_candidate, add_note, create_task, close_job wait for your OK by default. You can switch that off per tool for scheduled runs.
No. Cotlet works in your own signed-in Recruiterflow account, with your role. Recruiterflow's own API keys are issued by its support team on request and are tied to a workspace; the help center does not say which plan includes them (Recruiterflow Help, checked 23 Oct 2026).
An admin can make fields mandatory on a stage under Settings > Job Settings > Customize Stage Settings, a feature of the Advanced Plan and Custom Plan. A move into a Hired stage usually asks for placement details and a move into a Rejected stage asks for a disqualification reason. The tool returns these questions and moves nothing until they are answered.
Text only: nothing uploads files or CVs. Sequences, Recipes, scorecards, placements and revenue, job creation and deletes are not built, and Cotlet never changes your account settings, users or billing. Official Recruiterflow MCP and your normal login keep working next to it.
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 Recruiterflow changes. Pick Cotlet if you want it hosted and kept working for you.
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.
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.
No. Cotlet is independent and not affiliated with Recruiterflow.
Free 7-day trial with 2,000 credits, no card needed.
May we use Google Analytics to see which pages help people? It sets cookies only if you accept. No ads, and we never sell data. Cookie policy