Skip to main content
Glama

HR Assist

HR Assist is an AI-powered HR automation agent that uses Claude Desktop and MCP tools to handle tasks like onboarding, leave management, meeting scheduling, and ticket creation.

Architecture

HR Assist Architecture

HR Assist is an agentic AI-powered HR automation system built using Claude Desktop, MCP (Model Context Protocol), and Python.

Claude Desktop acts as the AI agent and MCP client, understanding user requests and deciding which HR actions need to be performed. The MCP server exposes HR operations as tools and connects Claude with the HRMS components.

The system includes the following managers:

  • Employee Manager

  • Leave Manager

  • Meeting Manager

  • Ticket Manager

Related MCP server: hr-assist

How It Works

The user provides an HR request through Claude Desktop. Claude understands the request, selects the required MCP tools, and executes the appropriate actions through the MCP server.

For example, when onboarding a new employee, the system can add the employee, send a welcome email, notify the manager, raise a laptop ticket, schedule an introduction meeting, and handle leave-related actions.

Tool Selection

Tool Selection

Employee Onboarding Inputs

Prompt Inputs

Meeting Scheduling

Meeting Time Selection

Onboarding Result

Onboarding Summary

MCP Tools

The project provides tools for:

  • πŸ‘€ Adding and retrieving employees

  • πŸ—“οΈ Managing leave

  • πŸ“§ Sending emails

  • πŸ“… Scheduling meetings

  • 🎫 Creating HR/IT tickets

  • πŸš€ Supporting employee onboarding workflows

Project Structure

hrms/
β”œβ”€β”€ employee_manager.py
β”œβ”€β”€ leave_manager.py
β”œβ”€β”€ meeting_manager.py
β”œβ”€β”€ ticket_manager.py
└── schemas.py

images/
β”œβ”€β”€ architecture.png
β”œβ”€β”€ tool_selection.png
β”œβ”€β”€ prompt_inputs.png
β”œβ”€β”€ meeting_time_selection.png
└── onboarding_summary.png

server.py
emails.py
utils.py
pyproject.toml
README.md

Tech Stack

  • 🐍 Python

  • πŸ€– Claude Desktop

  • πŸ”Œ Model Context Protocol (MCP)

  • πŸ“¦ uv

  • βœ‰οΈ Gmail SMTP

  • 🏒 HRMS Components

Setup

Clone the repository and install the dependencies:

uv sync

Run the MCP server:

uv run python server.py

Configure the MCP server with Claude Desktop and start interacting with HR Assist.

Example

User:
Onboard a new employee named Likhitha and assign Tony Sharma as the manager.

HR Assist:
βœ“ Employee added
βœ“ Welcome email sent
βœ“ Manager notified
βœ“ Laptop ticket created
βœ“ Introduction meeting scheduled
βœ“ Leave status checked

Conclusion

HR Assist demonstrates how agentic AI + MCP tools can automate real-world HR workflows by allowing an AI agent to understand requests, select tools, and execute multiple actions autonomously.

Available Tools

7 tools
add_employeeD

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

apply_leaveD

Inputs: emp_id (required), leave_dates (required). Returns: result

create_ticketD

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

get_employee_detailsD

Inputs: name (required). Returns: object

get_leave_historyD

Inputs: emp_id (required). Returns: result

schedule_meetingD

Inputs: topic (required), emp_id (required), emp_name (required), meeting_dt (required), +1 more. Returns: result

send_emailD

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

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    C2/5.0

    Scored across 7 tools

    Disambiguation4/5

    Tool names map to fairly distinct actions (employee CRUD-ish, email, ticketing, meetings, leave), so an agent can mostly tell them apart. However, with no descriptions provided, boundaries like add_employee vs get_employee_details and the generic send_email/create_ticket/schedule_meeting are only inferable from names, leaving mild ambiguity.

    Naming Consistency5/5

    All seven tools follow a clean snake_case verb_noun pattern (add_employee, get_employee_details, apply_leave, get_leave_history, etc.). No mixing of conventions or vague standalone verbs.

    Tool Count5/5

    Seven tools is well-scoped for an HR assistant spanning employee records, leave, and administrative actions. Each tool appears to earn its place without redundancy.

    Completeness3/5

    The surface covers create/read for employees and full leave apply/history, but lacks update_employee, delete/offboard, or a list_employees operation, creating dead ends in the employee lifecycle. Generic email/ticket/meeting tools are present but no supporting read/list operations for them.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers