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.
In agent mode the arithmetic must come from the server: leave_balance is allowance plus carry-over minus approved and pending, rounded down to whole days plus a half day, computed on the call, so an agent totaling requests by hand is composing an estimate the server already gives exactly.
| 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 .vscode/mcp.json, and the key inside it is servers.
| Scope | Path |
|---|---|
| This workspace | <workspace>/.vscode/mcp.json |
| Every workspace | the user profile mcp.json, opened by the MCP: Open User Configuration command |
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.
VS Code reads its own config, so here it is:
// .vscode/mcp.json (the key is "servers")
{
"servers": {
"leave": {
"command": "node",
"args": ["/absolute/path/to/mcp-servers/servers/leave/dist/index.js"]
}
}
}Or from a terminal:
code --add-mcp '{"name":"leave","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:
code --add-mcp '{"name":"leave","command":"npx","args":["-y","@theluckystrike/mcp-leave"]}'VS Code asks you to confirm you trust the server and its capabilities before it starts. Nothing runs until you answer.
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.
{
"servers": {
"leave": {
"url": "https://mcp.zovo.one/mcp/leave",
"headers": { "Authorization": "Bearer <token>" }
}
}
}The top-level key is "servers", not "mcpServers". A config pasted from a Claude Desktop or Cursor README parses cleanly, contributes no servers, and gives you no error to read, which makes it the most expensive one-word mistake here. Alongside it an "inputs" array holds secrets. The newer Agent Host reads a workspace .mcp.json instead.
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.
The key is servers, not mcpServers. A config copied from a Claude Desktop README parses cleanly and contributes nothing. Rename it. On the newer Agent Host, use a workspace .mcp.json instead.
No. code --add-mcp takes the server object on the command line, and MCP: Add Server in the palette asks whether the target is Workspace or Global.
In Chat, behind the tools picker, once the server has started. Adding or changing one raises a prompt asking you to confirm you trust it; if the picker is empty, that prompt is usually still waiting.
MCP Leave Tracker in detail · The same server in Cursor and Windsurf · Every server in VS Code · Guides · VS Code docs · Buy Pro