Skip to main content
Glama

Related Servers

Alternatives to mcp-session-threads

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      MCP server providing feedback-oriented development workflows with a Web UI and desktop application for interactive user confirmation, session tracking, and smart prompt management.
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides a web-based interactive feedback server for MCP, replacing desktop GUI with a browser interface supporting full CJK input and bilingual UI.
      1
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that establishes feedback-oriented development workflows with a Web UI and desktop app, allowing users to provide interactive feedback to AI models through prompts, images, and session tracking.
      -
    • A
      license
      A
      quality
      A
      maintenance
      An MCP server for in-loop design review of web previews. It enables agents to submit a preview URL, receive structured findings with suggested fixes, and recheck after applying changes, while never editing code itself.
      5
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      An MCP server designed for managing One-By-One (OBO) review sessions through specialized tools for creating, navigating, and resolving priority-scored items. It automates session tracking and item management within standardized JSON workflows to replace manual file-write operations.
      9
      AGPL 3.0

    TDQS

    B3.4/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools map cleanly to distinct lifecycle actions (create, resolve, defer, resume, list, backup). However, add_message reopens resolved threads, which overlaps with reopen_thread, and resume_thread acts like a reopen for deferred threads, so an agent could occasionally misselect.

    Naming Consistency4/5

    Core thread operations follow a clear verb_noun pattern: create_thread, resolve_thread, defer_thread, reopen_thread. A few outliers like wait_for_feedback, work_on_thread, and start_working/finish_working break the pattern but remain readable and predictable.

    Tool Count4/5

    Fifteen tools is at the high end of the typical well-scoped range, and most earn their place in the thread lifecycle. The set feels slightly over-scoped because working-state indicators and backup_board are auxiliary UI/durability extras rather than core thread operations.

    Completeness3/5

    The lifecycle is well covered: create, message, resolve, reopen, defer, resume, list, and feedback collection. The notable gap is the lack of a tool to retrieve a thread's full message history or body—only list_threads summaries and get_notes are available—so an agent cannot reconstruct previous thread content from the server alone.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues