S
spences10/mcp-sequentialthinking-tools
Suggest which MCP tool to use at each step
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
- Copy the command above
- Paste it as one entry under
mcpServersinclaude_desktop_config.json— local servers take command + args (example: clients) - Restart your client
Client config (built from the install command this repo gives)
{
"mcpServers": {
"spences10-mcp-sequentialthinking-tools": {
"command": "npx",
"args": ["-y", "mcp-sequentialthinking-tools"]
}
}
}Parsed from the README we fetched on 2026-11-05; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"spences10-mcp-sequentialthinking-tools": {
"command": "npx",
"args": ["-y", "mcp-sequentialthinking-tools"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio spences10-mcp-sequentialthinking-tools -- npx -y mcp-sequentialthinking-tools
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Source
- collected from the abordage/awesome-mcp list · type: MCP server
- Harvest history
- first seen 2026-11-05 · last seen 2026-11-14 · seen 10× · listed by 10 sources
- Score
- score 1,003 · 10 sources · mcp
- Install
npx -y mcp-sequentialthinking-tools
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
npx -y mcp-sequentialthinking-tools. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
first catalogued 2026-11-05；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.
# mcp-sequentialthinking-tools
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
A lightweight MCP server for recording sequential reasoning steps. It
is a scratchpad with history, branching, revision metadata, and
optional validation for model-authored tool plans.
It does not discover your other MCP tools and it does not
choose tools for the model. If you pass availabletools and
recommendedtools, the server validates that the recommended names
exist and stores the step.
## Why use it?
Use this when a task benefits from explicit, inspectable reasoning:
breaking a messy problem into steps;
revising or branching a plan;
keeping a small reasoning history by session;
validating tool-plan names against a supplied tool list;
clearing or inspecting reasoning history during a long agent run.
Do not use it for trivial requests. It adds overhead.
## Tools
### sequentialthinkingtools
Records one thought.
Required parameters:
thought — current reasoning step
thoughtnumber — current step number
totalthoughts — current estimate; automatically raised if lower
than thoughtnumber
nextthoughtneeded — whether another thought is needed
Optional parameters:
sessionid — history bucket; defaults to default
isrevision, revisesthought
branchfromthought, branchid
needsmorethoughts
availabletools — array of tool names or { name, description }
objects
recommendedtools — model-authored recommendations to
validate/store
remainingsteps — short list of upcoming steps
Example:
json
"sessionid": "svelte-debug",
"thought": "First inspect the route files, then run the failing check.",
"thoughtnumber": 1,
"totalthoughts": 3,
"nextthoughtneeded": true,
"availabletools": ["read", "bash"],
"recommendedtools": [
"toolname": "read",
"confidence": 0.9,
"rationale": "Need to inspect the relevant files before editing.",
"priority": 1
If recommendedtools contains a name not present in
availabletools, the call returns isError: true and does not store
the thought.
## Security posture
The server treats thought text, tool descriptions, rationales, and
remaining-step text as untrusted input. Prompt-injection-like text is
scanned and redacted before it is stored or returned in history. Calls
with redactions include securitywarnings showing which fields
matched.
This is defensive filtering, not a guarantee that arbitrary
adversarial text is safe. Do not put secrets in thoughts or tool
descriptions.
### getthinkinghistory
Returns stored thoughts for a session.
Parameters:
sessionid — defaults to default
branchid — optional branch filter
limit — max records to return; default 50, max 500
### clearthinkinghistory
Clears one session or every session.
Parameters:
sessionid — defaults to default
allsessions — clear all history buckets
## Prompt
### sequential-thinking-guidance
A short prompt that tells the model how to use this server honestly:
is a scratchpad with history, branching, revision metadata, and
optional validation for model-authored tool plans.
It does not discover your other MCP tools and it does not
choose tools for the model. If you pass availabletools and
recommendedtools, the server validates that the recommended names
exist and stores the step.
## Why use it?
Use this when a task benefits from explicit, inspectable reasoning:
breaking a messy problem into steps;
revising or branching a plan;
keeping a small reasoning history by session;
validating tool-plan names against a supplied tool list;
clearing or inspecting reasoning history during a long agent run.
Do not use it for trivial requests. It adds overhead.
## Tools
### sequentialthinkingtools
Records one thought.
Required parameters:
thought — current reasoning step
thoughtnumber — current step number
totalthoughts — current estimate; automatically raised if lower
than thoughtnumber
nextthoughtneeded — whether another thought is needed
Optional parameters:
sessionid — history bucket; defaults to default
isrevision, revisesthought
branchfromthought, branchid
needsmorethoughts
availabletools — array of tool names or { name, description }
objects
recommendedtools — model-authored recommendations to
validate/store
remainingsteps — short list of upcoming steps
Example:
json
"sessionid": "svelte-debug",
"thought": "First inspect the route files, then run the failing check.",
"thoughtnumber": 1,
"totalthoughts": 3,
"nextthoughtneeded": true,
"availabletools": ["read", "bash"],
"recommendedtools": [
"toolname": "read",
"confidence": 0.9,
"rationale": "Need to inspect the relevant files before editing.",
"priority": 1
If recommendedtools contains a name not present in
availabletools, the call returns isError: true and does not store
the thought.
## Security posture
The server treats thought text, tool descriptions, rationales, and
remaining-step text as untrusted input. Prompt-injection-like text is
scanned and redacted before it is stored or returned in history. Calls
with redactions include securitywarnings showing which fields
matched.
This is defensive filtering, not a guarantee that arbitrary
adversarial text is safe. Do not put secrets in thoughts or tool
descriptions.
### getthinkinghistory
Returns stored thoughts for a session.
Parameters:
sessionid — defaults to default
branchid — optional branch filter
limit — max records to return; default 50, max 500
### clearthinkinghistory
Clears one session or every session.
Parameters:
sessionid — defaults to default
allsessions — clear all history buckets
## Prompt
### sequential-thinking-guidance
A short prompt that tells the model how to use this server honestly:
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/spences10-mcp-sequentialthinking-tools/)
- Source
- awesome · https://github.com/spences10/mcp-sequentialthinking-tools
- Browse by field
- MCP servers
- Listed by
- 10 independent sources
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.