Home · Setup · Claude Code

MCP Leave Tracker in Claude Code

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.

`claude mcp add leave` at user scope is the level that matches the data: one store per machine is exactly one team's leave book, and the cap arithmetic counts pending requests as plans, so asking twice is free. There is no network call in the server, so it works identically offline.

What you get in Claude Code

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.

Install it in Claude Code

The file is .mcp.json, and the key inside it is mcpServers.

Scope	Path
local (default)	`~/.claude.json, this project only`
project	`.mcp.json at the repository root`
user	`~/.claude.json, every project`

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. Claude Code reads its own config, so here it is:

From the terminal, against a built file:

claude mcp add --scope user leave -- node /absolute/path/to/mcp-servers/servers/leave/dist/index.js
claude mcp list    # health-check it before the first prompt

# or --scope project, committed to .mcp.json for the team

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/leave

That 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:

claude mcp add leave -- npx -y @theluckystrike/mcp-leave

No restart. The entry is picked up in the next session, and `/mcp` reconnects one on demand.

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.

No install: the hosted endpoint

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.

claude mcp add --transport http leave https://mcp.zovo.one/mcp/leave \
  --header "Authorization: Bearer <token>"

Claude Code notes worth knowing first

The `--` is load-bearing: it separates Claude Code's own options, such as --transport, --env and --scope, from the command that runs the server. And the default scope is local, private to you and to the directory you ran it in, so adding it in the wrong folder leaves the tools absent with no error at all.

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.

Questions

Which scope should I use for MCP Leave Tracker?

Local, the default, writes ~/.claude.json and is private to you and that directory. --scope project writes .mcp.json at the repository root, shared through version control. --scope user loads it everywhere.

Why did my first prompt ignore the server?

Measured, not documented: of three fresh projects, one first prompt made zero tool calls although initialize answered in 1.05 seconds. Run claude mcp list once first: it prints Connected, and the next run used the tool.

Can I use MCP Leave Tracker without installing anything?

Yes: claude mcp add --transport http leave https://mcp.zovo.one/mcp/leave --header "Authorization: Bearer <token>". Mint a free token at https://mcp.zovo.one/mcp/token or use a Pro key. -t and -H are the short forms.

MCP Leave Tracker in detail · The same server in Claude Desktop and Cursor · Every server in Claude Code · Guides · Claude Code docs · Buy Pro