Leave Pto Requests Approvals

io.github.theluckystrikePublished by GitHub account theluckystrikev0.22.6Updated Oct 24, 2026

Employee leave and PTO requests: balances, approvals, calendars, and who-is-out summaries.

VerifiedSTDIODesktop onlyProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Local MCP server for small teams that tracks employee leave and PTO: allowances, requests, approvals, balances and who-is-out calendars.

What you can do
  • Add employees with an annual allowance and optional carried-over days
  • Log vacation, sick or personal leave requests, including half-days, and approve, reject or cancel them
  • Read per-employee balances: allowance, carried, approved, pending, committed and remaining days
  • See who is out over a date range as day-by-day calendar rows and person-days, and list employees and requests by status
  • Pro tier adds bulk CSV import of requests and export of approved leave as an ICS calendar
When to use it
Useful for solopreneurs and small studios that want to record and approve leave from an MCP client such as Claude Desktop or Cursor, without a separate HR system. It suits teams that need quick balance and who-is-out answers during planning.
Requirements
Runs locally as a stdio process, installed from the mcpb package or via npx. Data is stored in a local JSON file under the user's home or XDG data directory. No account or authentication is needed; the optional Pro license key is supplied through the MCP_LICENSE_KEY environment variable and verified offline.
Before you install
The server writes and changes data: adding employees, logging, approving, rejecting and cancelling requests all modify the local store, and cancellations keep an audit trail. Leave records, including reasons, are kept in a plain JSON file on the machine, so protect that file. The Pro license key is a secret and should not be shared.

Installation

In SourceWeft

  1. Open Leave Pto Requests Approvals in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

mcp-leave

[theluckystrike/mcp-leave MCP server]

In the official MCP Registry (io.github.theluckystrike/leave). Employee leave/PTO tracking for solopreneurs and small studios: who is off, when, and how many days each person has left. Add employees with an annual allowance and any carried-over days, log vacation/sick/personal requests (including half-days), approve or reject them, and read balances, conflicts and who-is-out calendars directly from your MCP client - Claude Desktop, Cursor, or any MCP host.

Tools

  • "leave_employee_add" - add an employee with annualAllowance (and optional carriedOver).
  • "leave_request" - log a leave request (employee, type, start, end, optional halfDay, reason).
  • "leave_approve" / "leave_reject" - decide a request; decisions are recorded with dates.
  • "leave_cancel" - cancel a pending or approved request (keeps the audit trail).
  • "leave_balance" - allowance, carried, approved, pending, committed and remaining days per employee.
  • "leave_out_range" - who is out in a date range: day-by-day calendar rows plus person-days.
  • "leave_list" - all employees and requests, filterable by employee and status.
  • "leave_import" (Pro) - bulk-create requests from CSV; conflicting rows are rejected one by one, valid rows still apply.
  • "leave_export_ics" (Pro) - export approved leave as an RFC5545 .ics calendar.

The one rule that decides everything else

A day is committed when the request that spends it is approved or pending. Balance is allowance + carried − approved − pending. Cancelling returns the days immediately; rejecting never charged them.

Overlapping requests for the same person are refused at creation time - both pending and approved count - so the calendar never contains two requests claiming the same day.

Free vs Pro

The free tier is the full CRUD surface: employees, requests, approvals, balances, calendars - watermark-free, no request limits. Pro (an MCP_LICENSE_KEY, activate with "license_activate") adds bulk CSV import and ICS calendar export. Run "license_status" to see the current tier.

Quick start

json
{  "mcpServers": {    "leave": { "command": "npx", "args": ["-y", "@theluckystrike/mcp-leave"] }  }}

Data lives in a single JSON store (~/.mcp-leave/store.json, or $XDG_DATA_HOME/mcp-servers/leave/store.json when set), written atomically under a file lock, so two clients on one machine never interleave writes.

Use these docs as an MCP server

Any MCP client (Claude, Cursor, Windsurf, VS Code) can read this repository's documentation directly via GitMCP - no install:

Source: servers/leave/README.md at commit 55b3f42

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.22.6LatestOct 14, 2026
  2. v0.22.0Sep 23, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts