sequential-thinking-mcp-v2
by spideynolove·★ 8·Score 41
A structured reasoning MCP server with session persistence and memory management
Overview
Sequential Thinking MCP v2 is a local MCP server that implements structured reasoning, session persistence, and project memory management. It follows a first principle thinking framework with an approved design for a layered memory architecture. The server manages reasoning lifecycles through scratch reasoning, checkpoint summaries, promoted conclusions, and canonical docs. It plans to integrate cloud-assisted operations with local-first fallback when network access fails.
Try asking AI
After installing, here are 7 things you can ask your AI assistant:
When to choose this
Choose this for complex coding tasks requiring persistent memory across sessions and structured reasoning approaches.
When NOT to choose this
Avoid if you need immediate production stability, as this is undergoing architectural redesign with unclear implementation timeline.
Tools this server exposes
7 tools extracted from the READMEretrieve_contextRetrieve relevant context for the current task
search_docsSearch through canonical documentation
search_memorySearch through promoted memory artifacts
promote_memoryPromote reasoning to durable memory
summarize_sessionCreate a summary of the current session
generate_handoffGenerate a handoff bundle for session continuity
map_changed_modulesMap modules that have changed during the session
Comparable tools
Installation
Installation
- Clone the repository:
git clone https://github.com/spideynolove/sequential-thinking-mcp-v2.git
cd sequential-thinking-mcp-v2- Install dependencies and run the server:
uv sync
uv run main.py- For Claude Desktop integration, add the following to your
claude_desktop_config.json:
{
"mcpServers": {
"sequential-thinking": {
"command": "python",
"args": ["main.py"],
"cwd": "/path/to/sequential-thinking-mcp-v2"
}
}
}FAQ
- What is the memory architecture design?
- The design uses markdown as canonical human truth, qmd for document retrieval, Zvec for promoted artifacts, and a structured metadata store for lifecycle state.
- How does token management work?
- The project targets an active context ceiling of 64K with compaction triggers at 45K. It retrieves on demand, checkpoints at subtask boundaries, and compresses old context.
- What happens when network access fails?
- The server operates with a cloud-assisted, local-first fallback approach, ensuring functionality even when internet access is unavailable.
Compare sequential-thinking-mcp-v2 with
Last updated · Auto-generated from public README + GitHub signals.