io.github.theluckystrike/leave

Official12 toolsLive

by theluckystrike · JavaScript

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

MCP Server: io.github.theluckystrike/leave

The MCP server io.github.theluckystrike/leave manages employee leave and PTO requests, including balances, approvals, calendars, and who-is-out summaries. It is focused on tracking leave status and related decision workflows through the server’s available operations.

🛠️ Key Features

Employee leave and PTO requests
Leave/PTO balances
Approvals
Calendars
Who-is-out summaries

🚀 Use Cases

Requesting and reviewing employee leave or PTO
Checking remaining leave/PTO balances
Viewing leave on calendars
Generating summaries of staff availability (“who is out”)

⚡ Developer Benefits

Structured access to leave/PTO data covering balances, approvals, calendars, and availability summaries

⚠️ Limitations

Available details do not specify supported data formats, authentication, deployment method, or API/tool counts.

Topics

claudecursorinvoicemcpmcp-servermodel-context-protocolspreadsheetaccountingai-toolsbookkeepingclaude-desktopfreelanceinvoicinglocal-firstmcp-serverspdfself-hostedtime-trackingvatproductivity

Captured live from the server via tools/list.

leave_employee_add

Add an employee to the leave tracker and return their EMP-NNNN id. Give their annual paid-leave allowance in whole days and any days carried over from last year. Balances charge approved plus pending leave against allowance + carried-over. Free tier: unlimited.

Parameters4

name	string	required	Full name, e.g. Taylor Wren
annualAllowance	integer	required	Annual paid leave allowance in whole days
carriedOver	integer	optional	Days carried over from last year (default 0)
email	string	optional	Work email, for calendar lookup

