Skip to main content
Glama

MCP Think Tool Server

npm version license TypeScript MCP

A Model Context Protocol (MCP) server that implements the "think" tool for enhancing complex reasoning capabilities in Large Language Models (LLMs). This tool provides LLMs with a dedicated space for structured thinking during problem-solving tasks, significantly improving performance in complex scenarios requiring policy adherence and multi-step reasoning.

🧠 Overview

The Think Tool MCP server is based on Anthropic's research demonstrating that providing LLMs with a dedicated "thinking space" dramatically improves performance on complex tasks. This tool allows any compatible LLM (Claude, GPT-4, and others) to:

  • Break down complex problems into manageable steps

  • Perform structured reasoning and analysis

  • Verify policy compliance during decision-making

  • Process and synthesize information from multiple tool calls

  • Maintain context and logical flow in long reasoning chains

As described in Anthropic's blog post, the think tool has shown significant improvements in tasks requiring complex reasoning and policy adherence across different language models.

Related MCP server: MCP Advanced Reasoning Server

✨ Features

  • πŸ”§ Structured Thinking Space: Provides LLMs with a dedicated environment for complex reasoning

  • πŸ“ Memory Aid: Helps maintain context during long chains of tool calls

  • 🎯 Policy Verification: Enables careful policy adherence checking

  • πŸ” Problem Decomposition: Supports breaking down complex problems into steps

  • ⚑ Lightweight: Minimal overhead with efficient MCP implementation

  • πŸ”Œ Easy Integration: Simple setup with popular AI platforms (Cursor, Claude Desktop, etc.)

  • πŸ› οΈ TypeScript: Built with TypeScript for type safety and better development experience

  • 🌐 Universal Compatibility: Works with any LLM that supports the Model Context Protocol

πŸš€ Platform Configuration

Cursor IDE

Requirements: Cursor version 0.45.6 or higher

  1. Open Cursor Settings (Cmd/Ctrl + ,)

  2. Navigate to Features β†’ MCP Servers

  3. Click "+ Add New MCP Server"

  4. Configure the server:

    • Name: think-tool-mcp (or your preferred name)

    • Type: command

    • Command: npx -y think-tool-mcp

  5. Save and restart Cursor

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "think-tool": {
      "command": "npx",
      "args": ["-y", "think-tool-mcp"]
    }
  }
}

Config file locations:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Other MCP-Compatible Platforms

This server works with any platform supporting the Model Context Protocol. Refer to your platform's documentation for MCP server configuration.

πŸ“Š Performance Analysis

Extensive research by Anthropic has demonstrated significant performance improvements when LLMs use the think tool. The following results showcase the measurable impact across different benchmarks and use cases.

Ο„-Bench (Tau-Bench) Results

Ο„-Bench is a comprehensive benchmark designed to test LLM tool usage in realistic customer service scenarios. It evaluates the ability to navigate complex conversations, follow detailed policy guidelines, and maintain consistency across multiple task trials.

Airline Domain Performance

The airline domain represents a complex policy-heavy environment where precise adherence to detailed rules is critical.

Configuration

k=1

k=2

k=3

k=4

k=5

Think + Optimized Prompt

0.584

0.444

0.384

0.356

0.340

Think Tool Alone

0.404

0.254

0.186

0.140

0.100

Extended Thinking

0.412

0.290

0.232

0.192

0.160

Baseline (No Think Tool)

0.332

0.206

0.148

0.116

0.100

Key Findings:

  • 54% relative improvement in pass^1 metric (0.584 vs 0.370 baseline)

  • Optimized prompting with examples dramatically enhanced performance

  • Improvements maintained across all trial consistency levels (k=1 to k=5)

Retail Domain Performance

The retail domain has simpler policies, allowing the think tool to show benefits even without extensive prompting.

Configuration

k=1

k=2

k=3

k=4

k=5

Think Tool (No Prompt)

0.812

0.735

0.685

0.650

0.626

Extended Thinking

0.770

0.681

0.623

0.581

0.548

Baseline

0.783

0.695

0.643

0.607

0.583

Key Findings:

  • 3.7% improvement in pass^1 metric without additional prompting

  • Demonstrates effectiveness across varying complexity levels

  • Consistent performance gains maintained across multiple trials

SWE-Bench Results

SWE-Bench evaluates coding performance on real-world software engineering tasks. The think tool contributed to Claude 3.7 Sonnet achieving state-of-the-art performance.

Performance Impact:

  • Baseline Score: 62.3% (without think tool)

  • With Think Tool: 64.9% (estimated based on 1.6% improvement)

  • Statistical Significance: Welch's t-test: t(38.89) = 6.71, p < .001, d = 1.47

  • Sample Size: 30 samples with think tool, 144 samples without

