Skip to main content
Glama
hr-assist

hr-assist

HR-ASSIST Agentic AI System


HR ASSIST is an Agentic AI system designed to help HR teams automate routine workflows. This example demonstrates automation of the employee onboarding process, streamlining tasks that typically require manual intervention.

In terms of technical architecture, for MCP client we use Claude Desktop and the code base here represents the MCP server with necessary tools that will be used by MCP client

🛠️ Setup Instructions

To set up and run HR ASSIST, follow these steps:

  • Configure claude_desktop_config.json Add the following configuration to your claude_desktop_config.json file:

    {
    "mcpServers": {
        "hr-assist": {
        "command": "C:\\Users\\dhaval\\.local\\bin\\uv",
        "args": [
            "--directory",
            "C::\\code\\atliq-hr-assist",
            "run",
            "server.py"
        ],
        "env": {
            "CB_EMAIL": "YOUR_EMAIL",
            "CB_EMAIL_PWD": "YOUR_APP_PASSWORD"
        }
        }
    }
    }
  • Replace YOUR_EMAIL with your actual email.

  • Replace YOUR_APP_PASSWORD with your email provider’s app-specific password (e.g., for Gmail).

Related MCP server: HR-ASSIST

đź§  AI Development Conversation

This project was developed and tested using Claude Desktop as the AI client, with MCP used to connect the AI assistant to the HR tools and services.

👉 View the Claude Desktop conversation

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_leaveA

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 of the meeting in python datetime format :param topic: Topic of the meeting (optional) :return: Confirmation message

Inputs: topic (required), employee_id (required), meeting_datetime (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: item (required), emp_id (required), reason (required). Returns: result

get_employee_detailsB

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_balanceB

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

Inputs: emp_id (required). Returns: result

get_leave_historyB

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

Inputs: emp_id (required). Returns: result

get_meetingsB

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_ticketsA

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_meetingA

Schedule a meeting for an employee. :param employee_id: Employee ID :param meeting_datetime: Date and time of the meeting in python datetime format :param topic: Topic of the meeting :return: Confirmation message

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

send_emailD

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

    C2.8/5.0

    Scored across 12 tools

    Disambiguation4/5

    Tools have distinct purposes related to employee management, leave, tickets, and meetings. However, 'send_email' has no description, creating ambiguity about its scope and potential overlap with other communication tools.

    Naming Consistency4/5

    Most tool names follow a consistent verb-noun pattern (e.g., get_leave_history, add_employee, update_ticket_status). Minor deviations like 'send_email' and 'schedule_meeting' still fit the pattern, but the mix of 'emp_id' and 'employee_id' in parameters is slightly inconsistent.

    Tool Count5/5

    12 tools is well-scoped for an HR assistant, covering employee records, leave, tickets, and meetings without redundancy. Each tool appears to serve a distinct function.

    Completeness3/5

    Core operations for leave and tickets are present, but missing update/delete for employee records and leave, and the 'send_email' tool lacks description, suggesting an incomplete or unclear communication surface.

    Related MCP Connectors

    Related MCP Servers