Skip to main content
Glama

Related Servers

Alternatives to deputy-mcp

No user-submitted related servers found.

    Related Servers

    TDQS

    A4.4/5.0

    Scored across 4 tools

    Disambiguation4/5

    Each tool has a distinct role (config check, date-range roster, single next shift, connection status) and descriptions include explicit 'When NOT to use' cross-references that steer selection well. The only soft overlap is between deputy_whoami and deputy_get_my_calendar_url, which both act as 'confirm configuration' probes and could be confused by an agent wanting a simple health check.

    Naming Consistency4/5

    All four tools share the deputy_ prefix and are snake_case, giving a predictable, readable surface. Minor deviation: two are verb_noun (get_my_roster, get_my_calendar_url) while next_shift drops the verb and whoami is a conventional standalone name.

    Tool Count4/5

    Four tools is a tight, well-scoped set for a read-only personal-roster integration, and each tool covers a real user intent. It sits at the thin end of the scale, but nothing feels redundant or padded for the stated iCal-feed mode.

    Completeness4/5

    For the declared read-only personal calendar domain, the surface is essentially complete: identity/mode check, configuration check, a date-range shift list, and a next-shift shortcut, with both markdown and JSON outputs. Gaps are deliberate (no team visibility, no write/lifecycle operations), so agents cannot get stuck on covered workflows but also cannot do anything beyond reading their own shifts.

    Maintenance

    ActivityActive
    ResponsivenessNo issues