Skip to main content
Glama
Sign In
mcp-leave

mcp-leave

by zovo-one
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to mcp-leave

No user-submitted related servers found.

    Related Servers

    • leave_manager

      RamehNagella
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables natural-language-based employee leave management including leave balance checks, leave applications, approvals, and history retrieval through an MCP-compatible client.
      -

    • Leave Manager

      AniketDonode
      F
      license
      B
      quality
      C
      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
      -

    • LeaveManager

      DhanyaHegdek
      F
      license
      B
      quality
      D
      maintenance
      Enables managing employee leave requests including checking balance, applying for leave, and viewing history.
      3
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 12 tools

    Disambiguation3/5

    Most tools target distinct actions, but the approve/reject/cancel trio blurs together: leave_approve also reopens rejected requests, and leave_reject's description says voluntary withdrawal should use leave_cancel 'via reject with reason', which contradicts the stated separation. The descriptions work hard to disambiguate, but an agent could still misselect between reject and cancel.

    Naming Consistency3/5

    The leave_* family mostly follows verb-first verb_noun (leave_approve, leave_list, leave_import), but leave_employee_add inverts the order and leave_export_ics adds a suffix. The license_status/license_activate pair uses noun_verb, opposite of the dominant pattern.

    Tool Count4/5

    Twelve tools is well-scoped for a leave tracker, with each operation (request, approve, reject, cancel, list, balance, coverage, import/export) earning a place. The two license tools are peripheral but justified by the free/pro tier model.

    Completeness3/5

    Core lifecycle is covered (create, approve, reject, cancel, list, balance, coverage, import/export), but there is no way to edit an existing request's dates or type, no get-single-request tool, and no employee management beyond add (no list/update/remove of employees).

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources