Allows sending emails via Gmail as part of employee onboarding workflow.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@HR-ASSIST Onboard Alice, Software Developer, start date 2025-04-01"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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\\dhanush\\.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).
Run uv init and uv add mcp[cli] as per the video tutorial in the course.
Usage
Click on the + icon and select the Add from hr-assist option, and send the request.
Fill the details for the new employee:
Alternatively, you can draft a custom prompt and let the agent take over.
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 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 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: employee_id (required), meeting_datetime (required), topic. Returns: result
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 the list of meetings scheduled for an employee. :param employee_id: Employee ID :return: List of meetings
Inputs: employee_id (required). Returns: result
Get employee details by name. :param name: Name of the employee :return: Employee ID and manager ID
Inputs: name (required). Returns: result
Get the leave balance of an employee. :param emp_id: Employee ID :return: Leave balance message
Inputs: emp_id (required). Returns: result
Get the leave history of an employee.
Args: emp_id (str): the employee ID for whom the leave history is being requested
Returns: List[Dict[str, str]]: List of leave history entries
Inputs: emp_id (required). Returns: result
List tickets for an employee with optional status filter. :param employee_id: Employee ID (optional) :param status: Ticket status (optional) :return: List of tickets
Inputs: status, employee_id. Returns: result
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
Inputs: body (required), subject (required), to_emails (required), html. Returns: result
Update the status of a ticket. :param ticket_id: Ticket ID :param status: New status (Open, In Progress, Closed)
Inputs: status (required), ticket_id (required). Returns: result
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 12 tools
Each tool targets a distinct resource/action: employee management, email, tickets, meetings, and leave. No two tools overlap in purpose, making selection unambiguous.
All tools follow a consistent verb_noun pattern in snake_case (add_employee, get_employee_details, create_ticket, schedule_meeting, etc.). No mixed conventions or chaotic naming.
With 12 tools covering multiple HR sub-domains (employee, ticket, meeting, leave, email), the count is well-scoped and appropriate for the server's purpose, neither too thin nor overwhelming.
Core workflows are covered: employee creation/retrieval, ticket lifecycle (create/update/list), meeting scheduling/cancellation/list, leave balance/apply/history. Minor gaps exist (e.g., no employee update/delete, no single ticket detail, no leave cancellation) but they are workable.
Agentic-AI operations platform for any business — automate sales, finance, support and back-office w
Build and manage AI-native customer support agents from Claude or any MCP client.
Give AI agents 30,000+ safe, token-optimized actions across Workday, SAP, Oracle + hundreds more.
Connect your AI assistant to your Peak HR portal: HR operations, people, documents and drafts.
