Skip to main content
Glama
HRMS MCP Server

HRMS MCP Server

HR Management System (MCP Server)

⚠️ Work in progress. This project is still under active development and is not production-ready. The manager functions in HRMS/ are mock implementations that mimic the API calls of Keka HR software, using in-memory sample data instead of real Keka API integration.

An HR assistant exposed as an MCP (Model Context Protocol) server. It lets an MCP-compatible client (e.g. Claude Desktop) manage employees, tickets, leaves, and meetings, and send emails — backed by in-memory data that is seeded with sample employees on startup.

Features

The MCP server (server.py) exposes the following tools and prompt:

Tool

Description

add_employee

Add a new employee to the HRMS.

get_employee_details

Look up an employee's details by name.

create_ticket

Raise a ticket for equipment/items (laptop, ID card, etc.).

update_ticket_status

Update a ticket's status.

list_tickets

List tickets for an employee, optionally filtered by status.

send_email

Send an email via SMTP.

Prompt

Description

onboard_new_employee

Guided workflow to onboard a new hire end-to-end.

Additional domain logic lives in the HRMS/ package (employee, leave, meeting, and ticket managers plus Pydantic schemas.py). These managers currently mock Keka's HR API; sample data is loaded by utils.seed_services on server start.

Related MCP server: OCP AI Custom HR MCP Server

Requirements

  • Python >= 3.12

  • uv (recommended) for dependency management

Setup

  1. Clone the repository:

    git clone <your-repo-url>
    cd HR_Management_System
  2. Install dependencies:

    uv sync
  3. Configure environment variables. Copy the example file and fill in your SMTP credentials:

    cp .env.example .env

    Variable

    Description

    MS_EMAIL

    Sender email address / SMTP login.

    MS_EMAIL_PWD

    SMTP password or app password.

    For Gmail, generate an App Password rather than using your account password.

Running

Start the MCP server (uses stdio transport):

uv run server.py

To use it with an MCP client such as Claude Desktop, add an entry to the client's MCP server configuration pointing at this command, for example:

{
  "mcpServers": {
    "atliq-hr-assist": {
      "command": "uv",
      "args": ["run", "server.py"],
      "cwd": "/absolute/path/to/HR_Management_System"
    }
  }
}

You can also test the email sender directly:

uv run emails.py

Project structure

.
├── server.py          # MCP server entry point (tools & prompts)
├── emails.py          # SMTP email sender
├── utils.py           # Seeds the managers with sample data
├── main.py            # Hello-world placeholder
├── HRMS/              # Core domain package (mocks Keka HR API)
│   ├── employee_manager.py
│   ├── leave_manager.py
│   ├── meeting_manager.py
│   ├── ticket_manager.py
│   └── schemas.py     # Pydantic models
├── .env.example       # Template for required environment variables
└── pyproject.toml

Roadmap / TODO

  • Replace the mock HRMS/ managers with real Keka HR API integration.

  • Persist data instead of using in-memory seeded sample data.

  • Expand MCP tool coverage for leave and meeting management.

Notes

  • Data is stored in memory and re-seeded on every start; it is not persisted.

  • Never commit your .env file — it contains secrets and is git-ignored.

Available Tools

6 tools
add_employeeC
 Add a new employee to the HRMS system.
  :param emp_name: Employee name 
  :param manager_id : Manager ID (optional)
  :return Confirmation message

Inputs: emp_name (required), manager_id (required), email (required). Returns: result

create_ticketA
Create a ticket for buying required items for an employee.
:param emp_id: Employee ID
:param item: Item requested (laptop, ID Card, etc.)
:param reason: Reason for the request
:return : Confirmation message

Inputs: emp_id (required), item (required), reason (required). Returns: result

get_employee_detailsA
Get employee details by name.
:param name: Name of the employee
:return Employee ID and manager ID

Inputs: name (required). Returns: result

list_ticketsC
List tickets for an employee with optional status filter.
:param employee_id : employee_id 
:param status : status
: return : List of tickets

Inputs: employee_id (required), status (required). Returns: result

send_emailD

Inputs: to_emails (required), subject (required), body (required), html. Returns: result

update_ticket_statusB
Update the status of a ticket.
:param ticket_id: Ticket ID
:param status: New status of the ticket
:return: Confirmation message

Inputs: ticket_id (required), status (required). Returns: result

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    C2.8/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools have clear, distinct purposes (employee CRUD, ticket management). However, 'send_email' lacks a description, making its role ambiguous and potentially overlapping with ticket notifications.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in snake_case (e.g., add_employee, create_ticket, list_tickets). No mixing of conventions.

    Tool Count5/5

    6 tools is a reasonable count for an HRMS server covering employee and ticket management. Not too few or too many.

    Completeness3/5

    Missing employee update/delete and ticket detail retrieval. Employee lookup only by name, not ID. Notable gaps in CRUD coverage for both domains.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers