Data as of
mcp-sequentialthinking-tools for Windsurf: Setup & Config
Windsurf: mcp-sequentialthinking-tools records stepwise reasoning with session history, branches, and revision metadata.
What you can do with mcp-sequentialthinking-tools in Windsurf
Pick it for inspectable session-based planning with honest, limited tool-name validation.
- Keep separate session histories with branches and revisions
- Inspect or clear history during a long agent workflow
Before you start: mcp-sequentialthinking-tools in Windsurf
- npx
- An MCP-compatible client
The history limit is per session and defaults to 1000. Its stdio transport accepts Content-Length framing and newline-delimited JSON used by older tmcp tooling.
mcp-sequentialthinking-tools Windsurf configuration
Choose Windsurf configuration scope
For mcp-sequentialthinking-tools, open macOS/Linux: ~/.codeium/windsurf/mcp_config.json Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json. Merge into mcpServers; remote endpoints use serverUrl.
Add mcp-sequentialthinking-tools to Windsurf
Use the mcp-sequentialthinking-tools entry below in mcpServers. Keep mcp-sequentialthinking-tools's documented stdio connection fields and your other Windsurf entries.
Check mcp-sequentialthinking-tools in Windsurf
mcp-sequentialthinking-tools: Refresh MCP in Windsurf settings and inspect Cascade’s tools.
Config file · macOS/Linux: ~/.codeium/windsurf/mcp_config.json
Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json
{
"mcpServers": {
"mcp-sequentialthinking-tools": {
"command": "npx",
"args": [
"-y",
"mcp-sequentialthinking-tools"
],
"env": {
"MAX_HISTORY_SIZE": "<maximum recorded steps per session; default 1000>"
}
}
}
}mcp-sequentialthinking-tools tools available to Windsurf
mcp-sequentialthinking-tools's stored tool list documents 3 tools; compare it with Windsurf's connected tool list, because the stored list is not a live check.
- sequentialthinking_tools
After refreshing mcp-sequentialthinking-tools in Windsurf settings, check Cascade's tool list for sequentialthinking_tools.
Record one reasoning step and optionally validate model-proposed tools against a supplied list.
- get_thinking_history
After refreshing mcp-sequentialthinking-tools in Windsurf settings, check Cascade's tool list for get_thinking_history.
Retrieve recorded session steps, optionally restricted by branch and record limit.
- clear_thinking_history
After refreshing mcp-sequentialthinking-tools in Windsurf settings, check Cascade's tool list for clear_thinking_history.
Troubleshooting mcp-sequentialthinking-tools in Windsurf
- Check npx mcp-sequentialthinking-tools (Node.js/npm) on the machine running Windsurf's MCP integration for mcp-sequentialthinking-tools; refresh MCP and inspect Cascade's tools.
- Check MAX_HISTORY_SIZE for mcp-sequentialthinking-tools; do not bypass a Windsurf permission error with a broad administrator token.
- mcp-sequentialthinking-tools uses stdio here: Windsurf must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
- Known limitation: Does not discover available tools or select tools for the model
- Known limitation: Adds unnecessary overhead for trivial requests
- Known limitation: Text filtering is not a guarantee against adversarial input
- General Windsurf troubleshooting lives in the /clients/windsurf guide.
mcp-sequentialthinking-tools — details. Windsurf guide