Structured Thinking
A unified MCP server for multiple structured thinking tools that help Claude organize its thoughts in complex problem-solving scenarios. This server provides:
- Template Thinking : Use structured templates for different thinking styles
- Verification Thinking : Systematically verify claims and assumptions
Overview
Structured Thinking provides a collection of complementary thinking tools that help Claude break down complex problems and verify its reasoning. Each tool serves a different purpose but shares a common interface and can be used together.
Features
- Persistent Data Storage : Templates, sessions, and verification chains are automatically saved to disk and loaded when the server restarts
- Predefined Templates : Includes templates for analysis, debugging, decision making, and more
- Custom Templates : Create your own templates for domain-specific thinking patterns
- Structured Verification : Systematically verify claims with confidence tracking
Tools Included
Template Thinking
Uses predefined or custom templates to guide structured thinking:
- Analysis frameworks for breaking down complex problems
- Decision making with criteria evaluation
- Debugging approaches for systematic troubleshooting
- Planning templates for implementation steps
- Custom templates for domain-specific thinking
Verification Thinking
Provides systematic verification of claims and assertions:
- Logical verification of reasoning steps
- Factual verification of claims
- Code correctness verification
- Mathematical proof verification
- Consistency checking across statements
- Counter-example generation
Installation
Place this project in your custom MCP tool directory:
cd /your-custom-mcp-dir
git clone https://github.com/adam-versed/structured-thinking.git
cd structured-thinking
npm install
npm run build
Add to your claude_desktop_config.json:
"template-thinking": {
"command": "node",
"args": [
"/your-custom-mcp-dir-here/structured-thinking/dist/index.js"
]
},
"verification-thinking": {
"command": "node",
"args": [
"/your-custom-mcp-dir-here/structured-thinking/dist/index.js"
]
}
Persistence
Structured thinking tools now maintain persistence between sessions:
- Storage Location : Data is saved in
~/.structured-thinking/ directory in your home folder
- What's Saved :
- Custom templates (including usage statistics for built-in templates)
- Active sessions with their progress
- Verification chains and steps
- Auto-save : Data is automatically saved after each operation
- Auto-load : Data is loaded when the server starts
Usage Tips
To encourage Claude to use these tools, add to your Claude Profile Settings (or system prompt):
When I ask you to "analyze methodically," use template-thinking. When I ask you to "verify your reasoning," use verification-thinking.
Example Usage
Template Thinking
// Start a new session with the analysis template
claude.templateThinking({
templateId: "analysis-template"
});
// Update a step in the session
claude.templateThinking({
sessionId: "session-1234567890",
stepId: "step-1",
content: "We need to implement a user authentication system that supports both password and OAuth login methods."
});
// List available templates
claude.templateThinking({
command: { type: "list-templates" }
});
// Create a custom template
claude.templateThinking({
createTemplate: {
name: "API Design Review",
category: "analysis",
description: "Template for reviewing API designs",
steps: [
{ content: "Review API endpoints for RESTfulness", order: 1 },
{ content: "Validate request/response schemas", order: 2 },
{ content: "Check error handling", order: 3 },
{ content: "Assess security considerations", order: 4 },
{ content: "Evaluate performance implications", order: 5 }
]
}
});
Verification Thinking
// Start a new verification chain
claude.verificationThinking({
subject: "Authentication system security analysis"
});
// Add a verification step
claude.verificationThinking({
chainId: "chain-1234567890",
type: "logical",
claim: "JWT tokens with proper expiration times will prevent session hijacking",
verification: "This is partially true. While proper expiration helps mitigate some risks, it doesn't fully prevent token theft via XSS attacks."
});
// Update a verification step with evidence
claude.verificationThinking({
chainId: "chain-1234567890",
stepId: "step-1234567890",
verification: "Research confirms that while JWT expiration is important, it must be combined with secure transmission (HTTPS) and proper storage (HttpOnly cookies).",
status: "verified",
evidence: "OWASP best practices document recommends multiple layers of protection beyond just token expiration."
});
// List all chains
claude.verificationThinking({
command: { type: "list-chains" }
});
Credits
Based on the sequential-thinking tool by the Model Context Protocol. Enhanced with structured thinking tools, persistence, and IDE chat output formatting.
