Branch Thinking MCP Server
# Branch Thinking
An MCP server that implements branch-based thought navigation, with support for:
- Multiple branches of thought
- Branch navigation (list, focus, history)
- Cross-references between related thoughts
- Insight generation from key points
- Branch priority tracking
This is based on the `sequential-thinking` tool available here:
https://github.com/modelcontextprotocol/servers/tree/main/src/sequentialthinking
## Features
- **Branch Management**: Create and navigate between different lines of thought
- **Cross References**: Link related thoughts across branches with typed relationships
- **Insights**: Automatically generate insights from key points in thoughts
- **Priority Tracking**: Track branch priorities based on confidence and connections
## Commands
- `list`: Show all branches with their current status
- `focus [branchId]`: Switch focus to a specific branch
- `history [branchId?]`: Show the history of thoughts in a branch
## Installation
Place this project in your custom MCP tool directory.
```bash
npm install
npm run build
```
Add to your `claude_desktop_config.json`:
```json
"branch-thinking": {
"command": "node",
"args": [
"/your-custom-mcp-dir-here/branch-thinking/dist/index.js"
]
}
```
## Tips
Claude often will not use tools unless explicitly prompted to do so.
If you want to use this tool without being prompted, add to either your Claude Profile Settings (or a system prompt) something like so:
_If I ask you to "think step by step," "think before you respond," or "use chain of thought," that means use the branch-thinking tool. Don't hesitate to use the branch-thinking tool on your own if you think your response would benefit from multiple steps._
## Credits
I can't pretend that I wrote most of this code. Most of it was generated by Claude. The concept was my own, and so were testing, fixes, and implementation.
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'branch-thinking' has a clear and distinct purpose for managing thought branches, making disambiguation perfect.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'branch-thinking' follows a clear noun-based pattern, and there are no other tools to cause inconsistency.
A single tool is too few for the apparent scope of managing multiple branches of thought with features like listing, focusing, and showing history. This server likely needs additional tools (e.g., for creating branches, adding thoughts, or deleting branches) to be well-scoped, making the count inappropriate.
The tool surface is severely incomplete for the domain of thought management. While the tool handles listing, focusing, and history, there are significant gaps such as creating or deleting branches, adding or modifying thoughts, and managing insights or cross-references directly, which will cause agent failures in comprehensive workflows.