Skip to content
Claude Kit

Sequential Thinking

Sequential Thinking

Section titled “Sequential Thinking”

Sequential Thinking provides structured reasoning tools for complex problem-solving, enabling step-by-step analysis with confidence tracking and revision capabilities.

Configuration

Section titled “Configuration”
{
  "mcpServers": {
    "sequential": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-sequential-thinking"]
    }
  }
}

Available Tools

Section titled “Available Tools”

sequentialthinking

Section titled “sequentialthinking”

Dynamic problem-solving through structured thought sequences.

Parameters:

ParameterDescription
thoughtCurrent thinking step
thoughtNumberCurrent step number (1, 2, 3…)
totalThoughtsEstimated total steps needed
nextThoughtNeededWhether more steps are needed
isRevisionIf this revises previous thinking
revisesThoughtWhich thought is being reconsidered
branchFromThoughtBranching point for alternative paths
needsMoreThoughtsIf more analysis is needed

Use Cases

Section titled “Use Cases”

Complex Debugging

Section titled “Complex Debugging”
/fix Intermittent authentication failures

Sequential Thinking:

  1. Defines the question clearly
  2. Gathers evidence systematically
  3. Forms hypotheses with probabilities
  4. Tests most likely cause first
  5. Documents conclusion with confidence

Architecture Decisions

Section titled “Architecture Decisions”
/brainstorm Database migration strategy

Sequential Thinking:

  1. Explores options step-by-step
  2. Tracks trade-offs for each approach
  3. Revises conclusions based on feedback
  4. Builds confidence incrementally

Root Cause Analysis

Section titled “Root Cause Analysis”
/research Why is the build slow?

Sequential Thinking:

  1. Breaks problem into investigation steps
  2. Documents evidence at each step
  3. Adjusts hypothesis as facts emerge
  4. Provides confidence-scored conclusion

Command Integration

Section titled “Command Integration”
CommandHow Sequential Thinking Helps
/fixSystematic root cause analysis
/planStructured task decomposition
/brainstormOrganized design exploration
/researchStep-by-step investigation

Mode Integration

Section titled “Mode Integration”
ModeIntegration
deep-researchPrimary tool for thorough analysis
brainstormStructures creative exploration
reviewSystematic code examination

Example Workflow

Section titled “Example Workflow”

Debugging Session

Section titled “Debugging Session”

Thought 1: Define the problem

"What is causing authentication to fail intermittently for some users?"
→ Confidence: N/A (question definition)

Thought 2: Gather evidence

"Checking logs shows failures occur during peak hours,
primarily for users with special characters in passwords."
→ Confidence: 7/10

Thought 3: Form hypothesis

"Hypothesis A: URL encoding issue with special characters.
Evidence: Failure pattern matches special char passwords.
Probability: 80%"
→ Confidence: 8/10

Thought 4: Test hypothesis

"Tested with password 'test@123' - fails.
Tested with 'test123' - works.
Hypothesis confirmed."
→ Confidence: 9/10

Thought 5: Conclusion

"Root cause: URL encoding mangles special characters.
Fix: Use base64 encoding instead.
Confidence: 9/10"
→ nextThoughtNeeded: false

Best Practices

Section titled “Best Practices”

Start with Clear Questions

Section titled “Start with Clear Questions”

Define what you’re investigating before gathering evidence.

Track Confidence

Section titled “Track Confidence”

Explicitly state confidence levels to identify when more investigation is needed.

Allow Revisions

Section titled “Allow Revisions”

Use isRevision and revisesThought to refine understanding as new information emerges.

Branch When Needed

Section titled “Branch When Needed”

Use branchFromThought to explore alternative hypotheses without losing the main thread.

Resources

Section titled “Resources”