Skip to main content
Glama

Related Servers

Alternatives to handoff-desk

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents on the same machine to exchange asynchronous messages as plain Markdown files, with optional wake-up notifications per agent.
      5 npm
      1
      AGPL 3.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables a planning Claude chat and Claude Code to exchange work through local Markdown files, letting the chat create tasks that code agents pick up, complete, and report back on. Project-scoped task and report tools track each item's status from open through reported, eliminating manual copy-paste between the two clients.
      5
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Gives AI coding agents persistent cross-session memory by storing atomic markdown knowledge cards with bidirectional wiki-links that agents recall before starting work. Syncs across clients and devices via git without any vector database or embeddings.
      13 npm
      ISC
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to save insights from completed tasks as atomic markdown knowledge cards with bidirectional links, then recall relevant cards before starting new work so context carries across sessions. Cards live in a shared local directory readable and editable by humans, with optional git-based sync across devices and clients, and no vector database or embeddings required.
      13 npm
      ISC
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to file and track issues, plan epics with steps, comment as they work, and hand decisions back to the user through a local Markdown- and YAML-backed issue tracker.
      MIT

    TDQS

    A3.6/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools target distinct objects: handoff_send creates a request for the user's agent, handoff_list/handoff_read inspect desk items, handoff_wait polls one item, and handoff_inbox/handoff_inbox_reply handle the reverse direction. The only soft overlap is handoff_send vs handoff_status (both write to the desk), but the descriptions clearly separate errands/questions from one-line status lines.

    Naming Consistency3/5

    All names share the handoff_ prefix and snake_case, which is helpful, but the verb convention is mixed: send/list/read/wait are verbs while status, capabilities, inbox are nouns and inbox_reply is noun+verb. It remains readable, but there is no predictable verb_noun pattern to infer new tools from.

    Tool Count5/5

    Eight tools is well within a comfortable range and each covers a distinct step of the handoff loop: create, poll, inspect, enumerate, plus policy lookup and inbox exchange. Nothing appears redundant or padded.

    Completeness4/5

    The round trip is covered end to end: send a request, wait for the reply, read the content, and answer notes the other agent left, with a capabilities lookup for policy. The gap is lifecycle mutation — there is no tool to cancel, withdraw, or close a desk item or to dismiss an inbox note, so an abandoned request can only be left waiting.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues