threadmap-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| threadmap_trackA | Track a message in the conversation timeline. Call after each user or assistant message to build the drift map. |
| threadmap_timelineA | Show the full color-coded conversation timeline with drift scores, inflection points, and branches. |
| threadmap_forkA | Fork the conversation from a specific message index. Creates a clean branch with only context up to that point. |
| threadmap_branch_contextA | Get the context packet for a specific branch — summarized intent and messages up to the fork point. |
| threadmap_statusB | Get current drift status — latest color, score, and whether an inflection point was just hit. |
| threadmap_resetA | Reset the session. Archives current thread and starts fresh tracking from a new origin. |
| threadmap_legendA | Show the color legend explaining what each dot color means. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.