HR Assist MCP Server
Allows sending emails via Gmail SMTP for sending welcome emails and manager notifications during employee onboarding.
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 MCP Server Onboard Priya Nair reporting to Tony Sharma"
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 โ MCP Server
An MCP (Model Context Protocol) server that automates HR onboarding tasks โ HRMS registration, welcome emails, IT ticketing, meeting scheduling, and leave management โ so an AI agent like Claude can handle the entire new-hire workflow from a single prompt. ๐
โจ Features
Area | What it does |
๐ค Employee Management | Add employees, fetch details by (fuzzy) name search, look up managers & direct reports |
๐ง Email | Send plain-text or HTML emails (with optional attachments) via SMTP |
๐ซ Ticketing | Raise, update, and list IT/equipment tickets (laptop, ID card, etc.) |
๐ Meetings | Schedule, list, and cancel meetings for any employee |
๐ด Leave Management | Check leave balance, apply for leave, view leave history |
โก Ready-made Prompt | Built-in |
Related MCP server: HRizzle-HR-Assist
๐๏ธ Project Structure
atliq-hr-assist/
โโโ server.py # FastMCP server โ defines all MCP tools & the onboarding prompt
โโโ emails.py # EmailSender โ SMTP email utility (plain/HTML + attachments)
โโโ utils.py # seed_services() โ seeds in-memory demo data
โโโ HRMS/
โ โโโ __init__.py
โ โโโ employee_manager.py # EmployeeManager โ employee CRUD + org hierarchy
โ โโโ meeting_manager.py # MeetingManager โ schedule/list/cancel meetings
โ โโโ leave_manager.py # LeaveManager โ leave balance & history
โ โโโ ticket_manager.py # TicketManager โ IT/equipment tickets
โ โโโ schemas.py # Pydantic models for all entities
โโโ pyproject.toml
โโโ .python-version
โโโ .gitignore
โโโ .env # ๐ local secrets โ never committed๐ Note:
server.pydoesfrom HRMS import *, so the manager classes (employee_manager.py,meeting_manager.py, etc.) andschemas.pyshould live inside anHRMS/package folder alongside__init__.py.
๐ ๏ธ Requirements
๐ Python 3.10+
Dependencies (see
pyproject.toml):fastmcp>=3.4.5mcp[cli]>=1.9.4pydantic>=2.13.4python-dotenv
โ๏ธ Setup
1. Clone & install
git clone https://github.com/Vraj-Data-Scientist/hr-onboarding-agent-with-MCP.git
cd hr-onboarding-agent-with-MCP
# using uv (recommended)
uv sync
# or using pip
pip install -e .2. Configure environment variables
Create a .env file in the project root (already git-ignored ๐):
EMAIL=your-smtp-email@gmail.com
EMAIL_PWD=your-app-specific-passwordโ ๏ธ Security note: Use a Gmail App Password, not your real account password, and never commit
.envto version control. If real credentials were ever pushed to a repo, rotate/revoke them immediately.
3. Run the server standalone (optional, for testing)
python server.pyThis starts the MCP server over stdio transport.
๐ Connecting to Claude as an MCP Client
This server speaks MCP over stdio, so it plugs directly into any MCP-compatible Claude client.
๐ฅ๏ธ Option A โ Claude Desktop
Open your Claude Desktop config file:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
Add this server under
mcpServers:
{
"mcpServers": {
"hr-onboarding-agent": {
"command": "uv",
"args": [
"run",
"--directory",
"/absolute/path/to/hr-onboarding-agent-with-MCP",
"mcp",
"run",
"server.py"
],
"env": {
"EMAIL": "your-smtp-email@gmail.com",
"EMAIL_PWD": "your-app-specific-password"
}
}
}
}Restart Claude Desktop. A ๐จ tools icon should appear, showing the
hr-assistserver connected with tools likeadd_employee,send_email,create_ticket,schedule_meeting, and more.Prompt Claude naturally, e.g.:
"Onboard a new employee named Priya Nair reporting to Tony Sharma."
๐ก Using the built-in onboarding prompt
The server exposes a ready-made MCP prompt, onboard_new_employee, which Claude Desktop (via the / prompt picker) and Claude Code can surface directly โ just supply employee_name and manager_name, and the full onboarding flow runs end-to-end.
๐งช Example
Prompt:
Onboard a new employee with the following details:
- Name: Vraj Dobariya
- Manager Name: Tony SharmaWhat happens automatically:
๐ค Employee added to HRMS with correct manager mapping
๐ง Welcome email sent with generated login
๐จ Manager notified of the new hire
๐ซ Tickets raised for laptop, ID card, and other equipment
๐ Introductory meeting scheduled between employee and manager
Available Tools
12 toolsadd_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
Scored across 12 tools
Most tools have clearly distinct purposes: employee, leave, ticket, meeting, and email operations are separated. However, send_email has no description and could be confused with other notification-style actions, and get_employee_leave_balance vs get_leave_history require careful reading to distinguish.
All names use snake_case with verb_noun structure, which is mostly predictable. Minor deviations exist, such as get_employee_details vs get_meetings, and some names include 'employee' while others rely on context.
12 tools is a well-scoped set for an HR assistant, covering employees, leave, tickets, meetings, and email without feeling bloated or thin. Each tool appears to earn its place.
Core workflows are represented, but there are notable gaps: no list/update/delete employee operations, no leave cancellation or approval, and no ticket detail retrieval. These gaps could force agents to work around missing lifecycle operations.
Maintenance
Related MCP Connectors
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Hosted MCP server connecting AI assistants to 9,000+ apps and 40,000+ actions via Zapier.
One MCP server for the services your AI needs: memory, files, Microsoft 365, kanban and more.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceAn 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-
- AlicenseNot gradedqualityDmaintenanceMCP-based HR automation tool that streamlines employee onboarding, leave management, and equipment requests via natural language conversations.1MIT
- FlicenseBqualityDmaintenanceAn agentic AI system that automates end-to-end HR workflows, from onboarding to scheduling, using the Model Context Protocol (MCP).12-
- FlicenseCqualityDmaintenanceMCP server for HR automation that enables employee onboarding workflows through Claude Desktop.12-