mcp-session-threads
Related Servers
Alternatives to mcp-session-threads
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server providing feedback-oriented development workflows with a Web UI and desktop application for interactive user confirmation, session tracking, and smart prompt management.2MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for visual feedback, video direction, and QA assertions on web pages, enabling AI agents to read, reply, and resolve annotations in real time.6MIT
- AlicenseNot gradedqualityDmaintenanceProvides a web-based interactive feedback server for MCP, replacing desktop GUI with a browser interface supporting full CJK input and bilingual UI.1MIT
- FlicenseNot gradedqualityCmaintenanceAn 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.-

mcp-reviewofficial
AlicenseAqualityAmaintenanceAn 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.51MIT- AlicenseAqualityBmaintenanceAn 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.9AGPL 3.0
TDQS
Scored across 15 tools
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.
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.
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.
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.