jade-mcp
Related Servers
Alternatives to jade-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables MCP clients to read users, absences, absence types, entitlement balances, rotas, public holidays and groups from an absence management system, and optionally book, update or delete absences.9MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude and other MCP clients to query and register HR data from TramitApp, including employees, clockings, absences, shifts, and vacation balances, with multi-company support.MIT
- AlicenseAqualityDmaintenanceEnables employee time tracking with clock-in/out, workday checking, and time log retrieval via MCP tools.41MIT
- FlicenseBqualityDmaintenanceEnables managing employee records, leave balances, and leave requests through MCP tools and resources, including submitting and approving leave, checking balances, and adding employees.61-
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables querying attendance information and managing employee leave requests, overtime requests, and schedules.-
- -licenseNot gradedqualityNot gradedmaintenanceEnables interaction with employee management systems through a standardized MCP interface. Supports comprehensive employee operations including CRUD operations, search, filtering by level/status, and data synchronization.-
TDQS
Scored across 31 tools
The dominant prepare_*/commit_* pairing makes each tool's role legible, and descriptions explicitly cross-reference siblings (e.g. remote-work cancellation pointing to jade_prepare_remote_work_revert, and delete/retract vs. attendance-cancel distinctions). The residual ambiguity is in clusters like jade_prepare_remote_work vs. jade_prepare_remote_work_day vs. jade_prepare_remote_work_revert, plus four separate 'cancel-ish' flows (overtime cancel, attendance cancel, delete/retract applications, remote-work revert) that an agent must read carefully to pick correctly.
Everything uses a stable jade_ prefix with snake_case and a predictable verb_noun scheme for the prepare/commit pairs (prepare_punch/commit_punch, prepare_vacation/commit_vacation). The deviations are the noun-only readers (jade_today, jade_calendar, jade_applications, jade_doctor, jade_attendance_cancel_candidates), which is a minor but noticeable break in the pattern.
31 tools is heavy for an attendance/leave domain, with 14 prepare/commit pairs accounting for most of the surface. The doubling is defensible as a safety pattern (validate, then submit with a one-time token), but it pushes the set past the comfortable range and makes token-to-commit bookkeeping a real burden for the agent.
Coverage is broad and lifecycle-complete for the core workflows: punch in/out, vacation, overtime and its cancellation, remote work (monthly, single day, revert), schedule changes, clock-correction requests, application listing, and delete/retract. The notable gap is creation of other attendance request types that only appear as cancellable candidates (e.g. business trips), and there is no approval-side or team-visibility tool.