CharlieHR MCP Server
छुट्टी मंज़ूर करें, अवकाश बुक करें, भत्तों में बदलाव करें और लोगों को ऑफबोर्ड करें।
होस्ट किया गया MCP सर्वर
npx add-mcp 'https://cotlet.dev/mcp/v1/charliehr'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
CharlieHR API and MCP server: Let your AI agent clear the time off queue in Charlie.
CharlieHR has a public API and no official MCP server (checked 27 Oct 2026). Its 30 documented operations read people, leave, allowances, salaries and offices; the only writes add notes. Cotlet runs 12 CharlieHR tools hosted, 7 of them leave writes, over MCP for agents and REST for scripts.
Approve leave, book time off, adjust allowances and offboard people. 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 CharlieHR
- Page: https://cotlet.dev/integrations/charliehr-api-mcp-server
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by CharlieHR. CharlieHR is a trademark of its owner. If CharlieHR's own integrations cover what you need, use them first.
What can you automate in CharlieHR?
- Approve holiday that fits balance and cover
- List who is off or at home this week
- Record sick days from a message
- Add or remove allowance days for a team
- Book leave on someone's behalf
- Offboard a leaver with the pro-rated holiday
Does CharlieHR have an MCP server or an API?
- A Super Admin creates the API keys under Company > Integrations > API Keys. The newer V3 keys offer "read and write", but CharlieHR says "for now, all integrations will be read only" (help center, 27 Oct 2026).
- Nothing official approves, denies, books or cancels leave, adjusts an allowance or offboards someone. There is no Zapier app, and the Slack app only posts notifications.
- StackOne sells a hosted CharlieHR MCP with 22 actions on the same API, so it reads and adds notes. It is built for software companies, not an HR team.
| What you need | CharlieHR API | StackOne MCP | Cotlet |
|---|---|---|---|
| Read people, leave and allowances | Yes | Yes | Yes |
| Approve or deny time off | No | No | Yes, after your OK |
| Book leave, record sick days, cancel | No | No | Yes, after your OK |
| Adjust allowances, offboard | No | No | Yes, after your OK |
| Works for a line manager, not only a Super Admin | Super Admin keys | Super Admin keys | Yes, your own role |
Checked 27 Oct 2026. Sources: CharlieHR Help: Integrate Charlie with selected apps (API Access), CharlieHR Help: Integrating your product with Charlie, CharlieHR API documentation, CharlieHR Help: Roles and permissions, CharlieHR pricing, StackOne CharlieHR connector
How does Cotlet connect to CharlieHR?
- Sign in to CharlieHR. 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 Charlie password, and no leave decision, booking or offboarding goes through until you approve it.
Connect CharlieHR 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.
- Enable CharlieHR for agents. Create a Cotlet account, sign in to Charlie in its Cloud Browser as the admin or manager who approves leave, and press Enable for agents.
- Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 in your agent as a remote MCP server or custom connector.
- Confirm the connection. Chat apps open a Cotlet sign-in once. Editors, n8n and scripts send an API key made in the console.
https://cotlet.dev/mcp/v1 carries CharlieHR next to your other apps. The agent can do what the signed-in role can: an Admin works company-wide, a Line Manager only on direct reports. Charlie prices by headcount band, so sign in as someone already on the account instead of adding a login. Refresh the connector after enabling CharlieHR so the tools load.
Claude:
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet-charliehr \
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-charliehr": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
}
Codex:
# ~/.codex/config.toml
[mcp_servers.cotlet-charliehr]
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: charliehr_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: charliehr_write
How to use the CharlieHR REST API
Create your Cotlet API key
Create a Cotlet API key with access to CharlieHR and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.
Connect CharlieHR in Cotlet and enable it for agents. Account access: Your own CharlieHR account (Super Admin or Admin for company-wide work, Line Manager or Team Lead for your own reports).
Make your first CharlieHR API request
REST:
curl https://cotlet.dev/api/v1/charliehr/team-members \
-H "Authorization: Bearer $COTLET_API_KEY"
Read team members 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": "charliehr",
"tool": "list_team_members",
"result": {
"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"
}
]
}
}
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.
Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.
CharlieHR workflows for agents and automations
| Tool | Connect through | Example workflow |
|---|---|---|
| n8n | HTTP Request | Time off requests with person, type, dates, days and status. Use list_time_off_requests in your configured team report. |
| Make | HTTP > Make a request | Allowance, days used, pending and remaining for one person and leave year, with adjustments. Use get_time_off_allowance in your configured team report. |
| Python or Node.js | REST API | Who is working where and who is off, for one day. Use get_whos_working 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 CharlieHR; 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.
CharlieHR API endpoints and MCP tools
People and who is working
Active or archived profiles with office, team and line manager. Salary and bank details are never returned, though the session of a Super Admin could see them.
- List team members (
list_team_members, read): People in your CharlieHR account with office, team, line manager and start date. - Get a team member (
get_team_member, read): One profile: office, team, line manager, start date, role and working week. - Get who is working (
get_whos_working, read): Who is working where and who is off, for one day.
Time off requests and bookings
What you see depends on the role: everyone for an Admin, direct reports for a Line Manager. Bookings on someone's behalf and sick days skip approval in Charlie, so each call asks you first.
- List time off requests (
list_time_off_requests, read): Time off requests with person, type, dates, days and status. - Approve a time off request (
approve_time_off_request, write, asks first): Approve one pending time off request, with an optional message to the person. - Deny a time off request (
deny_time_off_request, write, asks first): Deny one pending time off request, with a message to the person. - Book time off for someone (
book_time_off, write, asks first): Book time off on behalf of a team member; it is approved at once. - Record a sick day (
record_sick_day, write, asks first): Record sick leave for a team member; it is approved at once. - Cancel a time off booking (
cancel_time_off_booking, write, asks first): Cancel one upcoming or past time off booking.
Allowances
Days, or hours for hourly workers. An expiring adjustment stays inside one leave year.
- Get a time off allowance (
get_time_off_allowance, read): Allowance, days used, pending and remaining for one person and leave year, with adjustments. - Adjust a time off allowance (
adjust_time_off_allowance, write, asks first): Add or remove days on one person's allowance, with a type, an expiry date and a note.
Offboarding
Super Admins, Admins and Team Leads only. The profile is archived, not deleted.
- Offboard a team member (
offboard_team_member, write, asks first): Offboard a person with a leaving date and a reason; the profile is archived.
Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/charliehr-api-mcp-server#tools
Who can see my CharlieHR session, and how do I revoke it?
- What we store. The signed-in Charlie browser profile, AES-256-GCM encrypted, in Finland. No password.
- What your agent gets. The 12 CharlieHR tools. Never the session cookie.
- What the session sees. What your Charlie role sees. For a Super Admin that includes salaries.
- What no tool touches. Salaries, bank details, payroll, documents and reviews.
- Two-factor sign-in. You type the authenticator code yourself. We never pass a 2FA check for you.
- How to cut access. Disable for agents, reset the browser, or archive that login in Charlie.
Charlie holds employee personal data, so check that your privacy notice covers a processor acting in the HR account. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
Approvals, undo and mistakes
- Reads the queue. list_time_off_requests: pending requests your role can approve.
- Checks balance and cover. Remaining days, and who is working on the first and last day.
- Waits for your OK. Each approval shows up in your Cotlet console first.
- Reports back. Approved, and left for you with the date that failed.
| Action | Undo |
|---|---|
| Approve time off | Cancel the booking; the person was already told |
| Deny time off | No, they book again; the message was sent |
| Book time off or a sick day | Cancel it with the bin icon on the Time tab |
| Adjust an allowance | Add the opposite adjustment |
| Offboard a team member | Reactivate the archived profile |
7 of 12 tools ask first: every write, because each one changes a person's leave or access. Reads run at once. Switch the wait off per tool for a scheduled run, for example sick days you already checked.
Sick leave is approved automatically in Charlie, and cancelling past sick leave always needs an approver.
MCP call:
{
"name": "approve_time_off_request",
"arguments": {
"request_id": "tor_4f81c2",
"note": "Enjoy the break."
}
}
REST:
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."}'
Response:
{
"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
}
A script or a morning job calls the same tools over REST at /api/v1/charliehr, one key, one price. A call your Charlie role cannot make, such as a Payroll Admin approving leave, fails with APP_PERMISSION_DENIED and costs nothing. The tools table gives the REST path of each tool.
How much does the CharlieHR MCP server cost?
About $17 a month for a company of about 25 people, 2,860 credits. Your CharlieHR plan is billed as before.
| Job | Calls | Credits |
|---|---|---|
| Read the pending queue, daily | 1 × 30 | 300 |
| Check balance and cover, then approve | 3 × 22 | 660 |
| Monday list of who is off | 6 × 4 | 240 |
| Sick days from team messages | 2 × 4 | 80 |
| Allowance adjustments | 2 × 3 | 60 |
| Offboard a leaver | 2 × 1 | 20 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 2,860 |
- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- One-time packs, valid 12 months, no subscription
CharlieHR handled 800,000+ leave requests last year for 3,000+ companies (charliehr.com/customers, 27 Oct 2026), about 22 a month each, which is the queue in the example. For scale, Charlie for 15 to 29 people is £108 a month before VAT. Dollars at the $29 pack rate.
CharlieHR MCP server: API script, StackOne or hosted
| Option | What it does | Where it stops |
|---|---|---|
| CharlieHR API | 28 reads: team members, leave requests, allowances, adjustments, working locations, salaries. Free on every plan. | Writes only notes. A Super Admin makes the keys, and you host the script. |
| StackOne | Hosted MCP with 22 CharlieHR actions, with prompt injection checks and field-level rules. | The same reads plus notes. Sold to software companies that build agents into their product. |
| Merge, Kombo, Apideck, Truto, Knit | Unified HR APIs that CharlieHR names as partners, on V1 keys. | For vendors syncing many HR systems; leave writes are limited by the CharlieHR API. |
| GitHub | No CharlieHR MCP server found; api-evangelist/charliehr is an API profile with no code (gh, 27 Oct 2026). | Nothing to self-host yet. |
If you want a monthly absence report or a sync to payroll, a script on the CharlieHR API is free and official; use it. When the agent should decide the queue, book leave, fix allowances or offboard, or you are a line manager without Super Admin keys, that is the part Cotlet covers.
Who runs Cotlet
Take Group sp. z o.o. runs Cotlet. It is a software company registered in Poland, EU (VAT PL6342984273), trading since 2019, founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the CharlieHR tools go to contact@cotlet.dev.
CharlieHR API and MCP: questions
How do I get access?
Sign up free at https://cotlet.dev, open CharlieHR under Integrations in the console and sign in to Charlie in its Cloud Browser. The trial starts when you sign up; no card is asked.
How do I connect CharlieHR to ChatGPT or Claude?
Sign up at cotlet.dev, log in to CharlieHR 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 CharlieHR account through Cotlet, in their phone apps too.
What can ChatGPT do in CharlieHR?
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in CharlieHR: approve routine time off requests; offboard a leaver; adjust leave allowances. You ask in plain words, and anything that reaches other people waits for your OK first.
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).
Does CharlieHR have webhooks?
Not in its API docs (27 Oct 2026). The Slack app posts new time off requests and a daily digest to a channel. To act on new requests, run your agent on a schedule, for example one list_time_off_requests pass each morning.
Does it work with two-factor sign-in on?
Yes. You type the authenticator code yourself when you sign in to Charlie in the Cloud Browser. The session then stays signed in; if Charlie asks again, you sign in again.
Is the MCP server different from the REST API?
Only in how you call it. Both carry the same 12 tools, inputs and answers, under one API key and one price. Agents use MCP; scripts and HTTP steps use REST.
Is Cotlet affiliated with CharlieHR?
No. Cotlet is independent and not affiliated with Charlie OS Limited or CharlieHR.
Can I use the CharlieHR 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.