Structured chain-of-thought tool — lets the model plan and revise hypotheses through multiple thinking steps.
An MCP server implementation that provides a tool for dynamic and reflective problem-solving through a structured thinking process.
Facilitates a detailed, step-by-step thinking process for problem-solving and analysis.
Inputs:
thought (string): The current thinking stepnextThoughtNeeded (boolean): Whether another thought step is neededthoughtNumber (integer): Current thought numbertotalThoughts (integer): Estimated total thoughts neededisRevision (boolean, optional): Whether this revises previous thinkingrevisesThought (integer, optional): Which thought is being reconsideredbranchFromThought (integer, optional): Branching point thought numberbranchId (string, optional): Branch identifierneedsMoreThoughts (boolean, optional): If more thoughts are neededThe Sequential Thinking tool is designed for:
In practice, you do not call sequential_thinking directly by hand unless your client exposes raw tool calls. Instead, connect the server to an MCP-aware host and ask the model to think through a problem step by step. The host can then decide to call the tool one or more times while it works.
Example prompts that typically benefit from this tool:
Plan a database migration from PostgreSQL 14 to 16, list risks, and revise the plan if downtime exceeds 5 minutes.Debug why this deployment only fails in production and show your reasoning step by step.Compare three architecture options for a file sync engine and branch if one assumption turns out to be wrong.If your host or inspector shows tool activity, you should see repeated calls to sequential_thinking with fields such as:
thoughtthoughtNumbertotalThoughtsnextThoughtNeededWhen the reasoning changes course, you may also see revision or branching fields like isRevision, revisesThought, branchFromThought, or branchId.
After installing the server in your MCP host:
sequential_thinking tool appears in the host's MCP tool list or inspector.Add this to your claude_desktop_config.json:
{
"mcpServers": {
"sequential-thinking": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-sequential-thinking"
]
}
}
}
On Windows, use cmd /c to launch npx:
{
"mcpServers": {
"sequential-thinking": {
"command": "cmd",
"args": [
"/c",
"npx",
"-y",
"@modelcontextprotocol/server-sequential-thinking"
]
}
}
}
{
"mcpServers": {
"sequentialthinking": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"mcp/sequentialthinking"
]
}
}
}
To disable logging of thought information set env var: DISABLE_THOUGHT_LOGGING to true.
For quick installation, click one of the installation buttons below...
For manual installation, you can configure the MCP server using one of these methods:
Method 1: User Configuration (Recommended)
Add the configuration to your user-level MCP configuration file. Open the Command Palette (Ctrl + Shift + P) and run MCP: Open User Configuration. This will open your user mcp.json file where you can add the server configuration.
Method 2: Workspace Configuration
Alternatively, you can add the configuration to a file called .vscode/mcp.json in your workspace. This will allow you to share the configuration with others.
For more details about MCP configuration in VS Code, see the official VS Code MCP documentation.
For NPX installation:
{
"servers": {
"sequential-thinking": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-sequential-thinking"
]
}
}
}
On Windows, use:
{
"servers": {
"sequential-thinking": {
"command": "cmd",
"args": [
"/c",
"npx",
"-y",
"@modelcontextprotocol/server-sequential-thinking"
]
}
}
}
For Docker installation:
{
"servers": {
"sequential-thinking": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"mcp/sequentialthinking"
]
}
}
}
Run the following:
codex mcp add sequential-thinking npx -y @modelcontextprotocol/server-sequential-thinking
Docker:
docker build -t mcp/sequentialthinking -f src/sequentialthinking/Dockerfile .
This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.
Be the first to comment.