[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup) # CharlieHR API and MCP server > CharlieHR has an API, but a narrow one, and no official MCP server (checked 20 Oct 2026). A Super Admin creates a Client ID and Client Secret under Company > Integrations > API Access; the API covers team members, leave, offices and teams. It has no action to approve leave, book time off, adjust an allowance or offboard someone. HR software for small companies: team member profiles, time off, checklists, documents, reports and recruiting in one account. ## What is the CharlieHR API? Cotlet's CharlieHR API exposes 12 endpoints for your own CharlieHR account: list team members, get a team member, list time off requests, get a time off allowance, get who is working, approve a time off request, deny a time off request, book time off for someone, record a sick day, adjust a time off allowance, cancel a time off booking and offboard a team member. The list_team_members endpoint returns people in your CharlieHR account with office, team, line manager and start date. Each endpoint takes simple JSON inputs like member_id, notes or status and works both as an operation of the charliehr_read or charliehr_write MCP tool for agents and as a REST call for scripts. - **Category:** [HR & recruiting](https://cotlet.dev/integrations/category/hr-recruiting.md) - **Endpoints:** 12 (5 read, 7 write) - **Updated:** 2026-10-22 CharlieHR has an API, but a narrow one, and no official MCP server (checked 20 Oct 2026). Cotlet is a hosted MCP server and REST API for CharlieHR with 12 endpoints (5 read, 7 write): you sign in once in your own cloud browser, your AI agent does the work. ## Does CharlieHR have an official API? CharlieHR has an API, but a narrow one, and no official MCP server (checked 20 Oct 2026). A Super Admin creates a Client ID and Client Secret under Company > Integrations > API Access; the API covers team members, leave, offices and teams. It has no action to approve leave, book time off, adjust an allowance or offboard someone. | Task | CharlieHR official | Cotlet | |---|---|---| | List team members and their profiles | Yes: The API reads team members, offices and teams | Yes | | List time off requests | Partly: The API reads leave requests, without the pending queue an approver sees | Yes | | Read time off allowances | Partly: The API reads leave allowances, not adjustments with expiry dates | Yes | | See who is working and who is off | Partly: Built from leave requests, not from the Who's Working page | Yes | | Approve or deny time off requests | No | Yes | | Book time off or record a sick day for someone | No | Yes | | Adjust a time off allowance | No | Yes | | Cancel a time off booking | No | Yes | | Offboard a team member | No | Yes | Sources: [CharlieHR Help: Integrate Charlie with selected apps (API Access)](https://help.charliehr.com/en/articles/6193173-integrate-charlie-with-selected-apps), [CharlieHR Help: Integrating your product with Charlie](https://help.charliehr.com/en/articles/9579162-integrating-your-product-with-charlie), [CharlieHR API documentation](https://app.charliehr.com/api_docs), [CharlieHR Help: Roles and permissions](https://help.charliehr.com/en/articles/2844905-roles-and-permissions) ## For AI agents ```text CharlieHR has an API, but a narrow one, and no official MCP server (checked 20 Oct 2026). A Super Admin creates a Client ID and Client Secret under Company > Integrations > API Access; the API covers team members, leave, offices and teams. It has no action to approve leave, book time off, adjust an allowance or offboard someone. Cotlet provides a hosted MCP server and REST API for CharlieHR: 12 tools (5 read, 7 write). Access Sign up at https://cotlet.dev/app/signup?app=charliehr, then request the app and create API keys in the Cotlet console. MCP server https://cotlet.dev/mcp/v1 MCP tools charliehr_read, charliehr_write, reads and writes apart; call one with {"operation": "", "arguments": {...}} REST base https://cotlet.dev/api/v1/charliehr, each operation at its own route, e.g. POST /api/v1/charliehr/requests/{request_id}/time-off-request/approve Auth Authorization: Bearer . Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in. Operations list_team_members, get_team_member, list_time_off_requests, get_time_off_allowance, get_whos_working, approve_time_off_request, deny_time_off_request, book_time_off, record_sick_day, adjust_time_off_allowance, cancel_time_off_booking, offboard_team_member Confirm approve_time_off_request, deny_time_off_request, book_time_off, record_sick_day, adjust_time_off_allowance, cancel_time_off_booking, offboard_team_member (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations) Markdown https://cotlet.dev/integrations/charliehr-api-mcp-server.md How access works: 1. The user signs up at https://cotlet.dev/app/signup?app=charliehr, requests CharlieHR in the Cotlet console and creates an API key there. 2. The user signs in to CharlieHR once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables CharlieHR for agents. An agent cannot do this step. 3. The API key goes into the MCP client or the REST call as a bearer token. Fits: people who want a hosted CharlieHR server that someone else maintains, including non-developers. Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA. Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev. Sign-in: the user signs in to CharlieHR in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get CharlieHR only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273). API key: holds no CharlieHR login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once. Terms: the user stays responsible for following CharlieHR's terms; Cotlet is not affiliated with CharlieHR. ``` ## What can an AI agent do in CharlieHR? Cotlet is best for HR leads and office managers at small companies who want an agent to approve routine leave, adjust allowances and offboard leavers without running or fixing a server. - **[Approve routine time off requests](https://cotlet.dev/integrations/charliehr-api-mcp-server/approve-time-off-requests.md)** (runs: daily): "Go through pending time off requests in CharlieHR. Approve holiday that fits the person's remaining allowance and leaves at least two people working each day, deny nothing, and list the rest for me with a one-line reason." → `list_time_off_requests`, `get_time_off_allowance`, `get_whos_working`, `approve_time_off_request`, `deny_time_off_request` - **[Offboard a leaver](https://cotlet.dev/integrations/charliehr-api-mcp-server/offboard-a-leaver.md)**: "Offboard Daniel Kim from CharlieHR with leaving date 30 November, reason Resignation, and tell me his pro-rated holiday for this leave year." → `get_team_member`, `offboard_team_member` - **[Adjust leave allowances](https://cotlet.dev/integrations/charliehr-api-mcp-server/adjust-leave-allowances.md)**: "Add 2 extra days to the CharlieHR allowance of everyone in the Support team, expiring 31 December, with a note that it is for the October release weekend." → `list_team_members`, `get_time_off_allowance`, `adjust_time_off_allowance` - **Record sick days from a message**: "Sam Rivera messaged that he is ill today and tomorrow. Record it as sick leave in CharlieHR." → `get_team_member`, `record_sick_day` - **Check who is off this week** (runs: weekly): "Every Monday, list who is off or working from home this week in CharlieHR and post the summary to me." → `get_whos_working`, `list_time_off_requests` ## Can CharlieHR automations run on a schedule in n8n, Make or Zapier? Yes. Cotlet does not replace your automation platform: it gives it a CharlieHR connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to approve routine time off requests, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off. | Where | How to connect | How to schedule | |---|---|---| | Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. | | n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/charliehr/time-off-requests. | Schedule Trigger node. | | Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. | | Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. | | Your own script | GET https://cotlet.dev/api/v1/charliehr/time-off-requests with your API key. | cron or GitHub Actions. | ## Tools **For AI agents:** Every endpoint and its schema is public. The 12 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to CharlieHR. ### list_team_members People in your CharlieHR account with office, team, line manager and start date. Access: read. REST: `GET /api/v1/charliehr/team-members`. MCP: `charliehr_read → list_team_members`. | Parameter | Type | Required | Description | |---|---|---|---| | `status` | string | no | active (default) or archived | | `office` | string | no | Office name | | `team` | string | no | Team name | | `query` | string | no | Part of the name | Lists team members the signed-in role can see, by name. status active returns current people and archived returns offboarded ones. office and team filter by name. Each item has the member id other tools take. Salary and bank details are never returned. Example response: ```json { "members": [ { "member_id": "tm_31c9e4", "name": "Ana Lopez", "job_title": "Support Agent", "office": "London", "team": "Support", "line_manager": "Maya Cole", "start_date": "2023-03-06", "role": "Member" }, { "member_id": "tm_7d20ab", "name": "Daniel Kim", "job_title": "Account Executive", "office": "London", "team": "Sales", "line_manager": "Maya Cole", "start_date": "2022-09-12", "role": "Member" } ] } ``` ### get_team_member One profile: office, team, line manager, start date, role and working week. Access: read. REST: `GET /api/v1/charliehr/team-member`. MCP: `charliehr_read → get_team_member`. | Parameter | Type | Required | Description | |---|---|---|---| | `member_id` | string | no | Id from list_team_members | | `name` | string | no | Exact name, used when member_id is not known | Returns the profile of one team member by id or exact name. Use it to confirm the right person before a write. The line manager and team are the people who can approve that person's leave. Pay and bank details are not part of the response. Example response: ```json { "member_id": "tm_7d20ab", "name": "Daniel Kim", "job_title": "Account Executive", "office": "London", "team": "Sales", "line_manager": "Maya Cole", "start_date": "2022-09-12", "role": "Member", "archived": false } ``` ### list_time_off_requests Time off requests with person, type, dates, days and status. Access: read. REST: `GET /api/v1/charliehr/time-off-requests`. MCP: `charliehr_read → list_time_off_requests`. | Parameter | Type | Required | Description | |---|---|---|---| | `status` | string | no | pending, upcoming or past | | `member_id` | string | no | Only this person | | `from` | string | no | Earliest start date, YYYY-MM-DD | | `to` | string | no | Latest start date, YYYY-MM-DD | Returns requests in the three groups the Time tab shows: pending, upcoming (approved) and past. The role decides what you see: everyone for an Admin or Super Admin, direct reports for a Line Manager, the team for a Team Lead. A custom approver sees the requests assigned to them. Sorted by start date. Example response: ```json { "requests": [ { "request_id": "tor_4f81c2", "member_id": "tm_52e1a9", "member": "Sam Rivera", "type": "Holiday", "start_date": "2026-11-02", "end_date": "2026-11-04", "days": 3, "status": "pending" }, { "request_id": "tor_c3b5e8", "member_id": "tm_9b04f7", "member": "Leo Fischer", "type": "Holiday", "start_date": "2026-11-09", "end_date": "2026-11-09", "days": 1, "status": "pending" }, { "request_id": "tor_9a07d1", "member_id": "tm_18c6d3", "member": "Priya Nair", "type": "Holiday", "start_date": "2026-11-16", "end_date": "2026-11-20", "days": 5, "status": "pending" } ] } ``` ### get_time_off_allowance Allowance, days used, pending and remaining for one person and leave year, with adjustments. Access: read. REST: `GET /api/v1/charliehr/members/{member_id}/time-off-allowance`. MCP: `charliehr_read → get_time_off_allowance`. | Parameter | Type | Required | Description | |---|---|---|---| | `member_id` | string | yes | Id from list_team_members | | `leave_year` | string | no | Leave year as shown in Charlie, for example 2026; defaults to the current one | Returns the numbers shown under the person's holiday allowance on the Time tab, for the current leave year or the one you name. Hourly workers get hours instead of days. Adjustments list their type, amount, note and expiry date. Remaining is allowance minus used minus pending. Example response: ```json { "member_id": "tm_52e1a9", "name": "Sam Rivera", "leave_year": "2026", "unit": "days", "allowance": 25, "used": 5, "pending": 3, "remaining": 17, "adjustments": [ { "adjustment_id": "adj_20c8", "direction": "increase", "amount": 1, "type": "Length of service", "expires_on": null, "notes": "Third year" } ] } ``` ### get_whos_working Who is working where and who is off, for one day. Access: read. REST: `GET /api/v1/charliehr/whos-working`. MCP: `charliehr_read → get_whos_working`. | Parameter | Type | Required | Description | |---|---|---|---| | `date` | string | no | YYYY-MM-DD; defaults to today | Returns what the Who's Working page shows for a date: people by working location, and people on holiday or sick leave. Only people with a start date in the past who are not archived appear. Visible to every user of the account, so any role can call it. Defaults to today. Example response: ```json { "date": "2026-11-18", "working": [ { "location": "Office", "people": [ "Leo Fischer", "Maya Cole" ] }, { "location": "Home", "people": [ "Ana Lopez" ] } ], "off": [ { "name": "Priya Nair", "reason": "Holiday" }, { "name": "Sam Rivera", "reason": "Sick" } ] } ``` ### approve_time_off_request Approve one pending time off request, with an optional message to the person. Access: write, asks the user first. REST: `POST /api/v1/charliehr/requests/{request_id}/time-off-request/approve`. MCP: `charliehr_write → approve_time_off_request`. | Parameter | Type | Required | Description | |---|---|---|---| | `request_id` | string | yes | Id from list_time_off_requests | | `note` | string | no | Message to the team member | Does what Approve and Submit Decision do on the Home page. Open to Super Admins, Admins, Team Leads, Line Managers (direct reports only) and custom approvers. Payroll Admins and members get APP_PERMISSION_DENIED. The message goes to the team member. A request that is no longer pending returns an error. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "request_id": "tor_4f81c2", "member": "Sam Rivera", "type": "Holiday", "start_date": "2026-11-02", "end_date": "2026-11-04", "days": 3, "status": "approved", "note_sent": "Enjoy the break.", "remaining_days": 17 } ``` ### deny_time_off_request Deny one pending time off request, with a message to the person. Access: write, asks the user first. REST: `POST /api/v1/charliehr/requests/{request_id}/time-off-request/deny`. MCP: `charliehr_write → deny_time_off_request`. | Parameter | Type | Required | Description | |---|---|---|---| | `request_id` | string | yes | Id from list_time_off_requests | | `note` | string | no | Message to the team member | Does what Deny does in the approval panel. Same roles as approve_time_off_request. The message goes to the team member, so say why. A denied request frees the days again. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "request_id": "tor_9a07d1", "member": "Priya Nair", "type": "Holiday", "start_date": "2026-11-16", "end_date": "2026-11-20", "days": 5, "status": "denied", "note_sent": "Two people are already off that week. Could you move it by a week?" } ``` ### book_time_off Book time off on behalf of a team member; it is approved at once. Access: write, asks the user first. REST: `POST /api/v1/charliehr/members/{member_id}/time-offs`. MCP: `charliehr_write → book_time_off`. | Parameter | Type | Required | Description | |---|---|---|---| | `member_id` | string | yes | Id from list_team_members | | `type` | string | yes | Time off type name as shown in Charlie | | `start_date` | string | yes | YYYY-MM-DD | | `end_date` | string | yes | YYYY-MM-DD | | `notes` | string | no | Note on the booking | Does what "book time off" on the person's Time tab does when you book on behalf. Open to Team Leads, Line Managers, Admins and Super Admins. The booking skips approval and is approved automatically. type is a time off type of your account, for example Holiday. Returns the days used and the days left. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "booking_id": "tob_71d3f0", "member": "Leo Fischer", "type": "Holiday", "start_date": "2026-12-24", "end_date": "2026-12-24", "days": 1, "status": "approved", "remaining_days": 14 } ``` ### record_sick_day Record sick leave for a team member; it is approved at once. Access: write, asks the user first. REST: `POST /api/v1/charliehr/members/{member_id}/sick-days`. MCP: `charliehr_write → record_sick_day`. | Parameter | Type | Required | Description | |---|---|---|---| | `member_id` | string | yes | Id from list_team_members | | `start_date` | string | yes | YYYY-MM-DD | | `end_date` | string | yes | YYYY-MM-DD | Does what recording a sick day on behalf of a team member does. Open to the line manager, team lead, Admins and Super Admins. The sick leave is approved automatically and the line manager or team lead is notified. Past sick days can be recorded the same way. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "booking_id": "tob_5e2a96", "member": "Sam Rivera", "type": "Sick", "start_date": "2026-11-18", "end_date": "2026-11-19", "days": 2, "status": "approved", "manager_notified": true } ``` ### adjust_time_off_allowance Add or remove days on one person's allowance, with a type, an expiry date and a note. Access: write, asks the user first. REST: `POST /api/v1/charliehr/members/{member_id}/time-off-allowance/adjust`. MCP: `charliehr_write → adjust_time_off_allowance`. | Parameter | Type | Required | Description | |---|---|---|---| | `member_id` | string | yes | Id from list_team_members | | `direction` | string | yes | increase or decrease | | `amount` | number | yes | Days, or hours for hourly workers | | `adjustment_type` | string | yes | Type of Adjustment as listed in the form | | `expires_on` | string | no | YYYY-MM-DD, increases only | | `time_off_type` | string | no | Change the allowance of one time off type only | | `notes` | string | no | Note shown with the adjustment | Does what Edit Allowance > Adjust does on the Time tab. Open to Super Admins, Admins, Line Managers and Team Leads. amount is in days, or in hours for hourly workers. expires_on applies to increases only and cannot reach into the next leave year. Booked leave uses the adjustment with the soonest expiry first. Returns the new allowance. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "adjustment_id": "adj_3b71", "member": "Ana Lopez", "direction": "increase", "amount": 2, "adjustment_type": "Extra days", "expires_on": "2026-12-31", "notes": "October release weekend", "allowance_before": 25, "allowance_after": 27, "unit": "days" } ``` ### cancel_time_off_booking Cancel one upcoming or past time off booking. Access: write, asks the user first. REST: `POST /api/v1/charliehr/bookings/{booking_id}/time-off-booking/cancel`. MCP: `charliehr_write → cancel_time_off_booking`. | Parameter | Type | Required | Description | |---|---|---|---| | `booking_id` | string | yes | Id from list_time_off_requests | | `notes` | string | no | Reason shown to the approver | Does what the bin icon does on the Time tab. Upcoming bookings can be cancelled by their owner or an approver, and the approvers are notified. Past bookings need a line manager, team lead or Admin. Cancelling past sick leave always needs approval. Where Cancellation Requests are on, a cancellation can wait for the approver. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "booking_id": "tob_71d3f0", "member": "Leo Fischer", "type": "Holiday", "start_date": "2026-12-24", "end_date": "2026-12-24", "status": "cancelled", "approvers_notified": true } ``` ### offboard_team_member Offboard a person with a leaving date and a reason; the profile is archived. Access: write, asks the user first. REST: `POST /api/v1/charliehr/members/{member_id}/team-member/offboard`. MCP: `charliehr_write → offboard_team_member`. | Parameter | Type | Required | Description | |---|---|---|---| | `member_id` | string | yes | Id from list_team_members | | `leaving_date` | string | yes | YYYY-MM-DD | | `reason` | string | yes | Resignation, Termination, Contract Finished or Other | | `notes` | string | no | Internal notes | Does what "offboard team member" does in the profile settings. Open to Super Admins, Admins and Team Leads. reason is one of the four Charlie lists. The profile is archived, not deleted; the person cannot log in after the leaving date and no longer counts toward future invoices. The person gets no message. Returns the pro-rated allowance. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "member_id": "tm_7d20ab", "name": "Daniel Kim", "status": "archived", "leaving_date": "2026-11-30", "reason": "Resignation", "new_total_allowance": 23, "allowance_used": 17, "remaining": 6, "unit": "days", "member_notified": false } ``` ## How do I connect CharlieHR to Claude Code, Codex or Cursor? Connecting CharlieHR takes three steps: sign up, sign in to CharlieHR once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key. ### Connect CharlieHR to your agent. 1. **Create an account** Sign up and add CharlieHR in the console. Your API key is there too. 2. **Sign in to CharlieHR in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to CharlieHR there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off. 3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once. 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" ``` 4. **Ask your agent** Ask in plain words. Your agent finds the CharlieHR tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool. ``` Go through pending time off requests in CharlieHR. Approve holiday that fits the person's remaining allowance and leaves at least two people working each day, deny nothing, and list the rest for me with a one-line reason. ``` ### Call CharlieHR from your scripts. 1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code. ``` export COTLET_API_KEY="cotlet_..." ``` 2. **Call a tool** Every tool is an endpoint under /api/v1/charliehr with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise. ``` curl -X POST https://cotlet.dev/api/v1/charliehr/requests/tor_4f81c2/time-off-request/approve \ -H "Authorization: Bearer $COTLET_API_KEY" \ -H "Content-Type: application/json" \ -d '{"note":"Enjoy the break."}' ``` 3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing. ``` { "request_id": "tor_4f81c2", "member": "Sam Rivera", "type": "Holiday", "start_date": "2026-11-02", "end_date": "2026-11-04", "days": 3, "status": "approved", "note_sent": "Enjoy the break.", "remaining_days": 17 } ``` ## Why use Cotlet for CharlieHR? **Built for agents** - One MCP server for every app you connect. - The same tools as a REST API for scripts and cron jobs. - Works with Claude Code, Codex and Cursor. **Your login stays yours** - You sign in to CharlieHR yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses. - A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory. - The model never sees a login. - No stored passwords, no CAPTCHA solving, no MFA bypass. **You stay in control** - Scope each API key: its apps, its tools, read only or read and write. - Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you. - Every background request listed in your Background activity. Disable for agents in one click. **Kept working for you** - We test every integration every 6 hours. - When CharlieHR changes, the tool pauses until we fix it. - Failed calls cost nothing. ## Is it safe to connect CharlieHR to Cotlet? Yes. You sign in to CharlieHR yourself, in your own Cloud Browser, and we never save your password. Your agents only get CharlieHR once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself. - **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev) - **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on) - **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev) - **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev) [How Cotlet protects your access](https://cotlet.dev/security.md) ### Common concerns **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 this an official CharlieHR integration?** No, Cotlet is independent of CharlieHR. CharlieHR's own API is too limited for this work. Cotlet works through your own CharlieHR account, the way you use CharlieHR in the browser, so you need no partner approval and no developer setup. **What about client data and GDPR?** Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it. **Can I start with read only?** Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool. **Is it reliable?** Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev. **How do I stop?** Press Disable for agents next to CharlieHR in your console: your agents lose access at once and you stay signed in. Signing out of CharlieHR in the browser works too, and Reset browser deletes the whole profile. ## Is there a CharlieHR MCP server on GitHub? No official MCP server exists. The realistic option is a script on the CharlieHR API, which a Super Admin enables and which reads team members and leave. You write, host and fix the script yourself, and it cannot approve, book, adjust or offboard. Cotlet hosts a server that does those jobs in the CharlieHR screens and maintains it for you. | | API script | Cotlet | |---|---|---| | Setup | A Super Admin creates API keys; you write and host the script | Sign up, sign in to CharlieHR once, add one MCP server or API key | | What it can do | Read team members, leave, offices and teams | Also approve and deny leave, book time off, adjust allowances, offboard | | When CharlieHR changes | You update the script | Our team tests it daily and fixes it for you; failed calls are free | | Your credentials | Client ID and Client Secret that you store yourself; CharlieHR shows them once | Your session lives in your own Cloud Browser in the EU, encrypted; no password stored, disabled for agents in one click | | Upkeep | You host, monitor and debug it yourself | Nothing to host or update | | Where it runs | Wherever you host the script | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule | | Price | Free, paid for with your time | Free 7-day trial, then pay-as-you-go credit packs, no subscription | ### Which one fits you **Pick Cotlet if** - you are not a developer, or you do not want to maintain a server - you need it to keep working when CharlieHR changes, without checking it yourself - your agent or a script should run it on a schedule, also while your computer is off **Pick an open-source server if** - you are comfortable installing, updating and fixing it yourself - you want your sign-in to stay on your own computer - you only need it now and then, from one MCP client ## How much does the CharlieHR API cost? Free 7-day trial with 2,000 credits, no card needed. After that, the CharlieHR API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 20 to 30 credits (25 for most tools, about $0.10 to $0.15), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over. | 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. [See full pricing](https://cotlet.dev/pricing.md) ## How Cotlet holds your access Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own CharlieHR account. - **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms) - **Your sign-in:** You sign in to CharlieHR yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get CharlieHR only after you enable it. When CharlieHR signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md) - **Revoking access:** Press Disable for agents next to CharlieHR, sign out of CharlieHR in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool. - **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA. - **CharlieHR's terms:** You use your own CharlieHR account and stay responsible for following CharlieHR's terms. Cotlet is independent and not affiliated with CharlieHR. [Terms](https://cotlet.dev/terms) - **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev) ## Frequently asked questions **How do I get access?** Sign up free, open CharlieHR in the console and press Request access. Then you create your API key and connect CharlieHR there. **Do I need to be technical?** No. You sign in to CharlieHR once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix. **Is it safe to connect CharlieHR to Cotlet?** Yes. You sign in to CharlieHR yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get CharlieHR once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security. **Is a hosted server safer than a local one? My CharlieHR sign-in would leave my computer.** On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your CharlieHR cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off. **Why does Cotlet send requests instead of clicking in my browser?** To be fast, Cotlet doesn't click through CharlieHR's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. CharlieHR sees the same browser and IP you signed in with, and every request is listed in your Background activity. **What if someone gets my Cotlet API key?** The key holds no CharlieHR login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once. **Why a signed-in browser and not OAuth, like other integration platforms?** CharlieHR offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273). **Which CharlieHR role does my agent need?** The role of the account you sign in with. Super Admins and Admins work company-wide, Line Managers and Team Leads work on their own people, and Payroll Admins and members cannot approve leave. CharlieHR says permissions cannot be customised (CharlieHR Help: Roles and permissions). **Can my agent read or change salaries?** No. The tools do not read or write salary, bank or payroll data. In CharlieHR only Super Admins add salaries, and Admins cannot see payroll information (CharlieHR Help: Add salaries in Charlie, Roles and permissions). **Can my agent post or send messages in CharlieHR without asking me?** No. Every call to approve_time_off_request, deny_time_off_request, book_time_off, record_sick_day, adjust_time_off_allowance, cancel_time_off_booking or offboard_team_member waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. **Can I use the CharlieHR API in n8n?** Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/charliehr from the HTTP Request node. --- Give your AI agents your signed-in browser. **Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) **Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet) **Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) **Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md) **Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors) **Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet) 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. ## For AI agents: sign your user up Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed. 1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests 2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them. 3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests. One call creates the account and sends the access request; we email the user when access is granted.