Performance Insights

When Think Tool Excels

  1. Policy-Heavy Environments: Up to 54% improvement when complex rule adherence is required

  2. Sequential Decision Making: Significant gains when each action builds on previous ones

  3. Tool Output Analysis: Enhanced performance when processing results from multiple tool calls

  4. Complex Domain Navigation: Greater benefits in challenging domains (airline vs. retail)

Optimization Factors

  1. Domain-Specific Prompting: Examples tailored to specific use cases dramatically improve effectiveness

  2. Complexity Correlation: More complex domains benefit more from structured thinking

  3. Consistency Improvements: Benefits maintained across multiple trial runs, indicating robustness

  4. Error Reduction: Helps LLMs handle edge cases and unusual scenarios more effectively

Comparative Analysis

Approach

Airline Domain (k=1)

Retail Domain (k=1)

Implementation Effort

Baseline

0.332

0.783

None

Extended Thinking

0.412 (+24%)

0.770 (-1.7%)

Platform-dependent

Think Tool

0.404 (+22%)

0.812 (+3.7%)

Minimal

Think + Optimized Prompt

0.584 (+76%)

N/A

Low

Key Takeaway: The think tool provides substantial performance improvements with minimal implementation overhead, making it an excellent choice for enhancing LLM capabilities in complex reasoning scenarios.

πŸ“¦ Installation

The fastest way to get started:

npx -y think-tool-mcp

Global Installation

For persistent usage across projects:

npm install -g think-tool-mcp

Local Development Installation

For contributing or local development:

git clone https://github.com/abhinav-mangla/think-tool-mcp.git
cd think-tool-mcp
npm install
npm run build
npm start

🎯 Usage Examples

Complex Problem Solving

Human: Help me optimize our company's supply chain with 5 warehouses and 12 retail locations.

LLM: I'll help you optimize your supply chain. Let me think through this systematically.

[Uses think tool]
Thought: This is a complex optimization problem requiring:
1. Analysis of warehouse-retail location distances
2. Shipping cost calculations between all pairs
3. Delivery time constraints evaluation
4. Inventory capacity considerations
5. Demand pattern analysis

I need to formulate this as a linear programming problem and consider both cost minimization and delivery time constraints...

[Proceeds with structured solution based on analysis]

Policy Adherence

Human: Can I return this opened product after 45 days without a receipt?

LLM: Let me carefully check our return policy.

[Uses think tool]
Thought: Analyzing this return request:
- Item: 45 days old (exceeds standard 30-day window)
- No receipt available
- Package opened

Policy considerations:
- Standard returns require 30 days + receipt
- Store credit might be possible with purchase verification
- Product category affects policy (electronics vs. clothing)
- Loyalty members may have extended windows
- Manager override possibilities

[Provides policy-compliant response with available options]

Multi-Tool Analysis

Human: Find inactive premium users (60+ days) and create a re-engagement campaign.

LLM: I'll search the database and create a targeted campaign.

[Runs database queries]
[Uses think tool]
Thought: Query results show 342 inactive premium users. Key patterns:
- 45% are in 6-12 month subscription cohort
- 72% last activity was "viewed dashboard"
- Only 8% used newest features
- 28% had support tickets before going inactive

Campaign strategy:
- Segment users by usage patterns
- Highlight unexplored features
- Address support-related pain points
- Personalize incentives based on history

[Creates targeted email campaign based on analysis]

πŸ”§ API Reference

Available Tools

think

Provides LLMs with a dedicated space for complex reasoning and analysis.

Parameters:

  • thought (string, required): The thought process, reasoning, or analysis to record

Description: The think tool accepts any structured thinking that an LLM needs to perform. This can include:

  • Step-by-step problem analysis

  • Policy verification workflows

  • Multi-criteria decision making

  • Information synthesis from multiple sources

  • Complex reasoning chains

Usage Pattern: LLMs will automatically use this tool when they need to engage in complex reasoning. The tool does not retrieve new information or make changesβ€”it simply provides a space for structured thinking.

πŸ—οΈ Development

Project Structure

think-tool-mcp/
β”œβ”€β”€ src/
β”‚   β”œβ”€β”€ index.ts          # CLI entry point
β”‚   └── server.ts         # MCP server implementation
β”œβ”€β”€ examples/
β”‚   └── example_usage.md  # Usage examples
β”œβ”€β”€ dist/                 # Compiled JavaScript
β”œβ”€β”€ package.json
β”œβ”€β”€ tsconfig.json
└── README.md

