thinkLABSCO SUMMARY
Branching that is actually implemented, and a database you can open yourself.
The original server's schema had branch parameters with nothing behind them; here creating, switching, inspecting and merging a branch are separate tools, which is what makes 'explore three approaches and compare' a real move rather than a prompt. The persistence is plain SQLite in a file you can open in any viewer — so the reasoning is inspectable outside the assistant that produced it.
What it is
A fork of Anthropic's sequential-thinking server that replaced its one tool with 20. Thoughts are numbered and written to SQLite as they are added, branches are a full lifecycle rather than two inert parameters, and a session can be reloaded in a different conversation weeks later.
What you get
- think, revise and complete — add a thought, correct an earlier one with the original kept, close the chain with a conclusion
- branch, switch_branch, list_branches, get_branch, close_branch and merge_branch, merging as conclusion only, in full, or as a summary
- get_thought and get_history to retrieve one thought by number or the history filtered by branch
- tag and search — semantic tags such as hypothesis, evidence or decision, then search by content or by tag
- export as markdown or JSON, and visualize as an ASCII or Mermaid diagram of the thought structure
- session_save, session_load, session_list and session_summary — the last returning a compressed version for cheap context loading
- reset to clear the workspace and start again
- Write-through persistence: every think, branch, tag and revise call hits disk as it happens
Requirements
Nothing but npx, or a clone if you prefer. The database lands in the working directory by default; MAXENTIAL_DB_PATH moves it, and setting it to an in-memory value turns persistence off. If SQLite cannot initialise the server falls back to in-memory rather than failing. You do not call these tools yourself — you ask the assistant to think this way and it does the calling.
Setup effort
One command — npx -y @bam-devcrew/maxential-thinking-mcp
USE CASES
01
Comparing approaches without losing the thread
Branch per option, reason through each independently, then merge what each one concluded back into the main chain.
02
Picking up a decision you left half-finished
Browse saved sessions, restore the one you want with its thoughts, branches and tags intact, and carry on.
03
Correcting reasoning that went wrong earlier
Revise the specific thought, with the original kept alongside the revision.
04
Finding the decisions in a long chain
Tag as you go, then search by tag rather than rereading everything.
05
Showing someone how the conclusion was reached
Export the chain as markdown, or generate a diagram of the branch structure.
06
Loading old context cheaply
Pull a compressed summary of the session instead of replaying the whole chain.
20 tools
Listed in project docs. Your client may show a different list.
revisecompleteresetbranchswitch_branchlist_branchesget_branchclose_branchmerge_branchget_thoughtget_historytagsearchexportvisualizesession_savesession_loadsession_listsession_summaryBEFORE YOU INSTALL
What to know first
Tools you get
20 tools named in the project's documentation.
Requires
npx on PATH
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @bam-devcrew/maxential-thinking-mcpMCP Clients
Claude Desktop, Claude Code
JSON
{
"mcpServers": {
"maxential-thinking": {
"command": "npx",
"args": [
"-y",
"@bam-devcrew/maxential-thinking-mcp"
]
}
}
}
