mcp-mayo
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAYO_API_KEY | Yes | The token value placed on the hrmlicense header; authenticates Foundation, Attendance, and Payroll in a single credential |
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_active_employeesA | List active employees as of a given date, optionally scoped to a department. KNOWN ISSUE: The |
| list_resigned_employeesA | List employees who resigned or took leave within a date range. KNOWN ISSUE: The |
| get_organization_treeA | Get the organization hierarchy as of a specific date. KNOWN ISSUE: The |
| export_organization_with_employeesC | Export effective organization units together with their employees (OM + PA). |
| export_employeesA | Export effective employee master data (core fields only). |
| export_departmentsA | Export effective department master data (core fields only). |
| export_organization_fullC | Export effective organization master data with all fields (OM endpoint). |
| export_employees_fullC | Export effective employee data with every PA field. Supports many optional filters. |
| export_expatriationsB | Export effective employee expatriation (外派/派駐) assignments. |
| export_working_historyA | Export all employees' work-experience records. |
| export_education_historyA | Export all employees' education records. |
| export_employee_changesA | Export employee change orders within a date range (paginated). |
| export_organization_changesB | Export organization change orders within a date range (paginated). |
| export_pa_optionsC | Export reference code tables used by the People+ (PA) module. |
| export_company_custom_fieldsB | Export the custom field definitions configured by the tenant. |
| get_attendance_rulesA | Get each employee's base attendance configuration as of a given date. Returns the shift, rest-day rule, and attendance-group information that
applies to every active employee on |
| get_attendance_historyA | Get raw clock-in / clock-out records across all employees within a date range. |
| get_attendance_abnormalA | Get attendance exceptions (late, early leave, missed punch, etc.) within a date range. |
| get_forgot_checkin_recordsA | Get manually-added or corrected clock-in records within a date range. |
| get_leave_historyA | Get approved and pending leave applications within a date range (leave_historyV2). |
| get_employee_calendarA | Get each employee's assigned shift calendar (work day / rest day / holiday) for a range. |
| get_overtime_recordsB | Get approved overtime records within a date range. |
| get_trip_historyA | Get business trip / field-work records within a date range. KNOWN ISSUE: This endpoint is marked as failing upstream in MAYO's own Postman collection. Expect a server-side error response until MAYO fixes it. |
| get_monthly_labor_insuranceB | Get the monthly labor insurance (勞保) detail list for an insurance unit. KNOWN ISSUE: This endpoint is marked as failing upstream in MAYO's own Postman collection. Expect a server-side error response until MAYO fixes it. |
| get_monthly_nhiA | Get the monthly National Health Insurance (健保) detail list for a unit. KNOWN ISSUE: This endpoint is marked as failing upstream in MAYO's own Postman collection. Expect a server-side error response until MAYO fixes it. |
| get_monthly_labor_pensionA | Get the monthly labor pension (勞退) detail list for a unit. KNOWN ISSUE: This endpoint is marked as failing upstream in MAYO's own Postman collection. Expect a server-side error response until MAYO fixes it. |
| get_salary_insurance_detailA | Get per-employee salary insurance contribution detail for a given date. |
| get_salary_bonus_listA | Get the salary and bonus distribution roster across a month range. Accepts ISO-style |
| get_employee_profileA | Aggregate one employee's master, work history, and education into a single profile. Calls PA (filtered by employee_number) plus the company-wide Working and Education exports, then filters the latter two down to the target employee. Useful when an assistant needs a complete picture without having to call three raw tools and join the results. |
| get_organization_snapshot_as_ofA | Capture the organization tree and active headcount as of a specific date. Combines KNOWN ISSUE: Both underlying Report Center routes currently 404 on the PRE Foundation backend. This composite tool will light up once MAYO redeploys those endpoints. |
| get_attendance_summaryA | Build a consolidated attendance picture for a date range. Fans out to |
| search_active_employeesB | List active employees as of a date, defaulting to today when KNOWN ISSUE: Wraps |
| get_monthly_payroll_reportA | Get the salary and bonus distribution roster for a single month. Accepts ISO |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 33 tools
Several tool pairs have unclear boundaries, such as list_active_employees vs search_active_employees, get_salary_bonus_list vs get_monthly_payroll_report, and export_employees vs export_employees_full. While descriptions attempt to differentiate them, the overlap makes it easy for an agent to select the wrong tool.
Most tools follow a snake_case verb_noun pattern, but the verbs are inconsistent: list, get, search, and export are used interchangeably without a clear rule. For example, list_active_employees and search_active_employees both exist, and get_ vs export_ prefixes are used for similar data.
With 33 tools, the server is well beyond the typical 3-15 range. Although the HR domain is broad, many tools are redundant or could be consolidated, such as the multiple export variants and monthly insurance getters, making the count feel excessive.
The server covers a wide range of HR data including employees, organization, attendance, leave, salary, insurance, and expatriation. Composite tools like get_employee_profile and get_attendance_summary fill gaps, though write operations are absent, which is acceptable for a reporting-focused server.