Skip to main content
Glama
jade-mcp
by choiyounggi

Related Servers

Alternatives to jade-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      9
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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
    • F
      license
      B
      quality
      D
      maintenance
      Enables managing employee records, leave balances, and leave requests through MCP tools and resources, including submitting and approving leave, checking balances, and adding employees.
      6
      1
      -
    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables 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

    A3.9/5.0

    Scored across 31 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count3/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data