freemcplab / Diretório / Playground / mcp-sequentialthinking-tools

● Comunidade spences10 ⚡ Instantâneo

mcp-sequentialthinking-tools

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

por 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.

▶ Ver demo 📦 Instalar 💡 Casos de uso

Por que usar

Principais recursos

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

Demo ao vivo

Como fica na prática

sequentialthinking-tools.replay ▶ pronto

0/0

Instalar

Escolha seu cliente

~/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
    }
  }
}

Abra Claude Desktop → Settings → Developer → Edit Config. Reinicie após salvar.

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

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

Cursor usa o mesmo esquema mcpServers que o Claude Desktop. Config de projeto vence a global.

VS Code → Cline → MCP Servers → Edit

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

Clique no ícone MCP Servers na barra lateral do Cline, depois "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

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

Mesmo formato do Claude Desktop. Reinicie o Windsurf para aplicar.

~/.continue/config.json

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

O Continue usa um array de objetos de servidor em vez de um map.

~/.config/zed/settings.json

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

Adicione em context_servers. Zed recarrega automaticamente ao salvar.

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

Uma linha só. Verifique com claude mcp list. Remova com claude mcp remove.

Casos de uso

Usos do mundo real: mcp-sequentialthinking-tools

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

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

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

Fluxo

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.✓ Copiado

→ 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.✓ Copiado

→ Clean handoff between tools without skipping checks

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

Armadilhas

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

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

Fluxo

Force a revision

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

→ 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.✓ Copiado

→ Two parallel paths scored

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

Combine com: vibe-check

Combinações

Combine com outros MCPs para 10× de alavancagem

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.✓ Copiado

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.✓ Copiado

Ferramentas

O que este MCP expõe

Ferramenta	Entradas	Quando chamar	Custo
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

Custo e limites

O que custa rodar

Cota de API: None — runs locally
Tokens por chamada: 200–600 per thought
Monetário: Free
Dica: Cap total_thoughts at 5–7; longer chains rarely add value and spend tokens

Segurança

Permissões, segredos, alcance

Armazenamento de credenciais: None required

Saída de dados: None — 100% local

Solução de problemas

Erros comuns e correções

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

Verificar: npx mcp-sequentialthinking-tools --help

Alternativas

mcp-sequentialthinking-tools vs. outros

Alternativa	Quando usar	Troca
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

Mais

Recursos

📖 Leia o README oficial no GitHub

🐙 Ver issues abertas

🔍 Ver todos os 400+ servidores MCP e Skills