Raw schema

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "maxLength": 200,
      "description": "Full name, e.g. Taylor Wren"
    },
    "annualAllowance": {
      "type": "integer",
      "minimum": 0,
      "maximum": 1000,
      "description": "Annual paid leave allowance in whole days"
    },
    "carriedOver": {
      "type": "integer",
      "minimum": 0,
      "maximum": 1000,
      "description": "Days carried over from last year (default 0)"
    },
    "email": {
      "type": "string",
      "maxLength": 200,
      "description": "Work email, for calendar lookup"
    }
  },
  "required": [
    "name",
    "annualAllowance"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

leave_request

Create a leave or PTO request and return its LV-NNNN id. type is vacation, sick, unpaid or parental. start and end are inclusive YYYY-MM-DD dates; halfDay charges half a day for the whole span. A pending request is refussed if it would overlap another approved or pending request of the same employee. Free tier: unlimited requests.

Parameters6

employee	string	required	The employee id or name
type	string	required	Kind of leave
start	string	required	First day off, YYYY-MM-DD, inclusive
end	string	required	Last day off, YYYY-MM-DD, inclusive
halfDay	boolean	optional	Half-day charge for the whole span (default false)
reason	string	optional	Why, shown in reports and calendar

Raw schema

{
  "type": "object",
  "properties": {
    "employee": {
      "type": "string",
      "maxLength": 200,
      "description": "The employee id or name"
    },
    "type": {
      "type": "string",
      "enum": [
        "vacation",
        "sick",
        "unpaid",
        "parental"
      ],
      "description": "Kind of leave"
    },
    "start": {
      "type": "string",
      "maxLength": 32,
      "description": "First day off, YYYY-MM-DD, inclusive"
    },
    "end": {
      "type": "string",
      "maxLength": 32,
      "description": "Last day off, YYYY-MM-DD, inclusive"
    },
    "halfDay": {
      "type": "boolean",
      "description": "Half-day charge for the whole span (default false)"
    },
    "reason": {
      "type": "string",
      "maxLength": 2000,
      "description": "Why, shown in reports and calendar"
    }
  },
  "required": [
    "employee",
    "type",
    "start",
    "end"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

leave_approve

Approve a pending leave request by id. Also used to re-open a rejected one. Nothing to approve on an already-approved request.

Parameters2

request	string	required	The request id (e.g. LV-0001).
comment	string	optional	Approval note

Raw schema

{
  "type": "object",
  "properties": {
    "request": {
      "type": "string",
      "maxLength": 200,
      "description": "The request id (e.g. LV-0001)."
    },
    "comment": {
      "type": "string",
      "maxLength": 2000,
      "description": "Approval note"
    }
  },
  "required": [
    "request"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

leave_reject

Reject or cancel a leave request by id. A pending or approved request becomes rejected; a rejected one can be reopened via leave_approve. Use leave_cancel (via reject with reason) for voluntary withdrawal.

Parameters2

request	string	required	The request id (e.g. LV-0001).
reason	string	optional	Why

Raw schema

{
  "type": "object",
  "properties": {
    "request": {
      "type": "string",
      "maxLength": 200,
      "description": "The request id (e.g. LV-0001)."
    },
    "reason": {
      "type": "string",
      "maxLength": 2000,
      "description": "Why"
    }
  },
  "required": [
    "request"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

leave_balance

Show one employee's leave balance: allowance + carried-over, minus approved and pending, as whole days plus a possible half day. Remaining is rounded down to whole days on the report.

Parameters1

employee

string

required

Employee id or name

Raw schema

{
  "type": "object",
  "properties": {
    "employee": {
      "type": "string",
      "maxLength": 200,
      "description": "Employee id or name"
    }
  },
  "required": [
    "employee"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

leave_out_range

Who is out in a date range: start and end are inclusive YYYY-MM-DD. Each employee appears once per day; pending requests count as a plan. Use for coverage, calendars and absence summaries. Free tier: unlimited.

Parameters2

start	string	required	First day, YYYY-MM-DD, inclusive
end	string	required	Last day, YYYY-MM-DD, inclusive

Raw schema

{
  "type": "object",
  "properties": {
    "start": {
      "type": "string",
      "maxLength": 32,
      "description": "First day, YYYY-MM-DD, inclusive"
    },
    "end": {
      "type": "string",
      "maxLength": 32,
      "description": "Last day, YYYY-MM-DD, inclusive"
    }
  },
  "required": [
    "start",
    "end"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

leave_list

List all employees, or all leave requests (optionally filtered by employee and/or status). Omit the filter to list requests.

Parameters2

employee	string	optional	Filter requests to one employee
status	string	optional	Filter requests by status

Raw schema

{
  "type": "object",
  "properties": {
    "employee": {
      "type": "string",
      "maxLength": 200,
      "description": "Filter requests to one employee"
    },
    "status": {
      "type": "string",
      "enum": [
        "pending",
        "approved",
        "rejected",
        "cancelled"
      ],
      "description": "Filter requests by status"
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

leave_import

Pro. Bulk-create leave requests from a CSV/TSV. First row is a header: employee,type,start,end,halfDay,status,reason. status may be omitted (defaults to pending) or be approved/rejected. Each request is still checked for overlap conflicts; a conflicting row is reported, not applied. watermark-free, full CRUD.

Parameters1

csv

string

required

CSV text, newline-separated, first row header: employee,type,start,end,halfDay,status,reason

Raw schema

{
  "type": "object",
  "properties": {
    "csv": {
      "type": "string",
      "maxLength": 200000,
      "description": "CSV text, newline-separated, first row header: employee,type,start,end,halfDay,status,reason"
    }
  },
  "required": [
    "csv"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

leave_export_ics

Pro. Export all APPROVED leave as an .ics calendar (RFC5545). Returns the calendar text; pass path to also write it to a local file. watermark-free.

Parameters1

path

string

optional

Local .ics file to write

Raw schema

{
  "type": "object",
  "properties": {
    "path": {
      "type": "string",
      "maxLength": 500,
      "description": "Local .ics file to write"
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

license_status

Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.

Parameters

No parameters.

Raw schema

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}

license_activate

Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.

Parameters1

key

string

required

License key from checkout, MCPL1.<payload>.<signature>

Raw schema

{
  "type": "object",
  "properties": {
    "key": {
      "type": "string",
      "description": "License key from checkout, MCPL1.<payload>.<signature>"
    }
  },
  "required": [
    "key"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

leave_cancel

Cancel a pending or approved request by id, keeping its record with status cancelled. Differs from leave_reject in intent (voluntary withdrawal). Nothing happened if already cancelled.

Parameters2

request	string	required	The request id (e.g. LV-0001).
reason	string	optional	Why

Raw schema

{
  "type": "object",
  "properties": {
    "request": {
      "type": "string",
      "maxLength": 200,
      "description": "The request id (e.g. LV-0001)."
    },
    "reason": {
      "type": "string",
      "maxLength": 2000,
      "description": "Why"
    }
  },
  "required": [
    "request"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

servers/leave/README.md3 KBView on GitHub

mcp-leave

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:

Docs MCP URL: https://gitmcp.io/theluckystrike/mcp-leave

Install

Tools (12)

leave_employee_addleave_requestleave_approveleave_rejectleave_balanceleave_out_rangeleave_listleave_import

Remote endpoint

Streamable HTTP

Hosted server - connect over the network, no local install.

url

https://mcp.zovo.one/mcp/leave

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "leave": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.zovo.one/mcp/leave"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.

MCP Server: io.github.theluckystrike/leave

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

leave_employee_add

leave_request

leave_approve

leave_reject

leave_balance

leave_out_range

leave_list

leave_import

leave_export_ics

license_status

license_activate

leave_cancel

mcp-leave

Tools

The one rule that decides everything else

Free vs Pro

Quick start

Use these docs as an MCP server

Install

Remote endpoint

Related servers