Skip to main content
Glama

Related Servers

Alternatives to work-plan

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Local-first MCP server that gives any AI coding agent per-project memory, workflow intelligence, and always-on, lossless token & context optimization.
      37
      31 npm
      6
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A zero-dependency MCP server that gives agents a versioned memory tree: it classifies incoming messages to isolate casual chat from project memory, opens throwaway branches for exploration, and merges only distilled conclusions back into a persistent mainline state. Milestone checkpoints freeze the mainline into review documents that serve as new baselines, so long sessions keep their hard constraints instead of losing them to rolling summaries.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      A local-first MCP server that snapshots project working state into a structured context object, enabling agents to share and resume sessions seamlessly without leaving your machine.
      6
      5
      Apache 2.0

    TDQS

    C2.6/5.0

    Scored across 30 tools

    Disambiguation2/5

    The set is split into a core agent-facing API and a parallel `ui_*` app-facing API that duplicates much of it: `ui_create_task` vs `task_plan`, `ui_update_task` vs `task_update`, `ui_save_note` vs `note_save`, `ui_save_memory` vs `memory_save`, and `ui_delete_memory` vs `memory_delete`. The 'App-only' labels help somewhat, but an agent still faces several near-identical operations and must infer which layer to use.

    Naming Consistency3/5

    All names are snake_case and resource-prefixed, but the convention shifts between noun_verb (`project_list`, `task_start`, `note_save`, `memory_delete`) and `ui_` + verb_noun (`ui_move_task`, `ui_delete_project`). The `ui_` prefix is consistently applied to app-only tools, which keeps it readable despite the mixed verb placement.

    Tool Count2/5

    30 tools is heavy for a project/task planning server, and roughly half are `ui_*` wrappers duplicating core operations. The effective agent-facing surface is around 15 tools, so many entries do not earn independent places in the set.

    Completeness3/5

    Core lifecycle is covered for projects (list/get/create), tasks (plan/start/update), notes (save/list), and memory (save/list/delete), plus an open-UI tool. However, project update/archive/delete, task deletion, and note deletion exist only as App-only tools, and there is no core task get/delete, leaving notable gaps for agent-driven workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues