構造化された思考プロセスを通じて動的かつ反射的な問題解決のためのツールを提供する MCP サーバー実装。
複雑な問題を扱いやすいステップに分解する
理解が深まるにつれて考えを修正し洗練させる
代替的な推論の道に分岐する
思考の総数を動的に調整する
解決策の仮説を生成し検証する
Related MCP server: Think MCP
問題解決と分析のための詳細かつ段階的な思考プロセスを促進します。
入力:
thought (文字列): 現在の思考ステップ
nextThoughtNeeded (boolean): 別の思考ステップが必要かどうか
thoughtNumber （整数）：現在の思考番号
totalThoughts (整数): 必要な推定総思考数
isRevision （ブール値、オプション）：これが以前の考えを修正するかどうか
revisesThought (整数、オプション): 再考されている考え
branchFromThought (整数、オプション): 分岐点の思考番号
branchId (文字列、オプション): ブランチ識別子
needsMoreThoughts （ブール値、オプション）: さらに考えが必要な場合
シーケンシャル シンキング ツールは次の目的で設計されています。
複雑な問題を段階的に分解する
修正の余地がある計画と設計
軌道修正が必要な分析
当初は全体の範囲が明確でない可能性がある問題
複数のステップにわたってコンテキストを維持する必要があるタスク
無関係な情報をフィルタリングする必要がある状況
これをclaude_desktop_config.jsonに追加します:
{
"mcpServers": {
"sequential-thinking": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-sequential-thinking"
]
}
}
}{
"mcpServers": {
"sequentialthinking": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"mcp/sequentialthinking"
]
}
}
}ドッカー:
docker build -t mcp/sequentialthinking -f src/sequentialthinking/Dockerfile .このMCPサーバーはMITライセンスに基づいてライセンスされています。つまり、MITライセンスの条件に従って、ソフトウェアを自由に使用、改変、配布することができます。詳細については、プロジェクトリポジトリのLICENSEファイルをご覧ください。
A detailed tool for dynamic and reflective problem-solving through thoughts. This tool helps analyze problems through a flexible thinking process that can adapt and evolve. Each thought can build on, question, or revise previous insights as understanding deepens.
When to use this tool:
Breaking down complex problems into steps
Planning and design with room for revision
Analysis that might need course correction
Problems where the full scope might not be clear initially
Problems that require a multi-step solution
Tasks that need to maintain context over multiple steps
Situations where irrelevant information needs to be filtered out
Key features:
You can adjust total_thoughts up or down as you progress
You can question or revise previous thoughts
You can add more thoughts even after reaching what seemed like the end
You can express uncertainty and explore alternative approaches
Not every thought needs to build linearly - you can branch or backtrack
Generates a solution hypothesis
Verifies the hypothesis based on the Chain of Thought steps
Repeats the process until satisfied
Provides a correct answer
Parameters explained:
thought: Your current thinking step, which can include:
Regular analytical steps
Revisions of previous thoughts
Questions about previous decisions
Realizations about needing more analysis
Changes in approach
Hypothesis generation
Hypothesis verification
next_thought_needed: True if you need more thinking, even if at what seemed like the end
thought_number: Current number in sequence (can go beyond initial total if needed)
total_thoughts: Current estimate of thoughts needed (can be adjusted up/down)
is_revision: A boolean indicating if this thought revises previous thinking
revises_thought: If is_revision is true, which thought number is being reconsidered
branch_from_thought: If branching, which thought number is the branching point
branch_id: Identifier for the current branch (if any)
needs_more_thoughts: If reaching end but realizing more thoughts needed
You should:
Start with an initial estimate of needed thoughts, but be ready to adjust
Feel free to question or revise previous thoughts
Don't hesitate to add more thoughts if needed, even at the "end"
Express uncertainty when present
Mark thoughts that revise previous thinking or branch into new paths
Ignore information that is irrelevant to the current step
Generate a solution hypothesis when appropriate
Verify the hypothesis based on the Chain of Thought steps
Repeat the process until satisfied with the solution
Provide a single, ideally correct answer as the final output
Only set next_thought_needed to false when truly done and a satisfactory answer is reached
| Name | Required | Description | Default |
|---|---|---|---|
| thought | Yes | Your current thinking step | |
| nextThoughtNeeded | Yes | Whether another thought step is needed | |
| thoughtNumber | Yes | Current thought number | |
| totalThoughts | Yes | Estimated total thoughts needed | |
| isRevision | No | Whether this revises previous thinking | |
| revisesThought | No | Which thought is being reconsidered | |
| branchFromThought | No | Branching point thought number | |
| branchId | No | Branch identifier | |
| needsMoreThoughts | No | If more thoughts are needed |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description fully discloses behavioral traits. It explains the iterative, revisable nature of the process ('adjust total_thoughts up or down', 'question or revise previous thoughts'), the ability to branch or backtrack, and the workflow involving hypothesis generation and verification until satisfaction.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is excessively long (over 500 words) and not front-loaded. It includes redundant sections (e.g., 'Key features' and 'You should' lists overlap), and verbose explanations that could be condensed. Many sentences do not earn their place, reducing clarity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity (9 parameters, no annotations, no output schema), the description is mostly complete. It covers purpose, usage, behavior, and parameter semantics thoroughly. However, it lacks explicit information on output format or error handling, and the verbosity hinders effectiveness, preventing a perfect score.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3. The description adds significant value by explaining parameter semantics beyond the schema: it details what 'thought' can include (e.g., 'Revisions of previous thoughts', 'Hypothesis generation'), clarifies the purpose of 'next_thought_needed' and 'needs_more_thoughts', and provides context for revision and branching parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose as 'dynamic and reflective problem-solving through thoughts' and 'analyze problems through a flexible thinking process'. It specifies the verb ('analyze', 'problem-solving') and resource ('problems'), but lacks sibling tools for differentiation, preventing a perfect score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides explicit 'When to use this tool' with 7 specific scenarios (e.g., 'Breaking down complex problems into steps', 'Problems where the full scope might not be clear initially'). It also includes 11 'You should' guidelines that detail when and how to apply the tool effectively.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
sequentialthinkingWith only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined as a dynamic problem-solving process, making it distinct by default.
A single tool inherently has consistent naming, as there are no other tools to compare it against. The name 'sequentialthinking' is descriptive and follows a clear, albeit unique, pattern for this server.
One tool is too few for a server that aims to facilitate dynamic and reflective problem-solving, as it forces all functionality into a single, complex interface. This limits flexibility and could overwhelm users or agents with its many parameters, making it feel thin in scope despite its depth.
The tool covers a broad range of problem-solving steps, but as a single tool, it lacks modularity. There are no obvious gaps in functionality, but the monolithic design might lead to dead ends or inefficiencies in handling diverse tasks that could benefit from separate, specialized tools.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Breaks a hard question or decision into checkable sub-questions, grounds each to a real tool.
Shared reasoning for unresolved, disputed, multi-step, provenance-sensitive problems across agents.
Deterministic reasoning stack for AI agents: simulate, decide & compute, plus cross-domain tools.
Break down complex problems into clear, actionable steps. Adapt on the fly by iterating, revising,…
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/zalab-inc/mcp-sequentialthinking'
If you have feedback or need assistance with the MCP directory API, please join our Discord server