Building from Source

# Install dependencies
npm install

# Build the project
npm run build

# Run in development mode
npm run dev

# Start the built server
npm start

Contributing

Contributions are welcome! Please feel free to submit a Pull Request. For major changes, please open an issue first to discuss what you would like to change.

  1. Fork the repository

  2. Create your feature branch (git checkout -b feature/amazing-feature)

  3. Commit your changes (git commit -m 'Add some amazing feature')

  4. Push to the branch (git push origin feature/amazing-feature)

  5. Open a Pull Request

πŸ“‹ Requirements

  • Node.js: Version 16 or higher

  • npm: Comes with Node.js

  • MCP-compatible platform: Cursor, Claude Desktop, or other MCP-supporting applications

πŸ” Troubleshooting

Common Issues

Server not starting:

  • Ensure Node.js 16+ is installed

  • Check that the command path is correct in your MCP configuration

  • Verify no port conflicts exist

Tool not appearing in AI platform:

  • Confirm MCP server is properly configured

  • Restart your AI platform after configuration changes

  • Check platform-specific MCP documentation

Permission errors:

  • On Unix systems, ensure the binary is executable

  • Try using npx instead of global installation

Debug Mode

For development and debugging:

npm run dev

This runs the server with TypeScript directly and provides more detailed error information.

πŸ“š Learn More

πŸ“„ License

This project is licensed under the MIT License - see the LICENSE file for details.

πŸ‘€ Author

Abhinav Mangla

πŸ™ Acknowledgments

  • Anthropic for the think tool research and methodology

  • The Model Context Protocol team for the excellent framework

  • The open-source community for contributions and feedback


Available Tools

1 tool
thinkA

Use this tool to think about something. It will not obtain new information or change anything. Use it when complex reasoning is needed.

  Args:
  thought: A thought to think about. This can be structured reasoning, step-by-step analysis, policy verification, or any other mental process that helps with problem-solving.
ParametersJSON Schema
NameRequiredDescriptionDefault
thoughtYes

TDQS

A3.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly states 'It will not obtain new information or change anything', which effectively communicates read-only, non-destructive behavior. It also implies the tool is for internal reasoning processes. While it doesn't cover rate limits or detailed operational constraints, it provides sufficient behavioral context for a tool with no annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized with two main sentences followed by parameter documentation. The first sentence states the purpose, the second provides usage guidance, and the Args section adds necessary parameter context. There's minimal waste, though the formatting with indentation could be slightly cleaner.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's conceptual nature (thinking/analysis), no output schema, and no annotations, the description provides adequate context about what the tool does and when to use it. However, it doesn't explain what the tool actually produces (e.g., structured output, internal state change) or how the 'thinking' manifests operationally, leaving some gaps in completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 0%, so the description must compensate. It provides a detailed explanation of the 'thought' parameter, describing it as 'structured reasoning, step-by-step analysis, policy verification, or any other mental process that helps with problem-solving'. This adds substantial meaning beyond the bare schema, though it doesn't specify format constraints or examples.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool is for 'thinking about something' and mentions 'complex reasoning', which provides a general purpose. However, it's vague about what 'thinking' entails operationally and doesn't distinguish from siblings (though none exist). It avoids tautology by adding context about reasoning, but lacks specificity about the verb+resource combination.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states 'Use it when complex reasoning is needed', providing clear context for when to invoke the tool. It also mentions 'It will not obtain new information or change anything', which helps exclude alternative use cases. However, with no sibling tools, there's no need for differentiation, so it can't score a 5 for explicit alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

TDQS

A3.6/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'think' has a clearly defined and distinct purpose for reasoning without external actions.

Naming Consistency5/5

A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The name 'think' is straightforward and follows a simple verb pattern.

Tool Count2/5

One tool is too few for most server purposes, as it severely limits functionality and scope. This feels thin and incomplete, even for a specialized server like 'MCP Think Tool Server', which might benefit from additional reasoning or analysis tools.

Completeness1/5

The server is severely incomplete; a single 'think' tool does not provide a coherent surface for any meaningful domain. There are significant gaps, as it lacks any tools for input, output, or interaction beyond internal reasoning, making it impractical for most agent workflows.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    D
    maintenance
    A Model Context Protocol server for Claude Desktop that provides structured memory management across chat sessions, allowing Claude to maintain context and build a knowledge base within project directories.
    22
    6
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    An MCP server that implements the 'think' tool, providing Claude with a dedicated space for structured thinking during complex problem-solving tasks to improve reasoning capabilities.
    131
    MIT

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/abhinav-mangla/think-tool-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server