Staff leave and PTO: requests, approvals, balances, who is out and a calendar export. You add employees with an annual allowance and carried-over days, then requests arrive as vacation, sick, unpaid or parental, full day or half day, inclusive dates. Approve or reject with a reason, re-open a rejected one by approving it, and cancel via leave_reject with a reason. leave_balance is derived on the call (allowance plus carry-over minus approved and pending, rounded down to whole days plus a half day), leave_out_range answers who is out for coverage and calendars with pending counted as a plan, and the import and ICS export move the ledger in and out. EMP and LV numbers are sequential and never reissued.
leave_balance, leave_out_range, leave_list_requests and leave_list_employees are free, unlimited and write nothing, so leave them enabled permanently. leave_request and leave_approve are the deliberate ones: balance is derived on the call, so approving is what actually spends the days, and the server refuses a request that exceeds the allowance rather than warning.
| You say | Tool |
|---|---|
| Add Taylor Wren, 25 days a year, 2 carried over from last year. | leave_employee_add |
| Taylor wants next Tuesday to Wednesday off, vacation. | leave_request |
| Who is out the week of the 12th, and can I get Taylor's balance? | leave_out_range then leave_balance |
The unit suite is 21 tests, 21 passing, 0 failing (node --test, node v22), covering the balance arithmetic, half days, the re-open path and the out-range deduplication, with adversarial, concurrency, paths and contract suites alongside it.
The file is .cursor/mcp.json, and the key inside it is mcpServers.
| Scope | Path |
|---|---|
| This project only | <project>/.cursor/mcp.json |
| Every project | ~/.cursor/mcp.json |
If you also run Claude Desktop, the shortest path there is one click: leave.mcpb
from the latest release opens as an extension, with no JSON and no terminal.
Cursor reads its own config, so here it is:
The config block:
{
"mcpServers": {
"leave": {
"type": "stdio",
"command": "node",
"args": ["/absolute/path/to/mcp-servers/servers/leave/dist/index.js"]
}
}
}The node command above wants a built file. From a clone, once:
git clone https://github.com/theluckystrike/mcp-servers.git
cd mcp-servers && npm install
npm run build -w packages/mcp-license -w servers/leaveThat writes servers/leave/dist/index.js, and its absolute path is the one argument
the config needs.
The npm packages are not published yet, so the form below returns a 404 today. It is here because it is what the entry becomes the day the publish lands, with nothing else changed:
{
"mcpServers": {
"leave": {
"command": "npx",
"args": ["-y", "@theluckystrike/mcp-leave"]
}
}
}The Customize page shows the server and its tools once it has started.
Nothing is published to npm yet, so the working install paths are the ones above: the .mcpb bundle from the latest release, a clone and build, or the hosted URL.
The same server runs at https://mcp.zovo.one/mcp/leave over MCP streamable HTTP, no install. Mint a free token with curl https://mcp.zovo.one/mcp/token, or use a Pro key. It has no filesystem, so a file comes back as a one-hour download link.
{
"mcpServers": {
"leave": {
"url": "https://mcp.zovo.one/mcp/leave",
"headers": { "Authorization": "Bearer <token>" }
}
}
}The current field table marks `type` as required, with `stdio` for a locally launched server, so write it out rather than relying on command and args alone. The other documented restriction is that `envFile` is stdio-only: a remote HTTP or SSE server does not read it, and its headers belong in the config.
Free: Employees, requests, approvals, rejections, balances, the out-range view and the lists are free and unlimited; nothing a manager decides in a morning sits behind a paywall. Reads are free on every tier. Pro is $19 once, verified offline.
<project>/.cursor/mcp.json applies to that project and can be committed, which suits a server tied to one client. ~/.cursor/mcp.json applies everywhere. Both are managed from the Customize page.
The current field table marks type as required, with stdio for a locally launched server, so include it. Pointing at a remote endpoint, envFile is documented as stdio-only and is not read.
Servers in Cursor's marketplace get an Add to Cursor button. The deeplink reference currently documents prompt, command and rule links only, so for MCP Leave Tracker pasting the config block above is the supported route.
MCP Leave Tracker in detail · The same server in Claude Code and VS Code · Every server in Cursor · Guides · Cursor docs · Buy Pro