threadmap-mcp
Related Servers
Alternatives to threadmap-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceProvides persistent context management for Claude AI coding assistants, allowing you to save and restore conversation context, create checkpoints, and organize information across sessions to prevent losing important work history and decisions during long coding sessions.122 npm135MIT
- AlicenseAqualityCmaintenanceClarity and memory for Claude. Persistent memory, intelligent context ranking, safety modes, and session checkpoints for Claude Desktop & Claude Code in a single install.2038 npm1MIT
- AlicenseNot gradedqualityDmaintenanceSearch and reference your Claude Code conversation history directly from Claude, with full-text search, conversation viewing, and project browsing.8 npmMIT
- AlicenseAqualityDmaintenanceCross-surface persistent memory for Claude. Bridges context between Claude Chat, Code, and Cowork via local SQLite with full-text search.611 npm6MIT
- AlicenseNot gradedqualityDmaintenanceCaptures live conversation snapshots every 5 prompts and provides semantic recall to maintain context across Claude Code sessions.4 npmMIT
- FlicenseNot gradedqualityNot gradedmaintenanceAutomatically injects development framework context and workflows into Claude conversations, ensuring Claude follows your established patterns without manual context provision each time. Supports custom frameworks, keyword triggers, and Knowledge Graph integration.-
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: track, timeline, status, fork, branch_context, reset, legend. No two tools overlap in function, so an agent can reliably select the correct one.
All tools share the threadmap_ prefix, which aids recognition. However, the suffix mixes verbs (fork, reset, track) and nouns (status, legend, timeline), deviating from a strict verb_noun convention. This is a minor inconsistency.
Seven tools is well-scoped for a conversation drift tracking server. Each tool addresses a specific need and the set feels neither sparse nor bloated.
The core workflow of tracking messages, viewing timeline/status, forking branches, and accessing branch context is well covered. Minor gaps exist, such as no explicit branch listing or branch deletion, but these are not critical for the primary use case.