thread-mind-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 | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| project_createA | Create a new ThreadMind project with a main thread |
| project_listA | List all ThreadMind projects |
| project_switchC | Switch to a different project |
| thread_createB | Create a new child thread branching from a parent thread |
| thread_switchC | Switch to a different thread |
| thread_listA | Display the thread tree for the active project |
| summary_updateB | Update the summary/content of a thread |
| context_getA | Get the assembled context for the active thread (walks up the parent chain). Call this at the start of every session. |
| thread_deleteA | Delete a thread and all its descendants |
| thread_rebaseA | Move a thread to a different parent. All descendants move with it. Similar to git rebase. |
| threadmind_initB | Generate instruction files (CLAUDE.md, .cursorrules, etc.) to enable automatic ThreadMind integration with AI clients |
| stats_showA | Show token savings statistics for the active ThreadMind project |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| start-thread | Load the assembled ThreadMind context for the active thread. Use this at the start of every conversation to inject structured context instead of relying on chat history. |
| summarize-thread | Generate a structured summary for the current thread. The AI will produce a summary that can be saved with summary_update. |
| tm-help | Show all available ThreadMind commands and tools |
| tm-context | Get the assembled context for the active thread (shortcut for context_get) |
| tm-tree | Display the thread tree for the active project (shortcut for thread_list) |
| tm-create | Create a new child thread (shortcut for thread_create) |
| tm-switch | Switch to a different thread (shortcut for thread_switch) |
| tm-summary | Update the summary for the active thread (shortcut for summary_update) |
| tm-rebase | Move a thread to a different parent (shortcut for thread_rebase) |
| tm-stats | Show token savings statistics (shortcut for stats_show) |
| tm-init | Generate instruction files for AI clients (shortcut for threadmind_init) |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| current-context | The assembled context for the active thread (walks up the parent chain) |
| thread-tree | Thread tree visualization for the active project |
TDQS
Scored across 12 tools
All tools have clearly distinct purposes: context_get, project_create/list/switch, stats_show, summary_update, thread_create/delete/list/rebase/switch, and threadmind_init each target a unique action with no overlapping functionality.
Tool names follow a consistent verb_noun snake_case pattern (e.g., context_get, project_create, thread_rebase). Even 'threadmind_init' fits as verb_noun with 'threadmind' as a compound noun.
12 tools is well-scoped for a hierarchical thread management system, covering project and thread lifecycle without being excessive or insufficient.
Core thread operations are present, but missing project deletion and a direct way to retrieve a single thread's content (only full context via context_get) creates notable gaps.