Skip to main content
Glama

Related Servers

Alternatives to Progressor

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Gives AI coding agents persistent, cross-session memory by storing task insights as interlinked markdown knowledge cards and recalling relevant ones before new work begins. Uses plain files and git sync instead of a vector database or embeddings, and exposes this through MCP tools for Claude Code, Cursor, VS Code Copilot, Codex, Windsurf, and other clients.
      4 npm
      ISC
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to save and recall atomic markdown knowledge cards with bidirectional links across sessions, sharing persistent memory across MCP clients and syncing via git. Supports searching, writing, linking, organizing, importing, and browsing memory through MCP tools.
      4 npm
      ISC
    • A
      license
      A
      quality
      B
      maintenance
      Enables coding agents to store, search, and retrieve long-term memory as plain Markdown files with a disposable SQLite index, including note management, decision/bug tracking, and codebase symbol lookup via MCP.
      8
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      A structured project memory MCP server that persists plans, builds, reviews, and decisions across AI coding sessions and tools, enabling continuous project management with a dashboard.
      11
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides persistent, local-first memory for coding agents with Markdown as the source of truth, exposed via CLI, loopback API, MCP, and Codex hooks for context retrieval and durable writes.
      MIT

    TDQS

    A3.7/5.0

    Scored across 16 tools

    Disambiguation5/5

    The tools map cleanly to distinct entities and state transitions: goals, tasks, detours, ideas, standing instructions, and status reads. Pairs such as complete_goal vs release_goal and start_task vs update_task are differentiated by outcome, so an agent should not confuse them.

    Naming Consistency5/5

    All 16 tools use consistent snake_case verb_noun names (get_status, add_goal, start_detour, promote_idea), with no mixed conventions. The pattern is predictable across entities.

    Tool Count4/5

    16 tools is slightly above the typical 3-15 range but still reasonable for a stateful workflow manager covering goals, tasks, detours, ideas, and instructions. Each tool maps to a distinct operation, with little evident redundancy.

    Completeness3/5

    Core goal/task/detour lifecycle is covered, including claiming, starting, completing, and dropping work. However, there is no tool to list/read the full Roadmap or to update/delete goals, ideas, or standing instructions, which are notable gaps for discovery and maintenance.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues