freemcplab / Verzeichnis / Playground / mcp-sequentialthinking-tools

● Community spences10 ⚡ Sofort

mcp-sequentialthinking-tools

Name: mcp-sequentialthinking-tools MCP Server
Author: spences10

von spences10 · spences10/mcp-sequentialthinking-tools

Force your agent to think step-by-step AND suggest which other MCP tool to invoke at each step — a meta-planner for multi-tool workflows.

A fork of the canonical Sequential Thinking MCP that goes one step further: at every thought, it scores and recommends the best MCP tools from your installed set. Useful when Claude has 10+ MCPs loaded and keeps picking the wrong one.

▶ Demo ansehen 📦 Installieren 💡 Anwendungsfälle

Warum nutzen

Hauptfunktionen

Step-by-step reasoning with confidence scores per step
Recommends which MCP tools to call at each step and why
Supports branching thoughts and revisions
Single tool, trivial to install and uninstall

Live-Demo

In der Praxis

sequentialthinking-tools.replay ▶ bereit

0/0

Installieren

Wählen Sie Ihren Client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "sequentialthinking-tools": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-sequentialthinking-tools"
      ],
      "_inferred": true
    }
  }
}

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "sequentialthinking-tools": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-sequentialthinking-tools"
      ],
      "_inferred": true
    }
  }
}

Cursor nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "sequentialthinking-tools": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-sequentialthinking-tools"
      ],
      "_inferred": true
    }
  }
}

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "sequentialthinking-tools": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-sequentialthinking-tools"
      ],
      "_inferred": true
    }
  }
}

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "sequentialthinking-tools",
      "command": "npx",
      "args": [
        "-y",
        "mcp-sequentialthinking-tools"
      ]
    }
  ]
}

Continue nutzt ein Array von Serverobjekten statt einer Map.

~/.config/zed/settings.json

{
  "context_servers": {
    "sequentialthinking-tools": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "mcp-sequentialthinking-tools"
        ]
      }
    }
  }
}

In context_servers hinzufügen. Zed lädt beim Speichern neu.

claude mcp add sequentialthinking-tools -- npx -y mcp-sequentialthinking-tools

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

Anwendungsfälle

Praxisnahe Nutzung: mcp-sequentialthinking-tools

How to plan a multi-MCP workflow with sequentialthinking-tools

👤 Power users with many MCPs installed ⏱ ~5 min beginner

Wann einsetzen: You have Sentry + GitHub + Linear + Playwright + Notion all loaded and Claude keeps calling the wrong one or skipping steps.

Ablauf

Ask for a plan before execution

Before doing anything, use sequentialthinking_tools to plan: 'Triage the top Sentry issue, find the culprit commit on GitHub, file a Linear ticket.' Give 5 steps with tool recommendations.✓ Kopiert

→ Numbered plan with tool names + confidence scores
Execute one step at a time

Execute step 1. After done, show me the result and the next-step recommendation.✓ Kopiert

→ Clean handoff between tools without skipping checks

Ergebnis: Predictable tool usage, fewer wrong-tool detours, and an audit trail of reasoning.

Fallstricke

Model still picks a wrong tool despite the plan — Explicitly reject the bad choice in the next turn; the planner learns in-context

Break reasoning loops with sequentialthinking-tools

👤 Developers building agents that get stuck retrying ⏱ ~10 min intermediate

Wann einsetzen: Your agent is looping on the same failing approach and not re-evaluating.

Ablauf

Force a revision

Use sequentialthinking_tools with is_revision=true to revisit step 3 of your current plan. What assumption was wrong?✓ Kopiert

→ A named assumption and an alternative tool or approach
Branch into a parallel plan

Create a branch from step 3 and propose a different tool path. Compare confidence to the original.✓ Kopiert

→ Two parallel paths scored

Ergebnis: Agent breaks out of the loop with a reasoned pivot.

Kombinieren mit: vibe-check

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

sequentialthinking-tools + vibe-check

Plan + sanity-check — sequentialthinking plans the steps, vibe-check challenges the plan before execution

Plan a refactor with sequentialthinking_tools, then call vibe_check to poke holes before I run it.✓ Kopiert

sequentialthinking-tools + shrimp-task-manager

Turn each planned step into a persistent task

Plan with sequentialthinking_tools, then hand each step to shrimp-task-manager as a tracked task.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

Werkzeug	Eingaben	Wann aufrufen	Kosten
sequentialthinking_tools	thought: str, next_thought_needed: bool, thought_number: int, total_thoughts: int, is_revision?: bool, branch_from_thought?: int	Start of any multi-step or multi-MCP task where tool choice matters	0 — local reasoning wrapper

Kosten & Limits

Was der Betrieb kostet

API-Kontingent: None — runs locally
Tokens pro Aufruf: 200–600 per thought
Kosten in €: Free
Tipp: Cap total_thoughts at 5–7; longer chains rarely add value and spend tokens

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: None required

Datenabfluss: None — 100% local

Fehlerbehebung

Häufige Fehler und Lösungen

Tool recommendations are generic / unrelated to installed MCPs

The recommender works from names in the prompt — include a short list of your installed MCPs in the system prompt

Agent ignores the plan and jumps to action

Explicitly say 'do not call any other tool until you finish the sequential plan'

npx can't find the package

Try npm cache clean --force or pin a version: npx -y mcp-sequentialthinking-tools@latest

Prüfen: npx mcp-sequentialthinking-tools --help

Alternativen

mcp-sequentialthinking-tools vs. andere

Alternative	Wann stattdessen	Kompromiss
Sequential Thinking MCP (canonical)	You don't need tool recommendations, just step-by-step thinking	No tool suggestions — the main upside of this fork is lost
vibe-check	You want metacognitive feedback instead of sequential decomposition	Different shape — vibe-check interrupts, this one plans

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen