Skip to main content
Glama
Employee Leave Management MCP Server

Employee Leave Management MCP Server

by Sushmitha26

Employee Leave Management MCP Server

A FastMCP server that lets Claude Desktop manage employee leave through natural language. Uses an in-memory data model seeded with sample employees, so it runs with no external database.

Features

Tools: apply_for_leave, approve_leave, reject_leave, cancel_leave, list_pending_requests, check_leave_balance

Resources: employee://{id}/balance, employee://{id}/requests, policy://leave

Prompts: draft_leave_request, draft_decision

Leave is counted in working days (Mon–Fri). Balances deduct on approval and are credited back on cancellation.

Related MCP server: MCP Leave Manager Server

Setup

Requires Python 3.10+ and uv.

uv add "mcp[cli]"

Run

uv run main.py               # run the server
uv run mcp install main.py   # register with Claude Desktop

After installing, fully restart Claude Desktop. The server appears under Settings → Developer → Local MCP servers.

Example prompts

  • "What's the leave balance for employee E001?"

  • "Apply for annual leave for E001 from 2026-08-03 to 2026-08-07, reason vacation."

  • "Show pending leave requests for manager M001."

  • "Approve request 1 as M001."

  • "Apply for 30 days of annual leave for E001"

Available Tools

6 tools
apply_for_leaveA

Submit a leave request for an employee.

Dates use ISO format (YYYY-MM-DD). The number of working days is computed automatically and checked against the remaining balance. Returns the created request as a dictionary.

Inputs: end_date (required), leave_type (required), start_date (required), employee_id (required), +1 more.

approve_leaveC

Approve a pending leave request and deduct the days from the balance.

Inputs: request_id (required), approver_id (required), note.

cancel_leaveA

Cancel a leave request. If it was already approved, the days are credited back to the employee's balance.

Inputs: request_id (required).

check_leave_balanceA

Return the remaining balance for each leave type for an employee.

Inputs: employee_id (required).

list_pending_requestsB

List all pending leave requests for employees reporting to a manager.

Inputs: manager_id (required).

reject_leaveB

Reject a pending leave request. The balance is left unchanged.

Inputs: request_id (required), approver_id (required), note.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool targets a distinct lifecycle action (apply, approve, reject, cancel, list, check) with no obvious overlaps. The only minor potential confusion is between approve/reject/cancel, all acting on pending requests, but their differing effects on balance make them clearly distinct.

    Naming Consistency5/5

    All tools follow a consistent verb_noun naming pattern (apply_for_leave, approve_leave, reject_leave, cancel_leave, list_pending_requests, check_leave_balance). The verbs are clear and uniform, with snake_case throughout.

    Tool Count5/5

    Six tools is well-scoped for a leave management domain, covering the full request lifecycle plus balance and listing queries. No tool feels redundant or unnecessary, and none are missing within the core scope.

    Completeness4/5

    The surface covers the full request lifecycle (apply, approve, reject, cancel) plus balance checking and pending listing. Minor gaps exist—such as no update_leave for modifying a request or a get_leave for viewing individual approved requests—but core workflows are covered.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers