Skip to main content
Glama

HR-ASSIST: Agentic AI for HR Automation

Python Claude MCP Status

An Agentic AI system that automates end-to-end HR workflows, from onboarding to scheduling, using the Model Context Protocol (MCP).


Overview

HR-ASSIST is an intelligent automation system built as part of the Codebasics Gen AI Bootcamp.

It transforms the Claude Desktop App into a powerful HR assistant capable of interacting with local databases, sending real emails, and managing calendars.

Unlike standard chatbots, HR-ASSIST uses Agentic Workflows to execute complex, multi-step tasks autonomously.

The Problem

HR managers spend hours toggling between HRMS software, email clients, and ticketing systems to onboard a single employee.

The Solution

A unified interface where natural language turns into action.

  • Input: "Onboard Ruchitha as a Data Analyst."

  • Output: Employee record created + Welcome email sent + IT ticket raised + Orientation meeting scheduled.


Related MCP server: HR-ASSIST

See it in Action

1. Agentic Scheduling

2. Pre-built Prompt Templates

Scheduling Demo

Onboarding UI

The Agent intelligently parses dates to schedule meetings.

Custom UI forms for structured data entry.


Key Features

Feature

Description

MCP Prompts

Pre-configured templates (UI forms) for complex tasks like onboarding.

HRMS Integration

Custom Tool execution to search, add, and update employee records.

Email Automation

automated SMTP integration to send secure credentials via Gmail.

Ticket Management

Auto-generation of support tickets for IT equipment.

Intelligent Calendar

Natural language date parsing for meeting management.


Technical Architecture

graph TD
    User[HR Manager] -->|Selects Template| UI[Claude Desktop UI]
    UI -->|MCP Protocol| Server[HR-Assist Python Server]
    Server -->|Write| DB[(Local HR Database)]
    Server -->|Send| SMTP[Gmail API]
    Server -->|Create| Ticket[Ticket System]

Tech Stack

  • Language: Python 3.10+

  • Protocol: Model Context Protocol (MCP) by Anthropic

  • Dependency Management: uv

  • Libraries: fastmcp, pydantic, python-dotenv


Repository Structure


atliq-hr-assist/
├── hrms/                   # Core Business Logic Package
│   ├── __init__.py         # Package initialization
│   ├── employee_manager.py # Employee CRUD operations
│   ├── leave_manager.py    # Leave balance logic
│   ├── meeting_manager.py  # Calendar scheduling
│   ├── ticket_manager.py   # IT support ticketing
│   └── schemas.py          # Pydantic data models
├── images/                 # Documentation screenshots
│   ├── demo_onboard.png
│   └── demo_schedule.png
├── server.py               # Main MCP Server Entry Point
├── emails.py               # SMTP Email Handler
├── utils.py                # Helper functions (Data seeding)
├── .env                    # Email and Passwords (Excluded from repo)
├── .gitignore              # Git ignore rules
├── pyproject.toml          # Project dependencies configuration
└── uv.lock                 # Dependency lock file (ensures reproducibility)

Setup & Installation

  1. Clone the Repository

git clone [https://github.com/YOUR_USERNAME/hr-assist-mcp-agent.git](https://github.com/YOUR_USERNAME/hr-assist-mcp-agent.git)
cd hr-assist-mcp-agent
  1. Install Dependencies

uv init
uv add "mcp[cli]" python-dotenv
  1. Configure Environment Create a .env file for your credentials:

CB_EMAIL=your_email@gmail.com
CB_EMAIL_PWD=your_app_password
  1. Connect to Claude Add the server path to your claude_desktop_config.json:

{
  "mcpServers": {
    "hr-assist": {
      "command": "uv",
      "args": ["--directory", "ABSOLUTE_PATH", "run", "server.py"],
      "env": { "CB_EMAIL": "...", "CB_EMAIL_PWD": "..." }
    }
  }
}

Usage Guide

Method 1: Natural Language

Simply type in the chat bar:

"Schedule a meeting for employee E001 tomorrow at 10 AM regarding Project Kickoff."

  1. Click the Attach button or type / in Claude.

  2. Select onboard_new_employee.

  3. Fill in the form fields:

  • Employee Name: Ruchitha

  • Manager Name: Dhaval

  1. Hit Run. The Agent will execute the entire workflow automatically.


Future Improvements

  • Database: Migrate from in-memory storage to SQLite/PostgreSQL.

  • Frontend: Build a Streamlit dashboard to view the generated tickets.

  • Auth: Add Role-Based Access Control (RBAC) for manager approvals.


📄 License

  • Developed as part of the Codebasics Gen AI Bootcamp.

  • Copyright © Codebasics Inc.

Available Tools

12 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: email (required), emp_name (required), manager_id (required). Returns: result

apply_leaveC
Apply for leave for an employee.
:param emp_id: Employee ID
:param leave_dates: List of leave dates
:return: Leave application status message

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

cancel_meetingC
Cancel a scheduled meeting for an employee.
:param employee_id: Employee ID
:param meeting_datetime: Date and time in ISO format (YYYY-MM-DD HH:MM:SS)
:param topic: Topic of the meeting (optional)
:return: Confirmation message

Inputs: topic (required), employee_id (required), meeting_datetime (required). Returns: result

create_ticketC
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: item (required), emp_id (required), reason (required). Returns: result

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

Inputs: name (required). Returns: result

get_employee_leave_balanceC
Get the leave balance of an employee.
:param emp_id: Employee ID
:return: Leave balance message

Inputs: emp_id (required). Returns: result

get_leave_historyC
Get the leave history of an employee.
:param emp_id: Employee ID
:return: Leave history message

Inputs: emp_id (required). Returns: result

get_meetingsC
Get the list of meetings scheduled for an employee.
:param employee_id: Employee ID
:return: List of meetings

Inputs: employee_id (required). Returns: result

list_ticketsC
List tickets for an employee with optional status filter.
:param employee_id: Employee ID
:param status: Ticket status (optional)
:return: List of tickets

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

schedule_meetingB
Schedule a meeting for an employee.
:param employee_id: Employee ID
:param meeting_datetime: Date and time in ISO format (YYYY-MM-DD HH:MM:SS)
:param topic: Topic of the meeting
:return: Confirmation message

Inputs: topic (required), employee_id (required), meeting_datetime (required). Returns: result

send_emailC
Send an email to one or more recipients.
:param to_emails: List of email addresses
:param subject: Email subject
:param body: Email body content
:return: Success message

Inputs: body (required), subject (required), to_emails (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: status (required), ticket_id (required). Returns: result

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 12 tools

    Disambiguation4/5

    Each tool has a distinct purpose, and there is no significant overlap between them. The only minor potential confusion is between 'get_employee_details' and 'get_employee_leave_balance' or 'get_leave_history', but these are clearly differentiated by their output focus.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., add_employee, get_employee_details, send_email), with no deviations. The naming is predictable and easy to understand.

    Tool Count5/5

    12 tools is a well-scoped number for an HR assistant, covering key operations without being overwhelming. Each tool appears to earn its place by addressing a specific need.

    Completeness3/5

    While core operations like employee management, ticketing, meetings, and leave are present, there are notable gaps: no update or delete for employees, no meeting update, and no way to list all employees or get details by ID. These missing operations could cause agent failures in common workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      An MCP-powered HR management system that automates employee onboarding, leave tracking, meeting scheduling, and IT ticketing. It allows users to manage organizational workflows and administrative tasks through natural language interactions with Claude.
      2
      -
    • F
      license
      B
      quality
      D
      maintenance
      Agentic AI system that automates HR workflows like employee onboarding, enabling HR teams to streamline tasks through natural language interactions with Claude Desktop.
      12
      -
    • F
      license
      D
      quality
      D
      maintenance
      An AI-powered HR assistant that automates employee management, leave handling, ticket creation, meeting scheduling, and email notifications through natural language conversations using the Model Context Protocol.
      11
      -
    • F
      license
      C
      quality
      D
      maintenance
      Agentic HR assistant providing employee, leave, meeting, ticket, and email tools over the Model Context Protocol, designed to automate onboarding workflows via an MCP client such as Claude Desktop.
      14
      -