HR & recruiting
Personio
Time off, employees and attendance in Personio, handled by your agent.
13 endpoints
Bizneo's API cannot approve or reject absences or remote work requests, and it comes as an add-on. Sign in to Bizneo 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 Bizneo.
| What you need | Bizneo's API | GitHub MCP server | Cotlet |
|---|---|---|---|
| Absence approvals, remote work requests | No | No | Yes, 12 tools |
| Acts as you, signed in 24/7 | No | No | Yes, Cloud Browser |
| Fixed for you when Bizneo changes | N/A | No | Yes, tested every 6h |
| Runs with your laptop off | N/A | No | Yes, hosted |
Checked Oct 22, 2026. Sources: Bizneo HCM API v1 · Bizneo: Does it integrate with the tools we already use · Bizneo Help: How to request absences and holidays · Bizneo: Absence and leave management software
AI agents connect over MCP, scripts call the REST API. Both reach the same 12 tools with one API key.
Add Cotlet to your agent once. Bizneo 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/bizneo with its own method and path, such as POST /api/v1/bizneo/absence/request, with the same API key. Our open-source repo has ready scripts to start from.
12 tools on your own Bizneo account. Agents call them as operations of the MCP tools bizneo_read and bizneo_write; scripts call each one at its own REST endpoint, with the same inputs and answers.
| Tool | What it does | Access |
|---|---|---|
| list_absence_requests | Absence requests with employee, type, dates, state and comment, filtered by state, employee, type or dates. | read |
| get_absence_balance | What an employee has allotted, taken, waiting and still available for each absence type. | read |
| list_absence_types | The absence types your company configured, and whether each accepts hours or needs a document. | read |
| list_team_absences | Absences of colleagues in a date range, with type, dates and state. | read |
| list_remote_work_requests | Remote work requests waiting for a decision or already decided, with employee, day and time. | read |
| get_my_timetable | Your shifts for a range, with approved and pending remote work and the remote share of your hours. | read |
| request_absence | Sends an absence request to your manager for the dates and type you give. | writeasks first |
| cancel_absence_request | Deletes one of your absence requests that has not started yet. | writeasks first |
| approve_absence_request | Approves a pending absence request, with an optional comment for the employee. | writeasks first |
| reject_absence_request | Rejects a pending absence request, with a comment for the employee. | writeasks first |
| request_remote_work | Asks your manager to let you work remotely on the days you give, all day or in a time range. | writeasks first |
| decide_remote_work_request | Approves or rejects a pending remote work request. | writeasks first |
Scroll the table for all 12 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. Most calls use 25 credits, and your Cloud Browser uses 50 credits a day while Bizneo is enabled for agents, so 20 calls a day come to 550 credits.
| Credits | Price, one time | Calls at 25 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 200 | $5.80 |
| 15,000 | $79 | 600 | $5.27 |
| 32,000 | $149 | 1,280 | $4.66 |
| 60,000 | $249 | 2,400 | $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.
Yes, Bizneo has a documented REST API, HCM API v1 (checked 22 Oct 2026). It needs a token created in the app, and Bizneo says its API is available as an add-on. The API can request, list and delete absences and log time, but it has no endpoint to approve or reject an absence or a remote work request, and Bizneo has no official MCP server.
Sign up free, open Bizneo 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 12 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 Bizneo yourself and press Enable for agents. Your agent's calls go through it, from its IP with its cookies, so Bizneo 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: request_absence, cancel_absence_request, approve_absence_request, reject_absence_request, request_remote_work, decide_remote_work_request wait for your OK by default. You can switch that off per tool for scheduled runs.
No. Cotlet works in your signed-in Bizneo account and does not use the API. Bizneo says its API is available as an add-on and that it gives you the key, so the official route needs a quote first.
An employee account can request absences and remote work and read its own balance and timetable. Approving needs an account that Bizneo lets decide the request: approvers are set per absence type, and remote work requests are handled by the time manager or the time module admin. A call your role does not allow fails with a message saying so.
No. Clocking stays in the Bizneo app, kiosk or web clock. request_remote_work only asks for approval, and Bizneo says an approved remote work request makes it possible, but you still register it when you clock in.
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 Bizneo 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 Bizneo.
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