HR Assist MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CB_EMAIL | No | Email address for sending emails (optional, leave blank to run without email) | |
| CB_EMAIL_PWD | No | Gmail app password for the email account (optional) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_employeesA | List all sample employees with IDs, roles, departments, and managers. Use this before creating a new employee so you know valid manager IDs/names. |
| list_managersA | List managers you can assign when creating a new employee. Preferred manager IDs: E001 (Sarah Johnson), E002 (Michael Chen), E003 (David Wilson), E006 (Emily Kim), E009 (Priya Nair). |
| add_employeeA | Add a new employee to the HRMS system. :param emp_name: New employee full name :param manager_id: Manager employee ID OR manager name. Examples: "E001", "Sarah Johnson", "David Wilson". Defaults to E001 (Sarah Johnson) if omitted. :param email: Employee email. If empty, auto-generated as name@atliq.com :return: Confirmation message with new employee ID |
| get_employee_detailsB | Get employee details by name (or partial name). :param name: Name of the employee, e.g. "Tony" or "Sarah Johnson" :return: Employee details |
| send_emailD | – |
| 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 |
| update_ticket_statusB | Update the status of a ticket. :param ticket_id: Ticket ID :param status: New status of the ticket :return: Confirmation message |
| list_ticketsC | List tickets for an employee with optional status filter. :param employee_id: Employee ID (optional) :param status: Ticket status (optional) :return: List of tickets |
| 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 |
| get_meetingsB | Get the list of meetings scheduled for an employee. :param employee_id: Employee ID :return: List of meetings |
| 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 |
| get_employee_leave_balanceB | Get the leave balance of an employee. :param emp_id: Employee ID :return: Leave balance message |
| 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 |
| get_leave_historyB | Get the leave history of an employee. :param emp_id: Employee ID :return: Leave history message |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| onboard_new_employee |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Each tool targets a distinct function (employee, ticket, meeting, leave, email) with clear boundaries. Even send_email, despite lacking a description, is presumably for email sending and doesn't overlap with others.
Tools follow verb_noun snake_case consistently, like create_ticket, list_employees, schedule_meeting. Minor inconsistency: get_employee_leave_balance vs get_leave_history, and list_tickets vs get_meetings, but overall pattern is clear.
14 tools cover employee management, ticketing, meetings, and leave—reasonable for an HR assist server. Not too many or too few.
Covers core HR operations: CRUD for employees (add, get, list), ticketing, meetings, and leave. Missing update/delete for employees, but the set is functional for common tasks.