
Sequential Thinking
STDIOStructured problem-solving server with sequential thinking and iterative refinement capabilities.
Structured problem-solving server with sequential thinking and iterative refinement capabilities.
A powerful MCP server implementing sequential thinking protocol that provides a structured approach to problem-solving. This server helps break down complex problems into manageable steps while maintaining flexibility for revisions and alternative reasoning paths.
Facilitates a detailed, step-by-step thinking process for problem-solving and analysis.
Parameter | Type | Required | Description |
---|---|---|---|
thought | string | Yes | The current thinking step |
nextThoughtNeeded | boolean | Yes | Whether another thought step is needed |
thoughtNumber | integer | Yes | Current thought number |
totalThoughts | integer | Yes | Estimated total thoughts needed |
isRevision | boolean | No | Whether this revises previous thinking |
revisesThought | integer | No | Which thought is being reconsidered |
branchFromThought | integer | No | Branching point thought number |
branchId | string | No | Branch identifier |
needsMoreThoughts | boolean | No | If more thoughts are needed |
The Sequential Thinking tool is ideal for:
{ "mcpServers": { "sequential-thinking": { "command": "npx", "args": [ "-y", "@zengwenliang/mcp-server-sequential-thinking" ] } } }
{ "mcpServers": { "sequential-thinking": { "command": "docker", "args": [ "run", "--rm", "-i", "zengwenliang0416/mcp-server-sequential-thinking" ] } } }
# Install globally npm install -g @zengwenliang/mcp-server-sequential-thinking # Or use NPX directly npx -y @zengwenliang/mcp-server-sequential-thinking
{ "mcpServers": { "sequential-thinking": { "command": "npx", "args": [ "-y", "@zengwenliang/mcp-server-sequential-thinking" ] } } }
cd /path/to/sequential-thinking npm install npm run build
{ "mcpServers": { "sequential-thinking": { "command": "node", "args": [ "/absolute/path/to/sequential-thinking/dist/index.js" ] } } }
# Build Docker image docker build -t zengwenliang0416/mcp-server-sequential-thinking .
{ "mcpServers": { "sequential-thinking": { "command": "docker", "args": [ "run", "--rm", "-i", "zengwenliang0416/mcp-server-sequential-thinking" ] } } }
#!/bin/sh export CURSOR_MCP_CONFIG=/path/to/your/mcp_config.json open -a Cursor
mcp_config.json
:{ "mcpServers": { "sequential-thinking": { "command": "node", "args": [ "/absolute/path/to/sequential-thinking/dist/index.js" ] } } }
chmod +x start_cursor_with_mcp.sh
Note: MCP integration is primarily supported in the Composer feature of Cursor IDE.
git clone https://github.com/zengwenliang416/mcp-server-sequential-thinking.git cd mcp-server-sequential-thinking npm install npm run build
git clone https://github.com/zengwenliang416/mcp-server-sequential-thinking.git cd mcp-server-sequential-thinking docker build -t zengwenliang0416/mcp-server-sequential-thinking . # Verify the build docker images | grep sequential-thinking
Update version in package.json
{ "name": "@zengwenliang/mcp-server-sequential-thinking", "version": "0.6.4", "description": "MCP server for sequential thinking and problem solving" }
Use official npm registry
npm config set registry https://registry.npmjs.org/
Login to npm
npm login
Follow the prompts to log in through your browser.
Check organization membership For scoped packages, ensure you're part of the scope:
# Check if you're part of the organization npm org ls your-org-name # For personal scopes, this is automatically created with your username
Build and publish
npm run build # For first-time publishing a scoped package npm publish --access public # For subsequent updates npm publish
Verify publication
npm view @zengwenliang/mcp-server-sequential-thinking
Commit your changes
git add . git commit -m "feat(publish): 🚀 发布npm包@zengwenliang/mcp-server-sequential-thinking" git push
Use semantic versioning:
# For patches (bug fixes) npm version patch # For minor updates (features) npm version minor # For major updates (breaking changes) npm version major
After updating the version, build and publish again:
npm run build npm publish
Add these secrets to your repository settings:
NPM_TOKEN
DOCKERHUB_USERNAME
DOCKERHUB_TOKEN
To test your automated publishing workflow:
Note for 2FA Users: If you have Two-Factor Authentication enabled on your npm account, you must either:
- Use an "Automation" type token (recommended)
- Change 2FA settings to "Authorization only" (not recommended)
- Manually publish packages (not automated)
If you encounter integration issues:
chmod +x dist/index.js
This project is licensed under the MIT License - see the LICENSE file for details.
Based on modelcontextprotocol/servers and maintained at zengwenliang416/mcp-server-sequential-thinking.