Back to MCP directory
publicPublicdnsLocal runtime

mcp-think-tool

一个实现'think'工具的MCP服务器,为克劳德提供了一个专门的空间,以便在解决复杂问题时进行结构化思考,从而提高推理能力。

article

README

MCP Think Tool Server

A Model Context Protocol (MCP) server implementing the "think" tool for improving Claude's complex reasoning capabilities.

Overview

This MCP server implements the "think" tool as described in Anthropic's blog post, which provides Claude with a dedicated space for structured thinking during complex problem-solving tasks. The think tool has been shown to significantly improve performance in complex tasks requiring policy adherence and reasoning in long chains of tool calls.

Features

  • Structured Thinking Space: Provides Claude with a dedicated place to break down complex problems
  • Thought History: Maintains a log of all thoughts with timestamps for reference
  • Statistics and Analysis: Offers metadata about thinking patterns
  • Clean Slate Option: Allows clearing thought history when starting fresh

Installation

Install from PyPI:

pip install mcp-think-tool

Configuration

Windsurf

To use this tool with Claude in Windsurf, add the following configuration to your MCP config file:

"think": {
    "command": "/home/xxx/.local/bin/mcp-think-tool",
    "args": [],
    "type": "stdio",
    "pollingInterval": 30000,
    "startupTimeout": 30000,
    "restartOnFailure": true
}

The command field should point to the directory where you installed the python package using pip.

Docker

You can install this MCP server with only the Dockerfile

First download the Dockerfile, navigate to its directory, and build the Docker image

docker build -t mcp-think-tool .

Then add the following configuration your MCP config file

"think": {
    "command": "docker",
    "args": ["run", "--rm", "-i", "mcp-think-tool"]
}

This was tested and working with Claude Desktop and Cursor

help

Runtime guide

cloud

Hosted runtime

Hosted servers run from a provider-managed environment. You usually connect the MCP client to the hosted endpoint or follow the provider's authorization flow, without keeping a local process alive

  1. Open provider connection page
  2. Authorize or copy endpoint
  3. Connect from your MCP client
terminal

Local runtime / other methods

Local servers run on your own machine or infrastructure. You normally copy the server_config into your MCP client, install the required package, and provide env variables from env_schema when needed

  1. Copy server_config
  2. Install required package
  3. Fill env variables and restart client