kiwiHR MCP by usefulapi

Most tools target a distinct resource+action, but the singular/plural pairs (kiwihr_get_attendance_statement vs kiwihr_list_attendance_statements, kiwihr_get_timesheet vs kiwihr_list_timesheets) and the cluster of balance/usage queries (list_time_off_balances, list_overtime_balances, get_time_off_usage) require reading descriptions carefully to pick correctly. The descriptions do resolve the ambiguity once read, so misselection is unlikely but plausible at a glance.

All tools follow a strict kiwihr_verb_noun snake_case pattern with standard CRUD verbs (list_/get_/create_/update_/delete_/activate_/deactivate_). The singular get vs plural list convention is applied consistently, making the pattern predictable.

30 tools is heavy and sits at the borderline where breadth (users, timesheets, projects, journeys, time off, attendance, reference lists) makes each sub-area coherent but the total surface is large for an agent to navigate. Each tool does appear to earn its place, but trimming or grouping would improve usability.

Core domains have solid lifecycle coverage: users (list/get/create/update/deactivate/activate), timesheets (get/list/create/update/delete), and projects (list/get/create/update). Gaps exist in journeys (create/list/get only, no update/cancel/delete) and time off (read-only, no request creation), which agents can only partly work around.